-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request review for Scroll Boundary Behavior #193
Comments
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:
|
Thanks for the feedback. Here is our initial thinking about these. Are there events that allow a page to detect and act on overscroll behavior? (perhaps a separate point, but worth looking into) I don't think however that there is a major issue with having a non-blocking event. Also there is already a scroll customization effort that aims to create low-level primitive that explain scrolling. I think that spec is an appropriate venue to explore the idea of adding an event if there is enough interest. 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. Also we have the precedent of 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. |
subscribe |
FYI, there was some discussion and we reached consensus to use a slightly shorter name |
... and the spec has moved. |
Thanks @dbaron for pointing that out. I should have mentioned this as well but I was incorrectly assuming that GH redirects the links after repo rename. It actually does so for the repo itself but not for the associated gh-pages. Is there any concern or question regarding the above answers? Btw here is a blog post with more examples and demo of the feature. |
Discussed in out 2017-11-21 telcon and generally approved. Our primary concern at this point is where this fits in to Houdini scrolling APIs, e.g. how can this behavior be explained in terms of the lower-level API? how does the scrolling API provide the missing pieces to implement functionality like "pull-to-refresh"? We accept this property is but one part of a larger picture, we just want to see the rest... |
Hello TAG!
I'm requesting a TAG review of:
Further details (optional):
You should also know that...
The current design is the result of discussion with various CSSWG and WICG members.
You can see relevant discussion on this CSSWG github issue and WICG discourse thread.
We have a working prototype implemented in Chromium behind web platform experimental features flags. The API has received positive feedback from Edge and Mozilla and addresses a real need from web developers here and here.
We'd prefer the TAG provide feedback as (please select one):
The text was updated successfully, but these errors were encountered: