We discussed this very briefly in the TAG meeting this morning and again in more depth in a breakout this afternoon. A few points came up: * Are there events that allow a page to detect and act on overscroll behavior? (perhaps a separate point, but worth looking into) * Should this be a new property, or should this be a new part of the value on 'overflow'? It wasn't clear to us which is the right thing; in CSS this is often decided by whether the pieces should cascade together or separately. * Another related question is whether there should be logical (inline-direction and block-direction rather than x and y) versions of these -- and also whether there should be logical versions of overflow-x and overflow-y. https://drafts.csswg.org/css-logical/ doesn't have those, though. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/193#issuecomment-332547145
Received on Wednesday, 27 September 2017 14:51:28 UTC