-
Notifications
You must be signed in to change notification settings - Fork 473
Add and process reader view history entries #2879
Comments
We currently can't implement this without either new GV API or some web extension enhancements. Discussion continues in: https://bugzilla.mozilla.org/show_bug.cgi?id=1550144 |
@csadilek - snorp says you are working around this Reader View issue with an extension page. Is that correct or do you still need a new GV API or extension enhancements? |
@cpeterso Yes, using an extension page will improve reader view lot and also make navigation work. However, the link will be |
This is now also causing limitations in Fenix:
|
Can / should this be fixed before release? |
@mcarare I think we can address the two Fenix issues by using the original URL instead, as you mentioned. We don't have to extract (or parse) it, as it's already available in the browser store via @agi90 and I talked through options how to implement support for |
@agi90 pointed me to protocol headers https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/protocol_handlers which should be able to provide what we want e.g. a For sharing in Fenix, we would still want to use the original URL, as the receiver might not have |
After #2624 lands, we still need to add a history entry (
about:reader...
) when reader view is activated and add functionality to process it when navigating.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: