-
This issue is split from https://github.com/microformats/microformats2-parsing/issues/9 intended to focus only on the process of normalizing URLs when parsing `u-*`.
[Current language](https://micr…
-
I've recently discovered that modern browsers don't implement the 4.10.21.2 Implicit submission spec correctly.
This bug was reported to ... here:
- Chromium: https://bugs.chromium.org/p/chromium/is…
-
See https://github.com/whatwg/html/issues/1440#issuecomment-299275463.
The interesting case here is a toplevel navigation which is triggered by browser chrome, for example through typing a URL in t…
-
Refs: https://github.com/nodejs/undici/issues/1203
Refs: https://github.com/nodejs/performance/issues/9
-
Some changes I want to make to the session history traversal spec (as part of https://github.com/whatwg/html/pull/6315) that may need their own discussion:
In the current spec, each history entry h…
-
From https://github.com/whatwg/html/pull/2991#discussion_r137139377
> If any of the invocations complete with null, we will get a fetch error, and bail out before "find the first parse error" is re…
-
### What is the issue with the HTML Standard?
When a document opens a popup (using something like `const popup = window.open(url)`), and that popup requires a [browsing context group switch](https:…
-
```
http://™%00/ mangles input. The input is considered invalid, but not echoed
literally but rather first encoded as utf-8 and then converted back to code
points using byte inflation rather than ut…
-
```
http://™%00/ mangles input. The input is considered invalid, but not echoed
literally but rather first encoded as utf-8 and then converted back to code
points using byte inflation rather than ut…
-
See @bzbarsky's comment at https://github.com/whatwg/html/pull/1107#issuecomment-253558923.
@bzbarsky could you explain in more detail how the current spec is wrong? Is the idea that the response sta…