|
|
|
|
|
by tekknik
2106 days ago
|
|
> I don't write fronted software anymore, but writing for every browser means adhering to the standard. Yes, which you’ll find if you do Safari adheres to quite well. Finding examples where it doesn’t is easy, just like on chrome. Which is why we have media queries and poly fills because it’s simply impossible to have a unified platform without one entity owning it. If you found out Chrome doesn’t render the same on linux as it doesn’t on windows, would you call this not adhering to the standard? |
|
They don' t
Apple refused to implement 16 web API in Safari
> Which is why we have media queries and poly fills because it’s simply impossible to have a unified platform
And that' s why big players like Apple hat control a closed ecosystem shouldn't be allowed to be assholes
At least on Android I can install other browsers and other browser engines
Do you see the difference?
> Chrome doesn’t render the same on linux as it doesn’t on windows
that' s not true
Windows and Linux that have simply different font rendering engines and different native widgets
That's all
> would you call this not adhering to the standard?
absolutely NOT!
In no part of the standard rendering is formalized
It wouldn't make sense
The way things are rendered is standardized, not the way they should look
https://www.w3.org/TR/2014/REC-html5-20141028/rendering.html
> HTML is intended to apply to multiple media (it is a media-independent language). User agent implementors are encouraged to adapt the suggestions in this section to their target media.