Open Bug 1705202 Opened 3 months ago Updated 3 months ago

Add FTP related protocols to the registerProtocolHandler safelist.

Categories

(Core :: Networking: FTP, enhancement, P2)

enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: asanka, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

As a part of removing FTP support in Chromium (and in turn Google Chrome, Edge, etc.) I'd like to release ftp, sftp, ftps protocols as being registrable via registerProtocolHandler.

ChromeStatus entry is here: https://www.chromestatus.com/feature/5762628536238080

I'll follow up with relevant PR to whatwg/html and wpt.

Blink I2S thread is https://groups.google.com/a/chromium.org/g/blink-dev/c/ABhlioapE0E/m/gXL84wPfAAAJ . Please express your support objections here or there as appropriate.

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

Hi Asanka. You should file an issue on https://github.com/mozilla/standards-positions/issues to get a position on this topic.
I'll keep this bug for necessary changes if we reach a decision.

Blocks: kill-ftp
Severity: -- → S3
Flags: needinfo?(annevk)
Priority: -- → P2
Whiteboard: [necko-triaged]

Ah, I saw this after the GitHub issue. 😊 This seems reasonable to me now FTP is no longer a scheme the browser handles.

Flags: needinfo?(annevk)
Blocks: 1056860
You need to log in before you can comment on or make changes to this bug.