Aside from the enjoyable Irish fire and humour I thought the most interesting part of this article was that it bought to my attention this part of the Priority of Constituencies that I hadn’t taken notice of before:
In case of conflict, consider users over authors over implementors over specifiers over theoretical purity.
The full suggestion from the spec is:
consider users over authors over implementors over specifiers over theoretical purity.
this seems something that is unlikely to work in reality. Is it really the expectation that the browser makers are seriously going to prioritise users and authors over their own implementations of the actual technical specifications. This strikes me as incredibly unlikely and naive given browser and web history. I see there’s a few people who work for browser makers lurking in the comments (hey Bruce); can anyone expand a bit on what the practical implications of this part of the spec is for the browser makers and how likely they would be to abide by it (or even how on earth they could abide by it if they wanted to).
Steerpike
Aside from the enjoyable Irish fire and humour I thought the most interesting part of this article was that it bought to my attention this part of the Priority of Constituencies that I hadn’t taken notice of before:
The full suggestion from the spec is:
this seems something that is unlikely to work in reality. Is it really the expectation that the browser makers are seriously going to prioritise users and authors over their own implementations of the actual technical specifications. This strikes me as incredibly unlikely and naive given browser and web history. I see there’s a few people who work for browser makers lurking in the comments (hey Bruce); can anyone expand a bit on what the practical implications of this part of the spec is for the browser makers and how likely they would be to abide by it (or even how on earth they could abide by it if they wanted to).