WHATWG
2025-02-14
plaintext logs
prev next
source on github
19:03
<TabAtkins>
Hm, I'm digging into the exact multipage-splitting abilities HTML has, and I notice that the nav (on line 65 of the source) is set to w-nosplit, but definitely shows up in the multipage. Is that a fault in wattsi, or is the multipage nav getting generated by something else?
19:42
<devgianlu>

Hello, while implementing support for the autocomplete attribute on form associated elementes I stumbled upon a possible issue: the WPT tests assume that the field value will be transformed to be lowercase, but I could not see where it is explictly stated. All I can see is that the comparisons should be case insensitive. It seems to work fine if at step 15 I also perform lowercasing.

Spec: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill-processing-model
WPT test: https://github.com/web-platform-tests/wpt/blob/master/html/semantics/forms/the-form-element/form-autocomplete.html
Implementation PR: https://github.com/LadybirdBrowser/ladybird/pull/3517

21:08
<jmdyck>
TabAtkins: Similarly, the ToC and Full ToC are marked w-nosplit, but appear in the multipage edition.
21:08
<TabAtkins>
I'm wondering if w-nosplit just doesn't actually do anything in Wattsi currently
21:13
<jmdyck>
The "This specification is like no other etc" is marked w-nosplit, and isn't in the multipage, which at first appears to be a case of w-nosplit working, except it's also marked w-dev, which excludes multipage anyway.
21:15
<jmdyck>
The code doesn't seem to have any useful occurrences of "nosplit".
21:16
<jmdyck>
hm, maybe it does.