Hacker News Reader

Comment by mmis1000 | Hacker News Reader

The point is they are not even compliment to their "own" spec. They are part of whatwg. But if you ever write web page. You will know it's always the safari that differs from the spec. Firefox in the other end never have such issue.

Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari. Supports safari literally means support another browser (by workaround all its bugs).

View on HN

> The point is they are not even compliment to their "own" spec. They are part of whatwg.

I think web devs have too much faith in the "standard"; the WHATWG specifies anything supported by two implementations, and with Google controlling Mozilla that already feels somewhat unfair...

> Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari.

Disregarding the issue that you're writing pages that only 90% work on anything but Chrome... do you have any examples of Safari misbehaving?

The ios safari lies you about (or simply bugged out) video play event, display video element on play event will show a blank screen to user. This never happen in any other browser(including those china vendor browsers) except safari. To make this worse, you can't make a unloaded video element on safari to have transparent background so user will definitely see a black square unless you add a delay to mitigate the problem.(Most players already do it, but it's still a pain if you need to make one from scratch)

Those are some exaggerated beyond belief numbers you just made up. Some of us also work in web development and know better.

It's not even exaggerated, the ticket count about safari on my board is almost higher than sum of every other browser in total. I 100% just want this browser die if apple ever allow other browser on ios.

I mean that could be "two Safari tickets" for all we know, and you could be ignorantly chasing Chrome's ChromeOS un-standards or bleeding edge RFCs thinking a reference implementation or a mere memo should work everywhere. Personally, I almost never see Safari-specific bugs be reported and can't find one in my company's JIRA system in the last year. Are you sure you're not self-inflicting this pain?

Your desire for Safari to vanish is also historically short sighted. Ladybird has near-zero usage, Firefox is practically dead and is fully bought and paid for by Google, everything else is just a Chrome or Chromium fork. Safari is realistically the only thing holding back an outright Chrome monopoly with meaningful usage.

The safari literally broke border-radius of image whenever a opacity transition is triggered. It's the simplest effect you will see everyday. Or broke layer of position: fixed element when containing container is scrolled. They aren't even new features and exists since like 10 year ago? And it's still broken that requires specific workaround. Or on ios 26(the one just released). Every page that added to ios home screen is no longer able to play video at all if you close it and open it the second time. The list can go on infinitely if I ever want to dig up. When is the crap even usable? There isn't a way to not hit bugs at all unless your page is extremely barebone and require little interaction.

Besides these, the service worker debugger never work on my iphone device since like two major version ago.(It did not show up in the safari menu) There is no way to use it as a developer even I want to (let alone the devtool crashes and disconnects frequently)

Reply on news.ycombinator.com