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
The buildSelector function takes its cues directly from the request, but these do not always match the browser. For example, editing this file, using firefox 56:
This specific case seems simple (if not clean) to fix, by splicing ["tbody",1] into ancestry when there's a table that isn't followed by one of thead, tbody, or tfoot, when the browser is known to add the tag. The general case, though, is clearly bullshit. I don't know which browsers add which implicit tags under which conditions, and even if I did, keeping that list updated would be a nightmare.
Thoughts?
The text was updated successfully, but these errors were encountered:
The buildSelector function takes its cues directly from the request, but these do not always match the browser. For example, editing this file, using firefox 56:
Trying to update "one", will fail with with
TypeError: target is null
. The problem is solved if I make the implicittbody
tag explicit, though.This specific case seems simple (if not clean) to fix, by splicing
["tbody",1]
intoancestry
when there's atable
that isn't followed by one ofthead
,tbody
, ortfoot
, when the browser is known to add the tag. The general case, though, is clearly bullshit. I don't know which browsers add which implicit tags under which conditions, and even if I did, keeping that list updated would be a nightmare.Thoughts?
The text was updated successfully, but these errors were encountered: