[csswg-drafts] [css-nav-1] Revise selecting best candidate policy (#3386) from Florian Rivoal via GitHub on 2018-12-03 (public-css-archive@w3.org from December 2018)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Dec 2018 07:53:45 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-386697603-1543823624-sysbot+gh@w3.org>

frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-nav-1] Revise selecting best candidate policy ==
---

Migrated from https://github.com/WICG/spatial-navigation/issues/94
Originally created by @junhoseo on *Mon, 20 Aug 2018 01:57:40 GMT*

---
Currently we consider distance and order in DOM structure. But sometimes these are not sufficient for reasonable choice.

Case 1:
![image](https://user-images.githubusercontent.com/4897376/44316189-4faa1980-a465-11e8-8e36-2b9077a52c29.png)

In above case, distance with active element is same each other. So blue element will be selected if it is earlier element in DOM tree, and yellow element will be selected on the contrary.

Case 2:
![image](https://user-images.githubusercontent.com/4897376/44316208-66507080-a465-11e8-9074-3a6b07fd4065.png)

![image](https://user-images.githubusercontent.com/4897376/44316263-add6fc80-a465-11e8-8437-687243208f80.png)

Sometimes a focusable element can be placed inside another focusable element. In this case, should we allow focus moving to opposite element? Opposite element is not placed in direction, but partially.



Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3386 using your GitHub account

Received on Monday, 3 December 2018 07:53:46 UTC