So, after half an hour fighting with the European Commission's website to provide feedback on the draft-proposal of the Cyber Resilience Act, I tried in Chromium and went through swimmingly. What does this tell us about how serious the EU institutions are about reigning in Google's quas-monopoly if the same institutions cannot be arsed to make their websites work on browsers like Mozilla Firefox?
@whvholst How many other browsers (or, more specifically, rendering and/or javascript engines) did you try on? Two data points doesn't give much indication of their standards support.
@sparr @whvholst However, it's not like there are dozens of major engines. Missing Firefox support is a big one, regardless of the number of data points.
@shiide @whvholst supporting browsers should never have been a thing, and should cease to be a thing. support standards. if Firefox (or chrome, or safari) has a bug that breaks a standard, that's a firefox problem, not a problem with your website that follows the standard.
@sparr @shiide @whvholst that sounds like a perfect plan for stifling innovation and competition. While we're at it, cars should avoid adding safety features so people don't get confused about which car they are driving and all cars will fit in all garages, and it follows that buildings should all look the same, so no one gets confused about where the doors and light switches are, or where they should park.
@Matthewlariz @shiide @whvholst Adding features is potentially orthogonal to breaking standards. Nothing I said implied features shouldn't be added.
@sparr @Matthewlariz I didn't intend to imply that you implied that. 🙂 All I'm saying is that if a site doesn't work on a browser, it's a site problem.