W3C home > Mailing lists > Public > public-houdini@w3.org > June 2015

RE: Properties of Custom Layout

From: François REMY <francois.remy.dev@outlook.com>
Date: Mon, 1 Jun 2015 19:07:56 +0200
Message-ID: <DUB405-EAS374C01D127E47665BE98875A5B60@phx.gbl>
To: "'Ian Kilpatrick'" <ikilpatrick@chromium.org>, <public-houdini@w3.org>
> Shane & [Ian] sat down what we think are some of the desirable properties.
> https://gist.github.com/bfgeek/93408fe4182d87e92b7b

I still have a lot to learn about how browsers handle layout internally so I'll leave to more experienced people the opportunity to chime in, but here are a few comments of mine.

- If the browser can decide not to layout some element because it's off-viewport, should a custom layout be able to do the same? How/based on which pieces of information?

- If a custom layout decides some elements do not need to be included in the layout right now to avoid blocking the frame, can it just ask for another layout opportunity during the next frame, even if the style wasn't updated?

- What if we want to emulate something like scrollbars or carousels? Should custom layout be allowed to layout out boxes that are not in the DOM for their own purposes, and get some basic events on them and on the layouted element itself if it's focusable (I was thinking about: pointer-over, pointer-click, focus, enter-key, space-key, left-key, right-key, up-key, down-key)? Should we resort to using a web component as a backend for the custom layout? If so, is it that far away from the now-shelved "decorator" property proposal?

Best regards,
Received on Monday, 1 June 2015 17:08:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 1 June 2015 17:08:20 UTC