New issue
Advanced search Search tips

Issue 807562 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
yhirano@chromium.org
foolip@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Align with Fetch on data: URLs

Project Member Reported by annevank...@gmail.com, Jan 31 2018 
See https://fetch.spec.whatwg.org/#data-urls.

Tests have been reviewed and landed as well: https://github.com/w3c/web-platform-tests/pull/6890.

(I think you might have a couple more specific issues already, but it seemed reasonable to file one anyway given that these tests cover more than the individual issues I think.)

Comment 1 by foolip@chromium.org, Jan 31 2018 

Anne, are there specific bits of this that you'd deem more important to align on than the others? Maybe how "base64" is parsed?

Comment 2 by annevank...@gmail.com, Jan 31 2018 

I think there have been issues with all parts, and it's not too big of an algorithm, so all of it would be good.

Comment 3 by ricea@chromium.org, Feb 2 2018

Cc: yhirano@chromium.org
Status: Available (was: Unconfirmed)
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/external/wpt/fetch/data-urls/base64.any-expected.txt: 4 failures. Looks like we don't like \f in data: URLs.

https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/external/wpt/fetch/data-urls/processing.any-expected.txt: 26 failures. Appear to be mostly related to mimetype normalisation, which IIRC is known to be weird. I think yhirano@ did some work on the mimetype algorithm recently, so I will CC him.
►

Sign in to add a comment