W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2018

Re: [csswg-drafts] [css-nav-1] Revise selecting best candidate policy (#3386)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Dec 2018 07:53:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-443619268-1543823626-sysbot+gh@w3.org>
---

Migrated from https://github.com/WICG/spatial-navigation/issues/94#issuecomment-418079301
Originally created by @jihyerish on *Mon, 03 Sep 2018 10:56:58 GMT*

---
>  Case 1.

Yes. The focus will move depending on the DOM order if the candidates have the same distance from the active element.
So far, I think it's a reasonable result. But in some condition, it would be nice to consider the visual inclusion relation among the elements.

> Case 2.

In that regard, we need to consider the visual inclusion relation in this case.
If you see the sample below,
https://wicg.github.io/spatial-navigation/demo/sample/heuristic_text_type_elements.html
![image](https://user-images.githubusercontent.com/6636090/44983111-0c968d00-afb3-11e8-8a15-525c91f3c349.png)

The content area of the (A)`anchor element` with "spatial navigation" contains that of the (B)`anchor element` with "repository".
This causes that the focus cannot move from (A) to (B) nor from (B) to (A).

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3386#issuecomment-443619268 using your GitHub account
Received on Monday, 3 December 2018 07:53:49 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:55 UTC