3 ms·

I feel bad for such a brief reply: contenteditable And: Safari (https://www.safari-is-the-new-ie.com/ https://www.safari-is-the-new-ie.com/)

deanclatworthy 5y ago
These problems, much like the IE problems back in the day are well documented. Much like you need domain knowledge to work on the back-end this is "par for the course" in front-end world also.
- brailsafe 5y ago
  There are many documents in the world, but knowing when to look or how to find them comes over time and with much frustration.
skinkestek 5y ago
Making a website for it is good marketing, but it doesn't make it anymore true. Chrome is the new IE: - introduces its own standards: check - technologically superior in narrow fields: check - forced upon everyone by the most powerful computer company at its time true a multitude of shady deals, bundling etc: check - lazy programmers doesn't verify in other browsers: check - will be abandoned as soon as they have crushed competition: jury is still out, bit based on previous behavior by defender it is more a question of when rather than if. The same absolutely cannot be said for Safari.
- zamalek 5y ago
  At the end of the day the discrepancy is my point, it doesn't matter which browser is the worst culprit.
- aniforprez 5y ago
  Actually I'd say every single one applies to Safari more than Chrome. Chrome is not forced upon anyone in most cases. Most sites in Chrome would work just as well or better in FF. Lazy programmers is not something Chrome controls at all. It's just what makes sense considering the ubiquity of its use worldwide but is not something that's a good practice or Chrome's fault
  - skinkestek 5y ago
    > Actually I'd say every single one applies to Safari more than Chrome. Then you must read closer. Even one of your cherry picked examples is plain wrong.
- vbezhenar 5y ago
  Chrome is open source (well, except few proprietary parts nobody cares about). And not just formally open source, there are plenty of browsers built on chrome engine. That's its main difference from IE.

deanclatworthy 5y ago

These problems, much like the IE problems back in the day are well documented. Much like you need domain knowledge to work on the back-end this is "par for the course" in front-end world also.

brailsafe 5y ago
There are many documents in the world, but knowing when to look or how to find them comes over time and with much frustration.

skinkestek 5y ago

Making a website for it is good marketing, but it doesn't make it anymore true. Chrome is the new IE: - introduces its own standards: check - technologically superior in narrow fields: check - forced upon everyone by the most powerful computer company at its time true a multitude of shady deals, bundling etc: check - lazy programmers doesn't verify in other browsers: check - will be abandoned as soon as they have crushed competition: jury is still out, bit based on previous behavior by defender it is more a question of when rather than if. The same absolutely cannot be said for Safari.

zamalek 5y ago
At the end of the day the discrepancy is my point, it doesn't matter which browser is the worst culprit.
aniforprez 5y ago
Actually I'd say every single one applies to Safari more than Chrome. Chrome is not forced upon anyone in most cases. Most sites in Chrome would work just as well or better in FF. Lazy programmers is not something Chrome controls at all. It's just what makes sense considering the ubiquity of its use worldwide but is not something that's a good practice or Chrome's fault
- skinkestek 5y ago
  > Actually I'd say every single one applies to Safari more than Chrome. Then you must read closer. Even one of your cherry picked examples is plain wrong.
vbezhenar 5y ago
Chrome is open source (well, except few proprietary parts nobody cares about). And not just formally open source, there are plenty of browsers built on chrome engine. That's its main difference from IE.