You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if these will make it into version 1.0 or not. There are no real implementations of this available. Some things seem to still be in flux, such as its renaming recently.
In parent || child is parent always compared against col and child against td? What happens if specify something else: p || span?
Same question applies to :nth-col(), is the implied target td:nth-col() if you do something like .class:nth-col()?
There are a number of questions that I have which will need to be understood before this is implemented. There is also a bit of complexity involved here.
child must be verified to meet cell requirement and selector requirements.
parent must meet column requirement and selector requirements.
We would most likely:
verify that child is a td
verify location in row
crawl up and verify whether there are col tags in table header
capture appropriate column span considerations
determine td column and span based on captured info
calculate nth position and whether the td fits within the relation.
The text was updated successfully, but these errors were encountered:
Combinator || has been moved to a separate issue as it is specifically an "at-risk" feature. We still need better understanding to implement :nth-col and :nth-last-col, but this breaks up the tasks into more manageable pieces.
facelessuser
changed the title
Combination || and selectors :nth-col() :nth-last-col()
Selectors :nth-col() and :nth-last-col()
Jan 4, 2019
I don't know if these will make it into version 1.0 or not. There are no real implementations of this available. Some things seem to still be in flux, such as its renaming recently.
Inparent || child
is parent always compared againstcol
and child againsttd
? What happens if specify something else:p || span
?Same question applies to
:nth-col()
, is the implied targettd:nth-col()
if you do something like.class:nth-col()
?There are a number of questions that I have which will need to be understood before this is implemented. There is also a bit of complexity involved here.
col
tags in table headertd
column and span based on captured infotd
fits within the relation.The text was updated successfully, but these errors were encountered: