- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 May 2019 19:52:00 +0000
- To: public-css-archive@w3.org
I agree that "navigate" is problematic, because of its potential for confusion with [`Navigator`](https://developer.mozilla.org/en-US/docs/Web/API/Navigator) and URL navigation. The problem extends beyond this particular property to all the interface names. E.g. `NavigationEvent` sounds to me like something that should be triggered when the user clicks a URL. Adding adjectives doesn't seem to simplify things, especially when you want this to be a very generic framework for directional _or_ sequential movement of focus _or_ viewport. Throwing out some potential names (forgive me if these have previously been discussed & discarded): - view or contentView (con: view already has plenty of meanings in the web platform which are similar but not the same) - browse (con: although the word is not used in web platform APIs, it could still be confused with browsing to a different URL) - explore (pro: name implies that you are looking around the content that is already loaded; name not already used in the web platform; con: "Windows Explorer" and "Internet Explorer" might interfere with SEO) I like "explore". You're exploring the page. You can explore to the left, you can explore up or down, but you can also explore next or previous items in a list. You can explore only focusable items, or all content. For other API names, `exploration` could replace `spatialNavigation`, e.g., `ExplorationEvent`, `getExplorationContainer()` or `ExplorationDirection`. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3387#issuecomment-489219560 using your GitHub account
Received on Friday, 3 May 2019 19:52:01 UTC