- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Sat, 08 Jun 2019 18:55:25 +0000
- To: public-css-archive@w3.org
> I don't understand why we need both a "spatial navigation starting point" and "search origin". In Chrome we only use "search origin". It's just a spec concept, it doesn't have to be directly reflected in the implementation. The HTML spec does the same for Tab navigation. Basically, how to determine the "search origin" is fully defined by the spec, but if the browser wants to use some heuristic to search from somewhere else in some cases, it sets the "starting point", and that overrides the "search origin". That's all there's to it. ---- I can see use cases where keeping the SearchOrigin even when it is offscreen will make things more intuitive, and others when it doesn't. I think it depends both on the layout of the document, and on what the user is doing and how they are navigating the page. I would tend to think that keeping it even when offscreen is less surprising, but I don't have data to back that up, and if most people think otherwise, we could switch. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3391#issuecomment-500151241 using your GitHub account
Received on Saturday, 8 June 2019 18:55:26 UTC