Mike West

@wanderview: I agree! The change I was considering was related to the set of options that the `cache `attribute of the `RequestInit` argument to the `fetch()` API would accept, not...

@yutakahirano: Fetching `url + random junk` would end up evicting `url + random junk` from the cache, not `url`. The claim here is that some `cache` option values allow probing/evicting...

Sorry for the delayed response @shhnjk; it's been a long few weeks... I continue to prefer patching URL and dealing with the problem there. Given that opinions there apparently haven't...

@eligrey: In an ideal world, I agree with you.

> The parser can close these elements without their end tag sooner than The End Yeah. I'm discovering that while poking at a toy implementation. Parsing is complicated. :)

@bzbarsky: I agree about ``, and I'm actually not that concerned about submitting a form that hasn't been closed; I'm more concerned about submitting a text sink (like those mentioned...

Thanks, @hsivonen! > That said, I'm less worried about marking some DOM nodes broken but keeping the tree the same. I agree with your general concerns about changing the parser....

> * Parser-created textarea and select nodes are flagged as "do not submit". > * When the parser processes the end tag for textarea or select, it unsets the "do...

> No, that can be bypassed with `novalidate`. I was more interested in reusing the `invalid` event to inform developers that something's gone wrong than in matching validation behavior. I...

Sure, I'm happy with `error`. I'm putting together a prototype in Blink that we can use to collect some metrics about how often this would trigger... Let's see what the...