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.

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

[css-nav-1] Improve the name of window.navigate #120

Closed
frivoal opened this issue Oct 17, 2018 · 2 comments
Closed

[css-nav-1] Improve the name of window.navigate #120

frivoal opened this issue Oct 17, 2018 · 2 comments
Labels
needs:feedback The editors would like feedback from more people before resolving topic:spec type:question Known unknows: things we need to investigate

Comments

@frivoal
Copy link
Collaborator

frivoal commented Oct 17, 2018

Previously in #70, we discussed whether window.navigate() was a great name for this API or not. It seems like it could be confused with navigating to a new URL, so some better name would be good.

However, no suggestion so far seems to work:

  • focusNavigate() or other names invoking focus are wrong, because it can also scroll things instead of focusing them
  • directionalNavigate() or spatialNavigate() or similar are also problematic, because this method should be possible to extend to sequential navigation by passing it a "prev" or "next" argument, and that does not work with such names.

So, leaving this issue open to see if we can do better.

@frivoal frivoal added type:question Known unknows: things we need to investigate topic:spec needs:feedback The editors would like feedback from more people before resolving labels Oct 17, 2018
@hugoholgersson
Copy link

stepFocusOrScroll

@frivoal frivoal changed the title Improve the name of window.navigate [css-nav-1] Improve the name of window.navigate Dec 3, 2018
@frivoal
Copy link
Collaborator Author

frivoal commented Dec 3, 2018

Issue migrated to w3c/csswg-drafts#3387

@frivoal frivoal closed this as completed Dec 3, 2018
@WICG WICG locked and limited conversation to collaborators Dec 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs:feedback The editors would like feedback from more people before resolving topic:spec type:question Known unknows: things we need to investigate
Projects
None yet
Development

No branches or pull requests

2 participants