Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

Original Article ↗ Hacker News Discussion ↗

Keyboard shortcuts and UX

  • Many comments vent about sites hijacking Ctrl+F, /, Ctrl+K, etc., calling it confusing and hostile when browser-standard behavior changes.
  • Some argue it’s sometimes necessary for virtualized/SPA content where all text isn’t in the DOM, but others still find it infuriating.
  • Distinction is made between document-like pages (shouldn’t override) and full web apps (overrides and custom palettes can be acceptable if accessibility is handled well).
  • Suggested mitigations: press shortcut twice to fall back to browser search, allow users to configure/disable app shortcuts, or avoid conflicts with major browser bindings.
  • A few people note browser features and settings that disable page-level shortcut overrides.

Browser support and standardization

  • Scroll-to-text fragments now work in current Chrome/Chromium, Edge, and very recent Firefox releases; Safari lags on some JS APIs.
  • Firefox ESR and mobile versions don’t support it yet, leading to debate over what counts as “reliable” or “broad” support.
  • Brave disables the feature over privacy concerns about linkability and observation of where a page scrolls.
  • The specification lives in a W3C incubator group, not yet on a formal standards track, but has tests and is treated as de facto standard by major browsers.

Use cases and benefits

  • Widely appreciated for: pointing out typos, deep-linking to specific sentences/footnotes, and making long documentation easier to reference.
  • Some users forget the feature exists, but those who use browser “Copy link to highlight” love it; extensions fill creation gaps in Firefox.
  • Especially useful when you don’t control the target page or it lacks meaningful IDs.

Concerns and drawbacks

  • Some dislike search engines auto-inserting fragments that jump to parts of a page they didn’t intend to see.
  • On heavy pages (e.g., Confluence), the scroll/highlight can be delayed, which users find annoying.
  • A minority thinks text fragments may confuse users on unsupported browsers or when content changes; recommending also quoting the target text in surrounding context.

Developer and implementation notes

  • Questions raised about combining #:~:text= with other fragment parameters and integrating with Web Annotations.
  • Chromium-only header Document-Policy: force-load-at-top can disable this behavior but is underspecified and not cross-browser.
  • Some imagine extended APIs for programmatic access to highlighted regions, but others see this as too niche for heavy investment.