-
Notifications
You must be signed in to change notification settings - Fork 642
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
[scroll-animations-1] Something is odd with the handling of source
in the ScrollTimeline constructor
#5202
Comments
If we decide that a |
I notice that the procedure to resolve an element-based offset handles a null |
I guess the idea is that if the However thinking about this more, I wonder if we should allow a three state in our handling:
This is similar to how timeline is handler on |
But the spec explicitly says that the Document can have no scrollingElement and hence source can be null?
That would solve this issue (once we also define the behavior when source is null, e.g. in the "resolve a container-based offset" algorithm). I'm not sure if it's useful to be able to do that, but maybe it's fine. |
…5263) Fixing #5202 and #5211 Changes: - Fix IDL to make source nullable. - In CSS source will accept 'auto' and 'none' with none mapping to null. - In JS, we now map missing 'source' to document scrolling element (i.e., auto behavior) and explicitly null 'source' to null. - Correctly check null source when calculating offsets. Other minor cleanups.
Spec is fixed. I have filed a bug to fix Chromium implementation. |
The
ScrollTimeline
constructor text has the following:Which is odd because
source
is not nullable in theScrollTimeline
spec. So how can we assignsource
if it is null?Also, "Let source be source" is odd. Clearly it means the
source
member ofoptions
but it needs to say that.The text was updated successfully, but these errors were encountered: