Summary: | Fetch/XHR loads done by extensions should opt out of response sanitisation done in network process | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | youenn fablet <youennf> | ||||||
Component: | Page Loading | Assignee: | youenn fablet <youennf> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | achristensen, beidson, cdumez, ews-watchlist, japhet, timothy, webkit-bug-importer | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | WebKit Local Build | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Attachments: |
|
Description
youenn fablet
2020-07-21 01:54:02 PDT
Created attachment 404804 [details]
Patch
Created attachment 404806 [details]
Patch
Comment on attachment 404806 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=404806&action=review > Source/WebKit/WebProcess/WebPage/WebPage.cpp:7148 > + // FIXME: We should probably have this mechanism done between UIProcess and NetworkProcess directly. I agree, but since this will only be done for a few long-lived pages, this is ok for now. Committed r264664: <https://trac.webkit.org/changeset/264664> All reviewed patches have been landed. Closing bug and clearing flags on attachment 404806 [details]. |