Intent to Ship: Allow Navigator.registerProtocolHandler to register "ftp"

[Asanka Herath]

Contact emails

asa...@chromium.org

Explainer

None

Specification

None

Summary

Add "ftp", "ftps", and "sftp" to the list of protocols available for registration via registerProtocolHandler(). FTP is now deprecated and will imminently be removed from the codebase. Allowing websites to register themselves as handlers for ftp:// URLs makes it possible to build easy to use gateways for legacy ftp sites. In addition we propose adding related protocols "ftps" and "sftp" to the list. Google Chrome/Chromium was not handling these URL schemes.

Blink component

Blink>HTML>CustomHandlers

Search tags

ftp, registerprotocolhandler

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None

The implementation gives precedence to native protocol handlers before consulting sites registered via registerProtcolHandler.

Gecko: No signal

WebKit: No signal

Web developers: No signals

Is this feature fully tested by web-platform-tests?

Yes. After crrev/2826871

Flag name

None

Tracking bug

https://crbug.com/1199027

Link to entry on the Chrome Platform Status

https://www.chromestatus.com/feature/5762628536238080

This intent message was generated by Chrome Platform Status.

[Frédéric Wang]

Le 14/04/2021 à 19:51, Asanka Herath a écrit :

SpecificationNone

Custom handlers schemes are defined here : https://html.spec.whatwg.org/multipage/system-state.html#safelisted-scheme

Can you please provide the link to the corresponding WHATWG discussion ?

Gecko: No signal

WebKit: No signal

WebKit does not support registerProtocolHandler, but Gecko does. Do they support / used to support these schemes natively ?

I think it would be good to get feedback from other browser developers on this change.

-- 
Frédéric Wang

[Asanka Herath]

Thanks for the nudge. I filed the following issues to gather feedback from Firefox and to make the spec change:

Firefox issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1705202

whatwg/html: https://github.com/whatwg/html/issues/6583 

-- 
Frédéric Wang

--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d69b6dc2-5d15-dd1f-0826-2dfde089711c%40igalia.com.

[Daniel Bratell]

On 2021-04-14 22:59, Asanka Herath wrote:

On Wed, Apr 14, 2021 at 2:43 PM Frédéric Wang <fw...@igalia.com> wrote:

Le 14/04/2021 à 19:51, Asanka Herath a écrit :

SpecificationNone

Custom handlers schemes are defined here : https://html.spec.whatwg.org/multipage/system-state.html#safelisted-scheme

Can you please provide the link to the corresponding WHATWG discussion ?

Gecko: No signal

WebKit: No signal

WebKit does not support registerProtocolHandler, but Gecko does. Do they support / used to support these schemes natively ?

I think it would be good to get feedback from other browser developers on this change.

Thanks for the nudge. I filed the following issues to gather feedback from Firefox and to make the spec change:

Firefox issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1705202

whatwg/html: https://github.com/whatwg/html/issues/6583

Recently we have nailed down a more well defined method for determining the opinion of other vendors. It's written down at https://bit.ly/blink-signals and includes where to request feedback (bug reports don't quite work as a way to get the official standings we've learned).

/Daniel

[Asanka Herath]

Thanks Daniel for the pointer! I filed an issue requesting Mozilla's position at https://github.com/mozilla/standards-positions/issues/513 .

- Asanka 

/Daniel

[Yoav Weiss]

Can you send a similar email to webkit-dev, asking them for their opinion? While they don't support protocol registration in general, it might be useful to get their opinion on it, and the make them aware that we are shipping additions to it, which people (presumably) find useful.

[Yoav Weiss]

Friendly ping! :)

[Yoav Weiss]

An even friendlier ping! :)

[Asanka Herath]

Thanks for the ping!

I got feedback from FF that this is "worth prototyping." I set Safari's views to N/A for now due to them not supporting the API. I just sent an email to webkit-dev to request their opinion either way. The Chromestatus entropy should be up-to-date with this info.

I'll add WebKit's views once I hear back from them.

- Asanka

[Daniel Bratell]

WebKit has not been interested in registerProtocolHandler previously so I'm not sure we can expect any proper analysis from webkit-dev about individual protocols.

/Daniel

[Chris Harrelson]

LGTM1

--
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 blink-dev+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f3c338a5-d062-8e71-1b4f-ed9c21f1c4a9%40gmail.com.

[Mike West]

LGTM2.

-mike

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9BRgPTtFNWM%3D%2BJUhDL7qdfj6avN5zzP-2Qqm3L8uFuWQ%40mail.gmail.com.

[Domenic Denicola]

It looks like Mozilla is on board with this per https://github.com/mozilla/standards-positions/issues/513. Would you be able to submit a HTML Standard pull request?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3DfsG4zCXhhRL73-B-B%3D72SSbnJ-RtbjdGt-6jvmgFK6zg%40mail.gmail.com.

[Rick Byers]

LGTM3

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN2PR13MB3232748958D551E764263781DF2A9%40MN2PR13MB3232.namprd13.prod.outlook.com.

[Asanka Herath]

Thanks all!

+Domenic Denicola : I added you to the existing PR which was waiting for a signal from FF which is now resolved.

[Javier Garcia Visiedo]

Hi all,

I'm revisiting this I2S, as the code changes were never merged probably due to ongoing spec discussions at the time. I'd like to ship these changes now. Please let me know if these LGTMs are still valid, or if you need any additional input from my side.

Thank you

Javier

[TAMURA, Kent]

The HTML specification was updated for this change, and we don't see any bad signals after the last discussion.  I think it's ok to land the implementation without re-approvals.

--

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 blink-dev+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6c83481d-483c-4562-8151-1933d3f6e91bn%40chromium.org.

--

TAMURA Kent
Software Engineer, Google

[Javier Garcia Visiedo]

Thank you Kent.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqGQ1asq8kuTug6WQ81ULgv4UXcbG8-mAO1Co8MY%2BwNX4w%40mail.gmail.com.