> All/most of the hardware APIs are considered harmful by both Safari and Mozilla.
Well yes. Re https://wicg.github.io/webhid/, there's a risk in allowing apps to talk to hardware. We still let non-web apps do this. We deny by default, and have permissions screens etc where people can allow/reject the access.
Disagreements are a separate issue from Safari's record of shipping broken versions of uncontroversial web standards though. Eg, Mozilla disagrees with hardware support but nobody accuses them of ignoring web standards.
> We deny by default, and have permissions screens etc where people can allow/reject the access.
Yes, we do. And notification/dialog/prompt fatigue is one of many reasons listed behind not supporting these APIs. And at the link to the GitHub issue I provided a timeline of events for this "standard" which is anything but. Why would Firefox or Safari want to implement a standard that they had literally no input on?
> Disagreements are a separate issue from Safari's record of shipping broken versions
You asked for "If there are examples of 'Apple ignoring standards' actually meaning Chrome-only features please tell me one." I provided at least two. There are many others.
> Eg, Mozilla disagrees with hardware support but nobody accuses them of ignoring web standards.
Because it's fashionable to hate Safari with no justification other than because it's a drum incessantly drummed by Google's army of developer advocates. Even though more often than not Safari and Mozilla are in agreement about web standards these days. And are significantly closer to each other in the number of APIs shipped than they are to Chrome: https://web-confluence.appspot.com/#!/confluence
Even you didn't know about issues with Chrome's non-standards until I provided you with examples, but "Safari is the largest driver of the 'Safari no support standards'"
> All/most of the hardware APIs are considered harmful by both Safari and Mozilla.
Well yes. Re https://wicg.github.io/webhid/, there's a risk in allowing apps to talk to hardware. We still let non-web apps do this. We deny by default, and have permissions screens etc where people can allow/reject the access.
Disagreements are a separate issue from Safari's record of shipping broken versions of uncontroversial web standards though. Eg, Mozilla disagrees with hardware support but nobody accuses them of ignoring web standards.