[Webkit-unassigned] [Bug 161875] New: Setting contentInset on a WKWebView's scroll view does not work for PDFs.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 12 15:06:08 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=161875

            Bug ID: 161875
           Summary: Setting contentInset on a WKWebView's scroll view does
                    not work for PDFs.
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: iOS
                OS: iOS 9.3
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: gchatz at chromium.org

Created attachment 288614
  --> https://bugs.webkit.org/attachment.cgi?id=288614&action=review
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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160912/a4b629c9/attachment.html>


More information about the webkit-unassigned mailing list