XHR runs encoding detection on the response body if - The response type is "json", and - The response body has BOM. This is a spec violation. The spec requires us to always use UTF8 when the response type is "json" in https://xhr.spec.whatwg.org/#dom-xmlhttprequest-response.
Contact emails
yhi...@chromium.orgExplainer
NoneSpecification
https://xhr.spec.whatwg.org/Summary
XHR runs encoding detection on the response body if - The response type is "json", and - The response body has BOM. This is a spec violation. The spec requires us to always use UTF8 when the response type is "json" in https://xhr.spec.whatwg.org/#dom-xmlhttprequest-response.
Blink component
Blink>Network>XHRTAG review
None - This is a very small fix.TAG review status
Not applicableRisks
Interoperability and Compatibility
WebKit matches with our current behavior and Firefox matches with the spec, but the compatibility risk is low, given the low count.
Gecko: Matching with the spec (https://wpt.fyi/xhr/json.any.html)
WebKit: No signal (https://bugs.webkit.org/show_bug.cgi?id=223441)
Matching with our current behavior.
Web developers: No signals See the following for the existing usage. https://www.chromestatus.com/metrics/feature/timeline/popularity/3858Is this feature fully tested by web-platform-tests?
Yes
Flag name
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1189627Link to entry on the Chrome Platform Status
https://www.chromestatus.com/feature/5686951464140800This intent message was generated by Chrome Platform Status.
--
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/CABihn6ERcKBsEKvrxKUX%2BntVDLfgdLduC8FUN%2BTHSiFNQigzZA%40mail.gmail.com.
What's the planned deprecation period?
On Thu, Jun 17, 2021 at 1:24 PM Yutaka Hirano <yhi...@chromium.org> wrote:Contact emails
yhi...@chromium.orgExplainer
NoneSpecification
https://xhr.spec.whatwg.org/Summary
XHR runs encoding detection on the response body if - The response type is "json", and - The response body has BOM. This is a spec violation. The spec requires us to always use UTF8 when the response type is "json" in https://xhr.spec.whatwg.org/#dom-xmlhttprequest-response.
Blink component
Blink>Network>XHRTAG review
None - This is a very small fix.TAG review status
Not applicableRisks
Interoperability and Compatibility
WebKit matches with our current behavior and Firefox matches with the spec, but the compatibility risk is low, given the low count.
Gecko: Matching with the spec (https://wpt.fyi/xhr/json.any.html)
WebKit: No signal (https://bugs.webkit.org/show_bug.cgi?id=223441)I think this is too small to spam webkit-dev with a position, but it would be good to let them know on the issue that we're planning to follow Firefox.
Matching with our current behavior.
Web developers: No signals See the following for the existing usage. https://www.chromestatus.com/metrics/feature/timeline/popularity/3858Is this feature fully tested by web-platform-tests?
YesCan you link to the existing tests that we're failing?
On Thu, Jun 17, 2021 at 10:39 PM Yoav Weiss <yoav...@chromium.org> wrote:What's the planned deprecation period?I would like to change the behavior immediately, given the low use-counter number.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfULnUov0O_L4kxeasBXQUoWzAkxX6v9yvdbppzYC%3DnDKA%40mail.gmail.com.