08:01
<hsivonen>
Domenic: I think I've now addressed the Encoding Standard test case issues that were blocking on me.
09:29
<annevk>
Yay, no Encoding Standard changes needed
11:36
<makmm>
Is this the correct place to ask for the fetch function?
11:36
<makmm>
to ask questions about the fetch function*
11:40
<annevk>
makmm: sure is
11:40
<makmm>
Okay, I'm trying to get fetch to fetch from localhost:3000 to localhost:8080/data
11:41
<makmm>
But it gives NetworkError and doesn't even send the request
11:43
<makmm>
I just tried with axios library too, and it does the same, so ignore what I said :P
11:43
<makmm>
sorry
11:44
<ondras>
annevk: I am observing some unexpected rendering when using tab-size: https://jsfiddle.net/32x8e19v/2/ do you think it works as expected?
11:44
<ondras>
it renders the same in ff and chrome
11:45
<ondras>
hm, and it does the same stuff even without tab-size. so apparently it is related to how the generated content mixes with tabs?
12:11
<annevk>
I'm not sure, I worked on tab-size forever ago
12:12
<ondras>
@annevk: tab-size is probably a red herring :/
12:12
<ondras>
@annevk: I am probably more concerned about the general "tab" semantics in this case
12:13
<ondras>
@annevk: do you think there is some spec that covers this behavior?
12:15
<annevk>
ondras: I guess I don't understand what you think is wrong
12:15
<ondras>
I see.
12:16
<ondras>
let me rubberduck this for a moment to see if I am able to articulate what I think is wrong.
12:16
<annevk>
ondras: afaik CSS defines everything I'm seeing
12:18
<ondras>
@annevk: yeah, okay. I *thought* that <tab> behaves as a plain sequence of 0x20 chars, but it apparently maintains its tab-stop nature. Well, lesson learned.
12:19
<ondras>
(also, it screws tab-based code indentation when a ::before content is generated)
12:19
<annevk>
ondras: the initial value of tab-size is not 1
12:20
<annevk>
ondras: ooh, tab stops, hmm, maybe it does
12:20
<annevk>
I don't really recall that
12:21
<annevk>
Heh, MDN links to my email proposing tab-size: https://lists.w3.org/Archives/Public/www-style/2008Dec/0009.html
12:21
<ondras>
:P
12:21
<ondras>
almost 10 years ago
12:21
<ondras>
but tab-size is definitely not related to this. <tab> implementation for white-space:pre is.
12:22
<annevk>
And https://drafts.csswg.org/css-text-3/#white-space-phase-2 defines the tab stop behavior
12:22
<ondras>
@annevk: cool, thanks!
12:42
<annevk>
smaug____: I guess rniwa might be at TPAC; I wonder if hayato is around and can give feedback on https://github.com/whatwg/dom/issues/525#issuecomment-342179455
13:10
<smaug____>
yeah
13:10
<smaug____>
hayato: ^
15:05
<annevk>
I wonder if the W3C mailing list search infrastructure got updated
15:05
<annevk>
MikeSmith: do you know?
15:05
<annevk>
It seems rather crappy at the moment
15:08
<bradleymeck>
is this the right place to ask about web-platform-tests?
15:09
<annevk>
bradleymeck: yeah, there's also #testing on irc.w3.org:6667
15:12
<bradleymeck>
annevk: it seems that https://github.com/w3c/web-platform-tests/blob/master/html/semantics/scripting-1/the-script-element/serve-with-content-type.py#L12 is ignored on some condition and defaults to application/octet-stream. I'm trying to figure out why / if this is known about
15:12
<bradleymeck>
i haven't found a reliable minimal case though :-/
15:14
<annevk>
bradleymeck: how did you determine it becomes application/octet-stream? Through developer tools, network sniffer?
15:15
<bradleymeck>
devtools and curl
15:15
<bradleymeck>
if I serve an empty file it always appears to be respected though
15:16
<annevk>
bradleymeck: maybe you get application/octet-stream in case the script fails somehow, e.g., if you forget to provide a required parameter
15:17
<bradleymeck>
wait nm, I think Is ee whats going on. I need to rewrite the import specifier to go through that file
15:17
<bradleymeck>
I see*
15:17
<annevk>
cool
15:18
<bradleymeck>
tyty
15:19
<bradleymeck>
annevk: are making tests w/ loops to keep them somewhat dry discouraged?
15:27
<Ms2ger>
Not particularly
15:28
<annevk>
bradleymeck: no I love those
15:29
<annevk>
bradleymeck: when there's many tests I might even end up describing them all in an external JSON resource so they can be reused across various types of implementations
15:29
<annevk>
bradleymeck: that's how URL parser tests are done and also some data URL / MIME type parser stuff I'm working on
15:30
<bradleymeck>
kk
17:04
<Domenic>
hsivonen: awesome thanks, hopefully r12a can make the test changes.
17:28
<MikeSmith>
annevk: about mailing-list search getting updated recently, yeah I think it might have
17:29
<MikeSmith>
what specifically is bad/different about it now?
17:29
<MikeSmith>
slow?
17:39
<tantek>
MikeSmith: too much noise?
17:41
<MikeSmith>
noise?
17:44
<annevk>
MikeSmith: if I search for "template svg" sans quotes with list public-webapps I get worse results than Google
17:44
<annevk>
MikeSmith: I used to get excellent results for stuff like that
17:45
<MikeSmith>
OK, thanks
17:45
<MikeSmith>
will find out what changed there and if we can revert it
17:48
<MikeSmith>
> will take a look. It does seem less effective than it used to be
17:49
<MikeSmith>
⬆ response for the mailing-list expert on the systems team
17:49
<MikeSmith>
*response from
17:50
<Domenic>
w3cmemes is back and better than ever https://w3cmemes.wordpress.com/
17:50
<sangwhan>
annevk: do you have any input on localizable strings? Going to i18n in a bit
17:51
<sangwhan>
(Aside from what is already on GH)
17:51
<annevk>
sangwhan: I'm primarily concerned about a) implementer interest and b) getting a consistent story across APIs
17:52
<annevk>
MikeSmith: thanks!
17:52
<sangwhan>
I'm mostly trying to propose a solution that is syntactic so no explicit implementor support is needed
17:52
<annevk>
sangwhan: if nobody is going to implement it you're wasting your time
17:53
<sangwhan>
Any changes to the JSON format are a no go, TAG is firm on this
17:53
<sangwhan>
annevk: yeah, which is why I'm pushing for a solution hoisted on what we already have
17:53
<annevk>
sangwhan: I mean in the sense of one language per field, is any implementer actually planning on providing dedicated UX for that? Why did nobody push for that in HTML?
17:54
<annevk>
sangwhan: the syntax doesn't really matter, what matters is how much complexity do you add to an API that takes a couple of strings
17:54
<sangwhan>
annevk: Good question, probably fell through the cracks
17:54
<annevk>
sangwhan: and how compatible is that with existing solutions (see HTML and Notifications API)
17:56
<sangwhan>
Right, will bring those points up.
18:03
<annevk>
sangwhan: ta!
18:27
<annevk>
smaug____: curious what you make of https://groups.google.com/a/chromium.org/d/msg/blink-dev/z6ienONUb5A/F5-VcUZtBAAJ
18:27
<smaug____>
annevk: what in particularly
18:27
<annevk>
smaug____: (it would be interesting if that comparison also compared multiple ways of listening for those events)
18:28
<annevk>
smaug____: basically the performance numbers of callbacks vs events
18:28
<smaug____>
ok, let me read that again and think a bit
18:36
<Domenic>
I assume it's based on the O(n)-ness
18:43
<annevk>
Still seems like a rather large difference
18:56
<smaug____>
1 vs 4 is quite expected.
18:56
<smaug____>
One could still use events just the same way as observer by having resize events to fire on window and the event would contain list of resize changes
18:57
<smaug____>
but yeah, for cases when we want to call JS a lot from C++, we need to have some batch, and if there isn't need for dom propagation, observer approach is ok
19:17
<MikeSmith>
annevk: ⬇️
19:17
<MikeSmith>
> there is mechanism to reindex a given list
19:17
<Domenic>
annevk: so is https://github.com/whatwg/html/pull/3141 good to go?
19:17
<MikeSmith>
> public-webapps index should be fixed. I will take a look at others and maybe rebuild all of them.
19:30
<annevk>
Domenic: with a follow-up issue or PR, yes
19:30
<annevk>
Domenic: maybe MikeSmith can approve the PR for me
19:30
<Domenic>
Hmm, I still think base URL is the right name for that primitive, but OK. Can you approve then?
19:31
<annevk>
The primitive is the URL of the resource
19:32
<annevk>
It happens to be the base URL
19:32
<MikeSmith>
annevk: which PR?
19:32
<annevk>
If in the future you get <base> for JS (let’s not), you’d need a base URL primitive
19:32
<annevk>
MikeSmith: 3141
19:33
annevk
is stuck under a baby
19:34
<MikeSmith>
hai done
19:36
<annevk>
Ta
19:44
<sangwhan>
annevk: how do you feel about simplifying forms? (e.g. removing unimplemented validations, move that to scripts)
19:54
<annevk>
sangwhan: what is not implemented? File an issue I guess
19:57
<annevk>
Domenic: I hope you will file that follow up issue
20:11
<sangwhan>
annevk: Don't remember from the back of my head, trying to get http://w3c.github.io/test-results/html/all.html to work
20:13
<sangwhan>
...why is this all in one page :(
20:13
<sangwhan>
Oh my god, this is really old.