4 ms·
Hmm, so I'm assuming from this post that this same Safari CSS bug is present in GNOME Web too? 'Cause if it isn't then it's not really a good proxy for testing
by jabbany 5y ago
Hmm, so I'm assuming from this post that this same Safari CSS bug is present in GNOME Web too?
'Cause if it isn't then it's not really a good proxy for testing Safari behavior in this context...
- breakfastduck 5y agoWebKit is the engine safari uses so anything that uses WebKit should in theory provide the exact same rendering experience.
- jabbany 5y agoSafari itself is not open source so it's unclear how much/little they have modified WebKit and the JavaScript engine. Given that this bug involves JS (events not firing), and MacOS doing its own thing with JS, it's entirely possible that this is a Safari only bug that resides in the proprietary parts of the codebase...