Bug 198291

Summary: Zoom affects maximum element size
Product: WebKit Reporter: Andy E <andyearnshaw>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ahmad.saleem792, bfulgham, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Repro case (ResizeObserver support required to view) none

Andy E
Reported 2019-05-28 03:49:29 PDT
Created attachment 370724 [details] Repro case (ResizeObserver support required to view) Steps to reproduce the problem: 1. Create a div at height 33554428px 2. Zoom in 3. Observe the change in div height As the zoom level increases, the height of the div decreases. This behaviour is not observed in Firefox or EdgeHTML. The impact it has is on virtual scrolling solutions where the total scrollable area is greater than the maximum permitted element height. In this situation, we apply a multiplier to the scroll position to get the virtual scroll position. Chrome and Safari's behaviour means that we need to observe resizes of an element at maximum height/width so we can adjust our scaling accordingly (see 195158 for more info on that).
Attachments
Repro case (ResizeObserver support required to view) (1.04 KB, text/html)
2019-05-28 03:49 PDT, Andy E 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2019-05-28 11:42:35 PDT
By "zoom" do you mean pinch-zoom or Command-+?
Andy E
Comment 2 2019-05-29 00:39:36 PDT
Command-+ on macOS Safari, sorry I should have been more clear on this. I'm not sure about pinch-zoom on iPad/iPhone as I am unable to test it currently.
Radar WebKit Bug Importer
Comment 3 2022-07-01 15:30:36 PDT
<rdar://problem/96317811>
Ahmad Saleem
Comment 4 2023-04-21 05:22:36 PDT
Chrome Canary 114 and Safari Technology Preview 168 matches each other and changes DIV height while Firefox Nightly 114 does not. Just wanted to share updated testing result. Thanks!
Note You need to log in before you can comment on or make changes to this bug.