Krzysztof Jurewicz
Follow

If we want to achieve compatibility between , it is important to implement strictly, without non-standard error recovery. For example, someone mistyped backslashes into stylesheet URL on kobo.com. and convert backslashes into slashes, while displays website without any styles (correctly, I presume).

@KrzysiekJ I've been bugged by this for as long as I can remember. Standards are agreed upon, then discarded for the sake of convenience. Major browser being less strict is considered a "competitive advantage", as from the nontechnical user's viewpoint, they are the ones that "work" with those sites unlike others.
But there seems to be no adequate way to fight this behavior. Standards can't really be enforced by anyone other than browser creators.

@KrzysiekJ what is even more strange to me is why these vendors won't push for a liberalization of the standard in such cases? This would still leave them with the competitive advantage of being the ones who have implemented them "properly" first, while pushing for more consistency on the web.

I'm not even touching on the subject that this behavior reinforces sloppiness, lack of care for coding standards and general ignorance.

@kunev I guess there is some reluctance to standardise error correction. It would make implementations more complicated.

Sign in to participate in the conversation
capitalism.party

capitalism.party is a paid signup Mastodon instance funded directly by users purchasing accounts for just $5. An inexpensive alternative to free signup platforms, we impose direct economic cost on trolls who want to avoid blocks by creating many accounts. This instance will actively respond to any problematic users.