- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Aug 2017 10:41:04 +0000
- To: public-css-archive@w3.org
I've split out my idea for a property influencing the default navigation order to #1764, so it can be discussed separately. The tab group is a good idea to limit the indexes to a part of the element structure. It mitigates @jihyerish's issue about having to change the index of all following elements when inserting an element in between. It is still an issue for bigger groups, though. Another idea would be to combine both, relative and absolute indexing in one property. The syntax for that could then look like this: ```css nav-index: <integer> | after(<complex-selector>) ``` Allowing [complex selectors](https://drafts.csswg.org/selectors/#typedef-complex-selector) instead of only ID selectors also provides more flexibility and doesn't require to add IDs to the elements. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-325625502 using your GitHub account
Received on Tuesday, 29 August 2017 10:41:01 UTC