W3C home > Mailing lists > Public > www-style@w3.org > January 2016

Re: [css-round-display] Non rectangular displays and the robustness of CSS

From: Shane Stephens <shans@google.com>
Date: Tue, 12 Jan 2016 20:56:49 +0000
Message-ID: <CAGTfzwT6ETbfa_ByfLk7ip453fNgQjJGku9w7jVCWn5cE+=F6w@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>, Alan Stearns <stearns@adobe.com>
Cc: www-style list <www-style@w3.org>
On Tue, Jan 12, 2016 at 2:22 PM Florian Rivoal <florian@rivoal.net> wrote:

> > On Jan 12, 2016, at 03:04, Alan Stearns <stearns@adobe.com> wrote:
> >
> > On 1/11/16, 5:51 AM, "Florian Rivoal" <florian@rivoal.net> wrote:
> >
> >>
> >>> On Jan 11, 2016, at 18:32, Shane Stephens <shans@google.com> wrote:
> >>>
> >>> Perhaps a simple solution would be to require non-rectangular displays
> to define a default rectangular view that can be overridden by new round
> display primitives?
> >>
> >> Maybe. That said, on watches, the rectangular viewport that is small
> enough to fit inside the circle (so that there's nothing hidden by the
> corner) is so tiny I'm not sure that's practical.
> >
> > You can view everything in a rectangular view inside a circular display
> as long as you can scroll all of the contents through the center of the
> screen. Perhaps the default simple solution should be to extend the
> scrollable area of the default rectangular view 50% of the screen height in
> both the block-start and block-end directions?
> Right. That's also much simpler (which is good) than what I had in mind,
> but I'm not sure:
> 1) Even if you can read the line in the middle, that's not a great
> experience
> 2) On other-than-round non rectangular shapes, this may not be true (
> http://jsbin.com/kunezu/edit?html,css,output). Yes this example may be
> far-fetched, but the point is to get something that works *in environments
> the author has not anticipated*.

This is why a device-specific maximal viewport rectangle approach works

Taking your point of rectangular viewports being "so tiny" - by restricting
ourselves to the maximal rectangle inside a circle, we're restricting
ourselves to 2/π or ~64% of the total screen area.

I'd argue that if you thought this square was too small to be useful,
adding (a total of) half its size again in the form of four crescent shaped
pieces attached to each edge isn't going to make much difference.


> 3) What property's initial value causes this to happen on shaped screens
> but not on rectangular ones / how do you get rid of the over-scroll if you
> have tailored to the screen shape? (i.e. how does it fit the model?)
>  - Florian
Received on Tuesday, 12 January 2016 20:57:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:59 UTC