00:01
<rniwa>
Domenic: hm... scrollTo works synchronously
00:02
<rniwa>
Domenic: I think it's really the navigation that can't really be sync
00:02
<Domenic>
Hmm OK, so I guess instant scroll probably still has some value
00:03
<Domenic>
So you think it's important that given <span id="foo">, span.scrollIntoView() and clicking <a href="#foo"> behave differently?
00:03
<rniwa>
Domenic: i don't think it's important per se
00:03
<rniwa>
Domenic: in fact, it's probably better their behavior aligned
00:03
<rniwa>
Domenic: I'm just saying that it's not what iOS safari does
00:03
<Domenic>
Ah OK
00:04
<rniwa>
Domenic: and it apparently is hard to fix on our end
00:06
<rniwa>
Domenic: oh... actually, i might be completely off here.
00:06
<rniwa>
Domenic: I think what's happening is that on iOS, we do sync scroll in the task scheduled by a task scheduled by clicking on an anchor
00:07
<rniwa>
Domenic: so you have to do nested setTimeout(~, 0) to get to after the scrolling whereas on other browsers, a single setTimeout(~, 0) would suffice
00:07
<Domenic>
oh fascinating
00:07
<Domenic>
yeah i was just trying to track down how many tasks are posted during navigation
00:08
<rniwa>
Domenic: yeah, it's really tricky there because it goes though
00:08
<rniwa>
follow a hyperlink: https://html.spec.whatwg.org/#following-hyperlinks-2
00:08
<rniwa>
navigate: https://html.spec.whatwg.org/#navigate
00:08
<rniwa>
navigate to a frament: https://html.spec.whatwg.org/#scroll-to-fragid
00:08
<rniwa>
follow a hyperlink: https://html.spec.whatwg.org/#following-hyperlinks-2
00:08
<Domenic>
yeah, navigation is a known quagmire :(
00:08
<Domenic>
annevk's been cleaning it up bit by bit
00:11
<rniwa>
Domenic: I think it's supposed to have a single task there
00:11
<Domenic>
Yeah I found the one in "follows a hyperlink" and can't find any others
00:11
<rniwa>
Domenic: right
01:24
<MikeSmith>
Domenic: are there no open browser feature-implementation bugs for <script type=module>?
01:25
<MikeSmith>
OK found https://bugs.chromium.org/p/chromium/issues/detail?id=594639 at least
01:26
<MikeSmith>
Domenic: how I can make the HTML spec show the annotation with a link to the bug?
01:27
<MikeSmith>
if I add https://html.spec.whatwg.org/multipage/webappapis.html#module-script in a comment, would that do it?
01:27
<MikeSmith>
or does it need to be https://html.spec.whatwg.org/multipage/#module-script
01:32
MikeSmith
goes to read the build sources
01:35
<MikeSmith>
d’oh nm I realize it doesn’t do that at all, it just looks at W3C bugzilla and caniuse
01:47
<MikeSmith>
raised https://bugs.webkit.org/show_bug.cgi?id=166405
07:30
<hsivonen_>
Is there an online view of git blame for the HTML spec?
07:30
<hsivonen_>
(too large for github)
07:50
<MikeSmith>
hsivonen: there is not, as far as I know
07:56
<hsivonen>
MikeSmith: thanks
07:56
<hsivonen>
blame appears to be very slow even locally
07:57
<hsivonen>
this could use an online service that caches blame for each rev
07:58
<MikeSmith>
yeah
08:34
<tobie>
annevk: are all ByteStrings, USVStrings and all USVStrings, DOMStrings?
08:35
<annevk>
tobie: they are conversions, so not really, but in a way, perhaps
08:36
<tobie>
annevk: that's helpful. :D
08:40
<annevk>
tobie: ByteString should convert to a byte sequence I think, open issue
08:41
<annevk>
tobie: USVString should convert to a string and DOMString too; I guess these could use the same string type
08:42
<tobie>
annevk: I'm trying to define the acceptable types for toJSON return values
08:43
<tobie>
annevk: my assumption is that all records would be, regardless of which string type is used as key
08:47
<tobie>
annevk: it could have been kind of nice to have a special type for that so you could say: record<stringType, SerializableType>, etc.
08:47
<zcorpan>
maybe my English intuition is wrong but i thought "any ... objects whose constructor was" was correct. any opinions? https://github.com/whatwg/html/pull/2207#discussion_r93528785
08:48
<tobie>
annevk: but that seems super hard to define and make work across union types, distinguishability and the like. Anyway.
08:49
<tobie>
zcorpan: http://wasorwere.com/
08:51
<zcorpan>
tobie: the question is really "constructor" vs "constructors" -- was vs were falls out of that
08:52
<zcorpan>
with my intuition, "constructors" implies each object can have multiple constructors
08:53
<tobie>
zcorpan: oh, right, apologies.
09:00
<MikeSmith>
nox: am curious was Url serde impls is
09:00
<nox>
MikeSmith: What?
09:00
<MikeSmith>
https://github.com/servo/rust-url/pull/263/commits/146aee3e1eb1db5d917a23dbdf90e68b2a20c369
09:00
<MikeSmith>
「Slightly improve Url serde impls」
09:01
<nox>
MikeSmith: serde is Rust's serialisation framework.
09:01
<MikeSmith>
ah OK
09:01
<annevk>
tobie: why? This is post-conversion. You can only use on of these pre-conversion.
09:01
<nox>
MikeSmith: Our impls for Url used to allocate an intermediate String for nothing on serialisation, and panic on parse errors instead of returning them.
09:01
<annevk>
tobie: they are not distinguishable and such
09:02
<MikeSmith>
nox: this loooks nicer
09:02
<tobie>
annevk: not sure what you mean.
09:02
<MikeSmith>
nox: it did not expose the error description before?
09:03
<nox>
MikeSmith: Worse, it just panicked. :)
09:03
<nox>
MikeSmith: .unwrap() takes the v in Ok(v) of a result, and panics otherwise.
09:03
<MikeSmith>
ah OK
09:04
<MikeSmith>
not so familiar with “panic” it this context… means it fails hard? does not now how to recover? or ..
09:06
<MikeSmith>
*know how
09:06
<tobie>
annevk: what return type should `toJSON()` have when you'll rely on the abstract operation that rounds up all the attributes?
09:08
<jgraham>
MikeSmith: Typically panic is "terminate the process immediately"
09:08
<jgraham>
For some value of "immediately"
09:08
<MikeSmith>
ok
09:09
<MikeSmith>
I call that “catch fire and fail”
09:09
<MikeSmith>
because that is how it is described in the XML world
09:09
<jgraham>
(although see also https://doc.rust-lang.org/std/panic/fn.catch_unwind.html)
09:09
<MikeSmith>
and I am all about XML
09:09
<MikeSmith>
XML Forever
09:10
<MikeSmith>
XML, Right or Wrong
09:10
jgraham
backs away slowly
09:10
<annevk>
tobie: record<>?
09:11
MikeSmith
goes back to composing replies on xml-dev threads
09:11
<tobie>
annevk: record<DOMString, any?> ?
09:11
<tobie>
annevk: record<DOMString, any>
09:11
<annevk>
tobie: yeah
09:12
<annevk>
tobie: will have more time starting Tue
09:12
<tobie>
annevk: np
09:12
<tobie>
annevk: take care till then
09:15
<annevk>
You too 🎄
09:19
<nox>
Do you folks know about any spec using NodeIterator with filters not coming from script?
09:21
<nox>
And was URLMismatchError removed from all the specs?
09:30
<nox>
Also, do any specs have double, boolean or null constants?
09:52
<tobie>
nox, I wish we had a DB of all WebIDL snippets across all specs
09:53
<zcorpan>
nox: i don't think so. i can only find https://dxr.mozilla.org/mozilla-central/source/dom/webidl/Console.webidl#44
13:30
<MikeSmith>
annevk: thanks for digging up the thread about apple-touch-icon
13:31
<MikeSmith>
did not know that chrome supported it too
13:42
<Ms2ger>
Domenic, around?
17:47
<TabAtkins>
Domenic: Ugh, yeah, I'm gonna go add a warning to Position, Microsoft picked it up and then immediately dropped it.
17:47
<Domenic>
Yay
18:16
<TabAtkins>
Domenic: Warning is live, sorry it took me so long to make that fix.
18:16
<TabAtkins>
Should have been done months ago.