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-443619266-1543823626-sysbot+gh@w3.org>

Migrated from https://github.com/WICG/spatial-navigation/issues/94#issuecomment-425187209
Originally created by @hugoholgersson on *Thu, 27 Sep 2018 18:00:08 GMT*

> Usually, such green element never gets focus because it is encapsulated

The problem is that spatnav only looks _outside_ of activeElement's visual **box**, right?

> Also we define starting point as edge of active element.

Perhaps this is all we need to do (no need for an extra "internal" step)?

I wonder if we ever need to use the complete "focus **box**".... Perhaps [edges](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/page/spatial_navigation.cc?q=function:OppositeEdge&sq=package:chromium) as search origin give good enough approximations for most (all?) distance calculations?

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

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:40 UTC