Bug 172838

Summary: Allow clients to override viewport size for CSS viewport units.
Product: WebKit Reporter: alan baradlay <zalan>
Component: Layout and RenderingAssignee: alan baradlay <zalan>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, commit-queue, simon.fraser, thorton, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

alan baradlay
Reported 2017-06-01 15:59:46 PDT
vh, vw etc
Attachments
Patch (22.06 KB, patch)
2017-06-01 16:21 PDT, alan baradlay
no flags
Patch (22.06 KB, patch)
2017-06-01 20:28 PDT, alan baradlay
no flags
Radar WebKit Bug Importer
Comment 1 2017-06-01 16:00:52 PDT
alan baradlay
Comment 2 2017-06-01 16:21:35 PDT
Simon Fraser (smfr)
Comment 3 2017-06-01 16:29:05 PDT
Comment on attachment 311774 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=311774&action=review > Source/WebKit2/ChangeLog:11 > + This enables auto-sizing clients to ensure that styles relative to the viewport are > + resolved to a set value (presumably the size of the container) as opposed to the preferred > + document size (which is set as the FrameView size). How does this relate to fixedLayoutSize? Could we use that as something to resolve viewport units against?
Tim Horton
Comment 4 2017-06-01 16:54:29 PDT
Comment on attachment 311774 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=311774&action=review > Source/WebKit2/WebProcess/WebPage/WebPage.h:883 > + std::optional<WebCore::IntSize> viewportSizeForCSSViewportUnits() { return m_viewportSizeForCSSViewportUnits; } const?
alan baradlay
Comment 5 2017-06-01 20:28:48 PDT
WebKit Commit Bot
Comment 6 2017-06-02 11:38:20 PDT
Comment on attachment 311798 [details] Patch Clearing flags on attachment: 311798 Committed r217725: <http://trac.webkit.org/changeset/217725>
WebKit Commit Bot
Comment 7 2017-06-02 11:38:22 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.