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
When a block of content links to table content where named anchors are used, the mobile view (stacked table) content takes precedence over the desktop view content.
stacktable.js duplicates the table content into a hidden table which displays when the mobile mode is engaged. However, the named anchor assumes priority based on its position in the DOM, even though the table isn't displayed.
Have you encountered this use case before?
Suggestion
I think the plugin should change the names of anchors embedded in table code when the table is hidden, and revert them to the original when the table is visible. Can you think of an alternate solution?
When I have time, I could try to submit a pull request. But if you've already solved the problem I would greatly accept your solution. ;-)
The text was updated successfully, but these errors were encountered:
I had a similar problem, with duplicate of ID - I have at table some form's elements like Checkbox etc. I solve this problem by simple script - adding prefix "sec_ " for all "ID" and "FOR" attributes:
Issue
When a block of content links to table content where named anchors are used, the mobile view (stacked table) content takes precedence over the desktop view content.
Example
Behaviour
stacktable.js duplicates the table content into a hidden table which displays when the mobile mode is engaged. However, the named anchor assumes priority based on its position in the DOM, even though the table isn't displayed.
Have you encountered this use case before?
Suggestion
I think the plugin should change the names of anchors embedded in table code when the table is hidden, and revert them to the original when the table is visible. Can you think of an alternate solution?
When I have time, I could try to submit a pull request. But if you've already solved the problem I would greatly accept your solution. ;-)
The text was updated successfully, but these errors were encountered: