05:49
<annevk>
Domenic: was added per https://www.w3.org/Bugs/Public/show_bug.cgi?id=13154 which seems to have had at least some interest from Mozilla
05:51
<annevk>
Ah, looks like you found that too
08:36
<zcorpan>
botie: inform smaug____ <input type=range multiple> should give the widget two handles. as a data point, the audience really liked this feature when LeaVerou presented it at CSSDay.nl (she wrote a polyfill for it). https://leaverou.github.io/multirange/
08:36
<botie>
will do
10:02
<zcorpan>
maybe we should move the IDL stuff from the obsolete section into the main IDL block, with "// obsolete" instead?
10:02
<botie>
smaug____, at 2016-07-08 08:36 UTC, zcorpan said: <input type=range multiple> should give the widget two handles. as a data point, the audience really liked this feature when LeaVerou presented it at CSSDay.nl (she wrote a polyfill for it). https://leaverou.github.io/multirange/
10:05
<smaug____>
zcorpan: right. <input type=range multiple> has been in the spec for years and no one has implemented it
10:05
<zcorpan>
smaug____: yeah
10:19
zcorpan
goes offline until august 9th, reachable on twitter
10:22
<annevk>
ah yeah, I'm away next week, not sure if I'm reachable, will have to find out
10:33
<smaug____>
happy holidays
11:28
<smaug____>
hmm, have people started to use sync XHR more again
11:29
<smaug____>
at least I think I've seen more sync XHR usage related bugs
11:44
<hsivonen>
annevk: yeah, we are not *finally* allowed to depend on SSE2 being available, but unconditionally depending on SSE4 being available is not OK
11:45
<hsivonen>
annevk: well, more precisely, right now, we are allowed to depend on SSE2 on Mac and Windows, but Linux getting dragged closer to the present day is just a matter of time
11:47
<hsivonen>
I expect Mozilla-official builds for Linux to start requiring SSE2 when Rust becomes mandatory at the latest
11:58
<Ms2ger>
s/not/now/
13:29
<gsnedders>
(OS X never shipped on any Intel hardware without SSE2, did it?)
13:29
<gsnedders>
(Oh, SSE2 is even older than I remembered. Definitely didn't, then.)
13:44
<nox>
https://w3c.github.io/IndexedDB/#dom-idbfactory-open
13:44
<nox>
When in the spec is the IDBOpenDBRequest's done flag set to true...?
14:22
<annevk>
nox: I recommend filing bugs for all grievances
14:22
<nox>
Ok.
14:22
<annevk>
nox: jsbell should be able to fix them
14:22
<annevk>
nox: but his timezone is suboptimal
14:23
<nox>
Moon Time?
14:23
<annevk>
SF
15:26
<smaug____>
Domenic: FWIW, createDocument seems to return XMLDocument (in case you were thinking about removing that interface)
15:44
<annevk>
smaug____: see issue against DOM Standard
17:05
<annevk>
I'd like a topic that covers browsing context / document lifecycle
17:06
<annevk>
And maybe one for event loop?
17:06
<annevk>
There's still quite a bit of handwaving there
17:56
<__n0aaaaa>
Hello, could someone explain me what they mean by API base URL in https://www.w3.org/TR/XMLHttpRequest/#dom-xmlhttprequest-open
17:56
<__n0aaaaa>
is it location.href?
17:56
<__n0aaaaa>
or location.origin?
17:56
<__n0aaaaa>
the context being a browser
17:57
<__n0aaaaa>
http://w3c.github.io/html/webappapis.html#api-base-url
17:57
<__n0aaaaa>
doesn't help me much either
18:00
<__n0aaaaa>
no one knows?
18:04
<__n0aaaaa>
…I guess it's not the right place to ask for help regarding specification
18:04
<__n0aaaaa>
:/
18:19
<TabAtkins>
Domenic: I'll check it out (re: [CEReactions])
18:20
<TabAtkins>
Domenic: https://html.spec.whatwg.org/multipage/scripting.html#cereactions is a "dfn" type. It needs to be "extended-attribute".
18:20
<TabAtkins>
Oh shoot,nm.
18:20
<TabAtkins>
It is that.
18:21
<TabAtkins>
But I guess plinss doesn't yet have the "handle arbitrary new definition types" code. :/
18:21
<TabAtkins>
I'll bug him and get that added to the list explicitly, at least.