I pushed a prototype for a declarative onLoadRequest that covers the two cases where we actually need to ALLOW or DENY requests (from [comment 3](https://bugzilla.mozilla.org/show_bug.cgi?id=1734923#c3)): AMO & app links. My primary goals with this prototype were: 1. see if it was possible to cover these in GeckoView 1. see how practical the suggested API from [comment 0](https://bugzilla.mozilla.org/show_bug.cgi?id=1734923#c0) was A **non-goal was making the code readable/robust enough to land and make it work for every edge case.** I found 1) yes, it's possible (though I'm not sure what parts of an app link interception should be returned to the application) and 2) it's usable but clunky (it'd be less clunky with kotlin default arguments). I'm going to look into a few additional things before I request feedback.
Bug 1734923 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I pushed a prototype for a declarative onLoadRequest that covers the two cases where we actually need to ALLOW or DENY requests (from [comment 3](https://bugzilla.mozilla.org/show_bug.cgi?id=1734923#c3)): AMO & app links. My primary goals with this prototype were: 1. see if it was possible to cover these in GeckoView 1. see how practical the suggested API from [comment 0](https://bugzilla.mozilla.org/show_bug.cgi?id=1734923#c0) was A **non-goal was making the code readable/robust enough to land and make it work for every edge case.** I found 1) yes, it's possible (though I'm not sure what parts of an app link interception should be returned to the application) and 2) it's usable but clunky for app link's complex rules (it'd be less clunky with kotlin default arguments). I'm going to look into a few additional things before I request feedback.