Meta: Reader view

[pocmo]

The consensus seems to be that GeckoView will not provide any reader view functionalities / APIs. Instead it is recommended to provide this functionality as a WebExtension loaded into GeckoView. The extension would make use of Readability.js.

Since this is something that we would want in other apps using GeckoView and in order to have a consistent experience, it makes sense to wrap this in a feature component.

MVP:

• Expose API to app for running readability.js on current page
• Expose readerable API / Callback for current page to app

After MVP scope:

• Expose reader view UI (or the API hooks for a native UI)
  • Color scheme (Dark, Sepia, Light)
  • Font (Sans-serif, Serif)
  • Font size (+ / -)

Depends on:

• WebExtensions functionality in engine component
  • GeckoView: https://bugzilla.mozilla.org/show_bug.cgi?id=1511077
• Extension<->App messaging API (as WebExtension API)
  • GeckoView: https://bugzilla.mozilla.org/show_bug.cgi?id=1518843

GeckoView WebExtensions Meta:
https://bugzilla.mozilla.org/show_bug.cgi?id=1468844

Related

• Components wrapping WebExtensions? #1791 - Components wrapping WebExtensions? (DONE)
• Add reader view feature component #1346 - Add reader view feature component (DONE)
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1509257
• Expose state: "Is this page viewable in reader view?" #1385 - "Is this page viewable in reader view?" (DONE)
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1509258
• Add engine API for WebExtension messaging #2243 - Add engine API for WebExtension messaging (DONE)
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1518843
• ReaderView: Wire up messaging between feature and web extension #2624 - Wire up messaging between feature and web extension (DONE)
• Create customizable ReaderView appearance UI #2623 - Create customizable Appearance UI (DONE)

┆Issue is synchronized with this Jira Task