Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689)

Adding an extensibility point via a more complex object sounds like a reasonable way to stage this API. But I'm not sure I'm convinced unconditionally exposing the hinge as a segment is a net positive for developers, and either muddies the waters w.r.t. the concept of viewport segments as exposed via environment variables or makes them much more complex to use. Designing for future form factors is one thing, but consider the real-world devices in market today - Samsung foldables have no hinge, while Surface Duo does (i.e. the hinge consumes part of the viewport). Do we really want developers to have to add if statements and duplicate logic to support separate dual-view implementations on those devices? 

From https://github.com/w3c/csswg-drafts/issues/6339, the VisualViewport spec is to be adopted into cssom-view, so CSSWG is the destination.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/689#issuecomment-1138041335
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/689/1138041335@github.com>