You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all navigation is blocked within webview and navigation must be handled component user. Would be good to create a navigation policy where developers could state that I want to be able to navigate within this domain or based on some other rules.
Above increases navigation history correctly so goBack, goForward, canGoBack, and canGoForward are updated correctly but it feels that this is upside down. By default we should allow navigation to everywhere and that could be limited by some rules.
Based on quick check it looks that network protocol handlers could be unregistered/registered during runtime. This would already be better approach.
Currently all navigation is blocked within webview and navigation must be handled component user. Would be good to create a navigation policy where developers could state that I want to be able to navigate within this domain or based on some other rules.
Could you'd need to do it like this:
Above increases navigation history correctly so goBack, goForward, canGoBack, and canGoForward are updated correctly but it feels that this is upside down. By default we should allow navigation to everywhere and that could be limited by some rules.
Based on quick check it looks that network protocol handlers could be unregistered/registered during runtime. This would already be better approach.
See:
uriloader/exthandler/nsExternalHelperAppService.cpp
These are just ideas / food for thought.
The text was updated successfully, but these errors were encountered: