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

Migrated from https://github.com/WICG/spatial-navigation/issues/94#issuecomment-425300127
Originally created by @junhoseo on *Fri, 28 Sep 2018 02:23:22 GMT*

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

Yes. Spatnav looks outside of activeElement, also looks partially insersecting element. But never looks inside 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 as search origin give good enough approximations for most (all?) distance calculations?

I think using edge as search origin in common cases can minimize unreachable problem. But it maybe reduce intuitiveness. For example, in above scenario, left(apricot? color) and right(yellow color) can be candidate when we hit down key. It looks like such elements are not placed in direction. Of course, it depends on the person. What do you think?

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

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