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
Curiously, if I paste the same link to the Obsidian Reader that I open through the Obsidian Web Clipper extension (moz-extension://.../reader.html), the page is now properly parsed.
HighWire keeps the inactive full-text view, and each section inside it, at display:none until that view is selected. removeHiddenElements deletes elements whose inline style matches those hidden patterns, so the .fulltext-view subtree is removed, and .fulltext-view was not an entry point, so the visible abstract article remained the content root.
.fulltext-view is now matched in the same ENTRY_POINT_ELEMENTS slot as [role="article"], below article and above main.
Activity
qbilius commentedon May 6, 2026
Curiously, if I paste the same link to the Obsidian Reader that I open through the Obsidian Web Clipper extension (moz-extension://.../reader.html), the page is now properly parsed.
qbilius commentedon Sep 8, 2026
Here's my workaround in case others have a similar issue. In the template, I have the following conditional clause:
mvanhorn commentedon Oct 4, 2026
HighWire keeps the inactive full-text view, and each section inside it, at display:none until that view is selected. removeHiddenElements deletes elements whose inline style matches those hidden patterns, so the .fulltext-view subtree is removed, and .fulltext-view was not an entry point, so the visible abstract article remained the content root.
.fulltext-view is now matched in the same ENTRY_POINT_ELEMENTS slot as [role="article"], below article and above main.