Re: [csswg-drafts] Please add "tab-index" to CSS specification

```
<form>
   <input type="text" name="any1" />   
   <input type="text" name="any2" />   
   <input type="text" name="any3" />   
   <input type="text" name="any4" />  
   <input type="text" name="any5" />
</form>

input[type="text"]:nth-of-type(2n)
{
   tab-index: 1;
   width:300px;
}
input[type="text"]:nth-of-type(2n+1)
{
   tab-index: 2;
   width:300px;
   display:block; /* to break the line */
}
```

It cannot be modified via nav-pre and nav-next without addition of identifiers (modify of markup).

ray() is also bad for scrolled pages with fixed-positioned elements. the ray() can be resolved differently in this case due to scrollbar position. It also cannot be resolved if width of site isn't constant and part of elements is displayed as inline-table or inline-block (or inline for non-replaced elements with tabindex set to equal or greater than 0). 

The nav-index/tab-index hasn't these problems. 

I always starting coding of page write the markup (HTML) for the page SEMANTICALLY. Next Iwant to use CSS (and only CSS if it is possible). Next step: required JS if client needs to reload fragment of page etc.). I like to use ::after, ::before, advanced CSS. I'm annoying when I must change markup (and thus part of CSS) to add additional ID's, <DIV/>s etc.

For example we have WordPress, Drupal AUTOUPDATED page, we want only use CSS to change visual effects. These visual effects result in chaotic tabbing. What is the best solution? We have not ID on all controls. the ray() is in part of layouts not constant (fixed-positioned elements). 
If the page is autoupdated (to security fixes) your IDs can be removed during update but CSS not if is correctly linked (in appropriate file that is not updated). 

-- 
GitHub Notification of comment by Nadya678
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-324344072 using your GitHub account

Received on Wednesday, 23 August 2017 14:07:38 UTC