Bug 161875

Summary: Setting contentInset on a WKWebView's scroll view does not work for PDFs.
Product: WebKit Reporter: gchatz
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: jonlee, thorton
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: iPhone / iPad   
OS: iOS 9.3   
Attachments:
Description Flags
test app
none
actual results
none
expected results none

gchatz
Reported 2016-09-12 15:06:08 PDT
Created attachment 288614 [details] test app Summary: If I set the top content inset on the scroll view of a WKWebView during the - webView:didFinishNavigation: callback, the content is pushed down at page load for regular webpages but not for PDFs. Instead, the PDF loads as scrolled to the top, and the user has to manually scroll it to make room for the inset. Steps to Reproduce: Run attached test app which does the following steps: 1. Loads a PDF in a WKWebView 2. Sets contentInset during the -webView:didFinishNavigation callback. Expected Results: PDF loads scrolled down with enough room for the content inset (see screenshot.) Actual Results: PDF is scrolled to the top. (see screenshot) Version: Since at least iOS 9.0 Configuration: iPhones and iPads
Attachments
test app (27.50 KB, application/zip)
2016-09-12 15:06 PDT, gchatz 		no flags
Details
actual results (245.15 KB, image/png)
2016-09-12 15:06 PDT, gchatz 		no flags
Details
expected results (220.87 KB, image/png)
2016-09-12 15:06 PDT, gchatz 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
gchatz
Comment 1 2016-09-12 15:06:40 PDT
Created attachment 288615 [details] actual results
gchatz
Comment 2 2016-09-12 15:06:59 PDT
Created attachment 288616 [details] expected results
Note You need to log in before you can comment on or make changes to this bug.