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:48 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-443619263-1543823626-sysbot+gh@w3.org>

Migrated from https://github.com/WICG/spatial-navigation/issues/94#issuecomment-430495322
Originally created by @frivoal on *Wed, 17 Oct 2018 05:34:33 GMT*

I think there are several issues being discussed at the same time in this one. Separating them into sub topics: 

* case 1 form https://github.com/WICG/spatial-navigation/issues/94#issue-351959505 is now here: https://github.com/WICG/spatial-navigation/issues/121

* Prioritizing fully or mostly aligned elements is now here: https://github.com/WICG/spatial-navigation/issues/122

As for the rest, which I think is best described in https://github.com/WICG/spatial-navigation/issues/94#issuecomment-425004503, I think I was actually confused when I said I agreed. In https://github.com/WICG/spatial-navigation/issues/94#issuecomment-425004503, if the green box is in the same container as the other boxes, the specification already handles that. However, if it is not in the same container, then it seems that skipping it is a feature, not a bug. That is what containers are for. If that's not desired, then making the "blue" box in that example a container seems like a mistake.

Is there any situation where we would want the blue box to be a container, but still go from red to green?

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

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