Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Scrolling propagation #26

Closed
frivoal opened this issue Feb 16, 2018 · 2 comments
Closed

Scrolling propagation #26

frivoal opened this issue Feb 16, 2018 · 2 comments
Labels
closed:invalid Off topic / out of scope / non actionable / already handled topic:spec type:question Known unknows: things we need to investigate

Comments

@frivoal
Copy link
Collaborator

frivoal commented Feb 16, 2018

The propagation of scrolling up the ancestor chain described in the spec (for the non spatnav case) is how Chrome and Safari behave, but Firefox is different. We should get the spec and all implementations to align.

Note: this may interact with #19
@hugoholgersson
Copy link

Is this the same problem as http://crbug.com/585413 ?

I'd like the spatnav algorithm to behave more lite I've outlined in http://bit.ly/snav2 = instead of propagating scroll-actions outside fully scrolled scrollers, we first focus that scroller.

Firefox's Tab-key navigation does this. I believe spatnav (aka directional navigation) and tab-key navigation (aka sequential navigation) should handle scrollers in the same way.

frivoal added a commit to frivoal/spatial-navigation that referenced this issue Mar 20, 2018
@frivoal
Remove the spatial-navigation property
8d6ac29 
Whether spatnav should get invoked from arrow keys or something else
is for the UA to decide, and we don't need (at least in this level)
to provide control over it.

This also lets us get rid of the monkey-patch on UI-Events.

Closes WICG#35

Also closes WICG#22, WICG#24, and WICG#26 (as invalid / out of scope) by
deleting the section these issues applied to.
frivoal added a commit to frivoal/spatial-navigation that referenced this issue Mar 20, 2018
@frivoal
Remove the spatial-navigation property
27cdd49 
Whether spatnav should get invoked from arrow keys or something else
is for the UA to decide, and we don't need (at least in this level)
to provide control over it.

This also lets us get rid of the monkey-patch on UI-Events.

Closes WICG#35

Also closes WICG#22, WICG#24, and WICG#26 (as invalid / out of scope) by
deleting the section these issues applied to.
@frivoal
Copy link
Collaborator Author

frivoal commented Mar 22, 2018

closed by 27cdd49

@frivoal frivoal closed this as completed Mar 22, 2018
@frivoal frivoal added closed:invalid Off topic / out of scope / non actionable / already handled type:question Known unknows: things we need to investigate topic:spec labels Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed:invalid Off topic / out of scope / non actionable / already handled topic:spec type:question Known unknows: things we need to investigate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@frivoal @hugoholgersson