Lensari

Known Issues — Fine Print

Last updated: April 5, 2026

This page lists known limitations in the current version of Fine Print. We publish these so you know what to expect and can work around them while we improve the extension.

Current known issues

1. Navigate may miss target on framework-heavy sites

Severity: Minor Status: Planned for v1.1

On sites that heavily use React, Vue, or similar frameworks (e.g., some banking or SPA sites), clicking Navigate may scroll to the wrong location. This happens because the framework destroys and recreates page elements between scan time and navigation. The finding itself is accurate — only the scroll target is affected.

2. Pages discussing legal terms may produce false matches

Severity: Minor Status: v2 (AI layer)

Blog posts or articles that discuss terms of service, privacy policies, or legal language may trigger findings because the text contains the same phrases the scanner looks for. The scanner cannot distinguish between a page that uses concerning terms and a page that discusses them. The planned AI analysis layer in v2 will add this contextual understanding.

3. Major sites may use non-standard HTML for legal pages

Severity: Minor Status: Mitigated

Some major sites (Google, Meta) wrap all text in <div> elements with obfuscated class names instead of semantic HTML. Fine Print includes a fallback that collects text from non-semantic elements when fewer than 5 standard elements are found.