Skip to content
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.

window.history.go / back fire OnNavigating handler on Android #168

Open
Daddoon opened this issue Mar 6, 2020 · 2 comments
Open

window.history.go / back fire OnNavigating handler on Android #168

Daddoon opened this issue Mar 6, 2020 · 2 comments
Assignees
Labels
area-blazormobile The task is specific to BlazoMobile bug Something isn't working

Comments

@Daddoon
Copy link
Owner

Daddoon commented Mar 6, 2020

window.history.go / back, fire OnNavigating handler on Android .

This is related on how Webextension works with the onbeforerequestevent.

@Daddoon Daddoon added bug Something isn't working area-blazormobile The task is specific to BlazoMobile labels Mar 6, 2020
@Daddoon Daddoon added this to the BlazorMobile Task ideas milestone Mar 6, 2020
@Daddoon Daddoon self-assigned this Mar 6, 2020
@Daddoon
Copy link
Owner Author

Daddoon commented Mar 6, 2020

Same issue here related : piroor/newtabfromlocationbar#18 (comment)

@Daddoon
Copy link
Owner Author

Daddoon commented Mar 6, 2020

Some documentation : https://stackoverflow.com/questions/45139926/how-to-check-if-a-tab-has-been-reloaded-in-background-js

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts

As we can’t enforce some behavior between the webnavigation api and webrequest api, one solution is to inject a content_script that wrap the window.history API, and notify the background worker that the next request is coming from the history from JavaScript, and that the request can be executed without check.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazormobile The task is specific to BlazoMobile bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant