Bug 149416
| Summary: | Please allow WKWebView to control Do Not Track | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Stefan Arentz <stefan> |
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | andersca, ap, ddkilzer, mjs, sam, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 9 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Stefan Arentz
It would be great if the WKWebView had an option to enable the DNT header.
Either globally or per WKWebView.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
As Brady mentioned, support for Do Not Track was removed in Safari on iOS 13 and macOS 10.14. It’s also a failed standard that no major websites supported.
<https://twitter.com/bradeeoh/status/1211535779748405250>
Maciej Stachowiak
Probably the best path forward for this would be a general feature to let WKWebView clients add custom headers. I don't think we'd resurrect built-in DNT support. Also I wouldn't recommend browsers implementing it.
Radar WebKit Bug Importer
<rdar://problem/58363446>
Stefan Arentz
Apologies for the confusion, this was not a request to introduce DNT back into Safari.
It is only a request to allow third-party browsers (like Firefox in this case) to make an independent decision to enable this header in the WKWebView.
A general feature to let WKWebView users set arbitrary headers sounds like a great solution. As long as these custom headers are not just sent for the main frame. They would have to go to resource on the page.