News for hackers. Stuff that matters.
Re:Apple is not defending browser engine choice by BaculumMeumEst on Friday June 24, 2022 @06:44AM (#31859913)
I’ve done this but I haven’t encountered issues so far. What’s an example of some vanilla js/html/css that breaks under safari?
Re:Apple is not defending browser engine choice by lucsky on Friday June 24, 2022 @07:42AM (#31860327)
Two examples I have encountered in the past month alone that work just fine on any other browser but Safari:

- CSS outline not being affected by the border-radius property.

- Drag images being completely screwed up if the dragged element, or any of its ancestor, has a CSS transform.

Both of these problems have workarounds (insanely ugly hacks would be a better term), but they shouldn't have.

Re:Apple is not defending browser engine choice by mtomweb on Friday June 24, 2022 @08:27AM (#31860740)
Oh that second one is a nightmare. Our solution for it was to copy the element and create a new one that was absolutely positioned for the draggable element. The issue is syncing elements can be quite tricky.
Re:Apple is not defending browser engine choice by SCLeo on Friday June 24, 2022 @08:27AM (#31860729)
From my memory:

- Regular expression lookbehind

- overscroll-behavior

- Web push

- SVG favicon

- Web Bluetooth (haven't run into this personally, but someone complained about this)

Re:Apple is not defending browser engine choice by halostatue on Friday June 24, 2022 @10:32AM (#31862517)
From a developer user's perspective:

- Nice to have - Problem - Don’t want it, will never allow it - Nice to have - Don’t want it, will never allow it

Of the five items you list, I only see one as a real problem. Two of them are privacy misfeatures that have no business being on the web platform. The other two are annoying and would be better to have than not.

Re:Apple is not defending browser engine choice by blinzy on Friday June 24, 2022 @03:14PM (#31867935)
It's not about whether you like it, or they like it, or I like it; it's about being able to provide certain features that a subset (of which you may or may not be a member) desire or require.

For example, taking web push notifications, you and many others may not want it, but someone else and many others too may want it for whatever reason:

- maybe from a developer perspective because they're a hobbyist and don't want to create an app instead of a website just to get notifications, but would be happy if they had the option. And before you say you don't need them, you DON'T know their use case, e.g., if it's a chat web-app it's going to be pretty damn useless without notifications.

- maybe from a user's perspective because they're not happy granting additional permissions (or making it harder to use an ad-blocker) that could be required by an app from the store, they just need the push notification to get some alert, but don't want to give up access to their photos, files, or contacts too.

In any case, it's about having empathy towards allowing others to have wants/needs different from yours, and if you do that and put yourself in other people's shoes, you should be able to see that Safari is clearly lacking in implementing a bunch of features (or delivering them several years after every other browser).

Finally, all that doesn't take away the fact that Safari does some things better than others, and that other browsers do things worse or push features that are in line with their own agenda or monetisation strategy.

Re:Apple is not defending browser engine choice by mtomweb on Friday June 24, 2022 @08:25AM (#31860718)
https://github.com/web-platform-tests/interop-2022/issues/84 << this issue we’ve had for at least 7 years. It’s never worked and to solve all the edge cases the workarounds are insane.