Created attachment 466588 [details] WebKit ToT (same as Safari 16.5) Hi Team, While going through Playstation website, I noticed that the animation is jittery and slow compared to Chrome Canary 116. Link: https://www.playstation.com/en-gb/ps-plus/#subscriptions Just capturing the video to help out. Thanks!
<rdar://problem/110603549>
Seems to work fine now in Safari 17 and WebKit ToT on macOS Sonoma. Might be Safari 16.x specific or macOS Ventura? @Karl - by any chance, can it be tested with Safari 16?
Yes probably with Xcode https://developer.apple.com/documentation/safari-developer-tools/adding-additional-simulators that would be then accessible through Develop Menu in "Open Page With…"
I think Karl got confused with his reply and thought this was related to testing on iOS. I tested this with Safari 16.6 on macOS Ventura 13.5.2 (22G91) and I can confirm that while the issue is very much present there, with macOS Sonoma the issue is no longer present. However, testing a ToT build on macOS Ventura shows the issue is still there. So this may well be an issue below WebKit which got fixed in macOS Ventura, or some Ventura-specific WebKit behavior. Either way, the reported issue is indeed fixed in Safari on macOS Ventura. Ahmad, does that answer your question?
(In reply to Antoine Quint from comment #4) > I think Karl got confused with his reply and thought this was related to > testing on iOS. I tested this with Safari 16.6 on macOS Ventura 13.5.2 > (22G91) and I can confirm that while the issue is very much present there, > with macOS Sonoma the issue is no longer present. However, testing a ToT > build on macOS Ventura shows the issue is still there. So this may well be > an issue below WebKit which got fixed in macOS Ventura, or some > Ventura-specific WebKit behavior. Either way, the reported issue is indeed > fixed in Safari on macOS Ventura. > > Ahmad, does that answer your question? Yes - it helps. If it is fixed on below WebKit level, do I need to tag this as 'RESOLVED MOVED' or 'RESOLVED CONFIGURATION CHANGED', or we continue to track this since macOS Ventura is supported?
Not an expert of Bugzilla resolutions, so your guess is as good as mine. As to whether we would want to keep this open to fix on Ventura, I can't speak with any kind of authority on that, but I expect a bug specifically targeting a previous OS that does not have an impede the use of a popular website or is a security concern will likely not be deemed a high priority.