3 ms·

> > I develop for Firefox. Chrome basically always works fine with my pages. Safari chokes on all of them. > Doubt. For what it's worth, my development profil

> > I develop for Firefox. Chrome basically always works fine with my pages. Safari chokes on all of them. > Doubt. For what it's worth, my development profile is similar. I would say that Safari works most of the time, but I get browser-specific failures from it at a noticeably higher rate than Chrome-derivatives. One memorable one, if you're curious, was triggered because of a minification step. Terser[0] has a special argument `--safari10` to emit code that's supported by Safari. I discovered this argument after running into the bug. [0]: https://github.com/terser/terser https://github.com/terser/terser

illiarian 4y ago
> Terser[0] has a special argument `--safari10` to emit code that's supported by Safari. I discovered this argument after running into the bug. So the problem is with the tool, not with the Safari it seems. Without an explanation what "non-standard" is about Safari 10/11 it's on the same level as the rest of hand wringing on HN.
- recursive 4y ago
  > So the problem is with the tool, not with the Safari it seems. You're making an assumption. I'm not sure where you're getting that. From what I recall, it was common `const` or parameter declarations in nested scopes. Safari was (is?) unambiguously wrong. Edit: here's the bug: https://bugs.webkit.org/show_bug.cgi?id=171041 https://bugs.webkit.org/show_bug.cgi?id=171041