It looks like "tr_open" tokens have their "map" property populated only if they are inside the "thead" of a table, while "tr_open" tokens inside the "tbody" section of the table don't have their "map" property populated.
It would be useful if all "tr_open" tokens got their "map" properties populated so that scroll synchronization solutions that are built on top of that could reliably map table rows too.
It looks like "tr_open" tokens have their "map" property populated only if they are inside the "thead" of a table, while "tr_open" tokens inside the "tbody" section of the table don't have their "map" property populated.
It would be useful if all "tr_open" tokens got their "map" properties populated so that scroll synchronization solutions that are built on top of that could reliably map table rows too.