Cool! Thank you for making more of the platform testable in WPT! Has there been any discussion in the HTML spec community of making registerProtocolHandler an official "powerful feature <https://w3c.github.io/permissions/#powerful-features>"? Will doing so also have web visible implications via permissions policy <https://w3c.github.io/webappsec-permissions-policy/>?
Rick On Fri, May 13, 2022 at 6:12 AM Javier Fernandez <[email protected]> wrote: > Contact emails [email protected] > > Explainer > https://github.com/Igalia/explainers/blob/main/custom-protocol-handlers/Permission-API/README.md > > Specification > https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers > > Summary > > Provides Automated testing support for the registerProtocolHandler method, > so that we could avoid the user prompt dialog to grant permission for the > protocol handler registration. We would need to define a new > 'PermissionName' that we can use as part of the 'PermissionDescriptor' > argument for the SetPermission command provided by the WebDriver API. > > > Blink component Blink>HTML>CustomHandlers > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EHTML%3ECustomHandlers> > > Motivation > > Currently there are only manual tests in the WPT repository to cover the > registerProtocolHandler functionality. The main challenges to implement > automated testing are: * UserActivation: The registerProtocolHandler method > requires transient activation to consider the request; otherwise it'll be > ignored. * Permission prompt dialog: Although the spec is quite vague on > this regard, current implementations (Firefox and Chrome) requires the user > to grant permissions for the handler registration. Using the > test_driver.set_permission function we could make tests like this way: > promise_setup(async () => { await test_driver.set_permission({name: > 'protocol-handler'}, 'granted'); await test_driver.bless('handler > registration'); // Provides UserActivation register(); }); > > > Initial public proposal https://github.com/whatwg/html/issues/7920 > > TAG review > > TAG review status Pending > > Risks > > > Interoperability and Compatibility > > *Gecko*: No signal > > *WebKit*: No signal > > *Web developers*: No signals > > *Other signals*: > > WebView application risks > > No > > > Debuggability > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? No > > Flag name > > Requires code in //chrome? True > > Tracking bug https://bugs.chromium.org/p/chromium/issues/detail?id=1321073 > > Estimated milestones > > No milestones specified > > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5047679389270016 > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1ce0bb72-2b95-4e9a-f9bc-f1e156682811%40igalia.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1ce0bb72-2b95-4e9a-f9bc-f1e156682811%40igalia.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9jB5Afma_dbaRqMFyj3%3D7vyQpX2OrL%2Bf03sqAh3ykRXQ%40mail.gmail.com.
