5 ms·
Simply put: Don't write for chrome, write w3c conform. Or better: Use standards which match most browsers at caniuse.com
by xtf 7y ago
Simply put: Don't write for chrome, write w3c conform.
Or better: Use standards which match most browsers at caniuse.com
- richthegeek 7y agoThat only works if everyone does it. At the moment some people develop only for Chrome because it has the most market share. So they deploy their site using the <toast> thing and suddenly people using Firefox are wondering why things are broken. At this point Firefox can either implement the new feature(s) or lose users. And once FF etc. have implemented it suddenly it's on caniuse.com as "works in all modern browsers".
- vcavallo 7y ago> that only works if everyone does it which is probably why OP is suggesting it
- deleted 7y ago[deleted]
- BlueTemplar 7y agoEven better : Develop for Firefox / Gecko in mind, and ignore Chrome / Chromium / Blink / V8 / Node.js