| Summary: | New page loaded with a negative content offset for the first time | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Daohan Chong <dh.chong> | ||||||
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||||
| Status: | NEW --- | ||||||||
| Severity: | Critical | CC: | beidson, ddkilzer, simon.fraser, thorton, webkit-bug-importer | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | Safari 13 | ||||||||
| Hardware: | Mac | ||||||||
| OS: | macOS 10.15 | ||||||||
| Attachments: |
|
||||||||
|
Description
Daohan Chong
2020-05-26 06:15:19 PDT
Created attachment 400241 [details]
Demo project (need to be run on macCatalyst)
Attaching a demo project.
Please note that this should be run on mac catalyst
Created attachment 400242 [details]
Screenshot
Attaching a screenshot
This reproduces for me. You can work around this (I tried in your test app) by avoiding the safe area: webView.frame = view.bounds.inset(by: view.safeAreaInsets) but ... we should figure out why this isn't working, since it works fine on iOS. This bug still exists on Version 14.0 (16610.1.23.1.3), Big Sur beta Adding a new radar: FB8704777 (In reply to Daohan Chong from comment #6) > Adding a new radar: FB8704777 The interesting thing about this bug report (per the reporter) is that it demonstrates that this bug also affects MobileSafari. (In reply to David Kilzer (:ddkilzer) from comment #7) > (In reply to Daohan Chong from comment #6) > > Adding a new radar: FB8704777 > > The interesting thing about this bug report (per the reporter) is that it > demonstrates that this bug also affects MobileSafari. Desktop Safari is also affected. Not 100% repro. Any updates on this bug? It can still be reproduced on macOS 12.0 beta. In addition, on iOS 14.x, `SFSafariViewController` can sometimes repro this bug. |