RESOLVED DUPLICATE of bug 145136 24807
Don't run transitions when the user zooms 
https://bugs.webkit.org/show_bug.cgi?id=24807
Summary Don't run transitions when the user zooms
Simon Fraser (smfr)
Reported 2009-03-25 10:50:54 PDT
Changes in zoom level should not fire transitions, which they do now. See testcase.
Attachments
Testcase (649 bytes, text/html)
2009-03-25 10:51 PDT, Simon Fraser (smfr) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2009-03-25 10:51:16 PDT
Created attachment 28935 [details] Testcase
Peter-Paul Koch
Comment 2 2011-10-08 11:56:41 PDT
The original test case does not display the bug. However, additional test cases at http://quirksmode.org/css/transitions.html do. This is my test page for common transition effects, and all transitions are triggered by a zoom, which should not happen. Tested in Chrome 14.0.835.186 and Safari 5.1 on Mac OS 10.6.8 . Opera 11.51 and Firefox 6.0.2 on the same OS do not have this bug. Alex Russell asked me to add eae@google.com and esidel@webkit.org to the cc list, but I'm afraid I don't know how to do that.
Ahmad Saleem
Comment 3 2022-09-20 05:59:18 PDT
I am able to reproduce this bug in Safari 16 using attached "test case" and it does do 'transition' while zooming in while other browsers (Chrome Canary 108 and Firefox Nightly 107) does not. Just wanted to share updated results. Thanks!
Ahmad Saleem
Comment 4 2022-09-20 11:19:56 PDT
Fixed in Chromium / Blink - https://crbug.com/267316
Ahmad Saleem
Comment 5 2023-02-24 09:28:18 PST
*** Bug 24666 has been marked as a duplicate of this bug. ***
Antoine Quint
Comment 6 2023-05-10 12:57:37 PDT
*** Bug 198025 has been marked as a duplicate of this bug. ***
Ahmad Saleem
Comment 7 2023-05-10 14:43:22 PDT
This seems to be fixed with following commit: https://github.com/WebKit/WebKit/commit/be05571ab5fe4f51bd9f1ab85a0a2017b821a3c4 Matching Chrome Canary 115. Marking this as "RESOLVED DUPLICATE". *** This bug has been marked as a duplicate of bug 145136 ***
Note You need to log in before you can comment on or make changes to this bug.