| 00:12 | <bobbytables2> | someone knows why ParentNode.childElementCount is still a thing? |
| 00:17 | <jgraham> | Why not? |
| 00:18 | <bobbytables2> | it is redundant with children.length |
| 00:19 | <bobbytables2> | there was the intent to remove it, but it didn't happen https://bugzilla.mozilla.org/show_bug.cgi?id=673790 |
| 00:19 | <bobbytables2> | trying to understand the reason... |
| 00:39 | <jsbell> | bobbytables2: almost certainly it proved to be not web-compatible to remove |
| 00:40 | <jsbell> | bobbytables2: i.e. there was content out there using it and the attempt to remove it "failed" (i.e. people reported bugs to Moz so they reverted the removal) |
| 00:47 | <MikeSmith> | I don't remember ever seeing an intent to remove discussion about ParentNode.childElementCount anywhere |
| 00:48 | <MikeSmith> | at least not in recent memory |
| 00:49 | <MikeSmith> | kinda surprised it was ever even considered |
| 00:49 | MikeSmith | looks at https://bugzilla.mozilla.org/show_bug.cgi?id=673790 |
| 00:49 | <MikeSmith> | oh annevk |
| 00:50 | <MikeSmith> | I guess his heart was in the right place on that |
| 04:45 | <annevk> | I did not introduce it |
| 04:46 | <annevk> | Doug Schepers did in something I believe was called Element Traversal |
| 04:46 | <annevk> | Not entirely sure why nobody objected when implementing though |
| 05:21 | <Domenic> | I think in naive implementations at least it will be faster |
| 05:21 | <Domenic> | won't have to reify .children |
| 06:58 | <MikeSmith> | annevk: yeah didn't mean that you had introduced it but instead that you had tried to get it removed while there was still time |
| 07:04 | <annevk> | Seems like most things in DOM we tried to remove failed, but perhaps we overreached |
| 09:27 | <nox> | heycam|away: Are interfaces that support indexed properties supposed to always come with a length attribute? |
| 09:51 | <annevk> | nox: since I think you're in Europe, might be best to file issues instead |
| 09:52 | <nox> | annevk: Just did that. :) |
| 09:52 | <nox> | 3 of them. |
| 09:52 | <nox> | Ms2ger is trying to make an editor. I smiled and went away. |
| 09:53 | <annevk> | New but already too smart to fall for that old trick |
| 09:54 | <nox> | Ah ah. |
| 12:49 | <smaug____> | I have a bad feeling about this... is wpt testInIFrame racy |
| 12:53 | <MikeSmith> | http://stackoverflow.com/questions/34409254/are-messages-sent-via-worker-postmessage-queued |
| 12:58 | <smaug____> | the answer is yes |
| 12:58 | <smaug____> | but IIRC some implementations do have issues with queing |
| 12:58 | <smaug____> | at least when dealing with MessagePort |
| 12:59 | <smaug____> | (didn't test myself but baku was telling me that) |
| 16:27 | <Domenic> | Trivia question: is it possible for relative URL parsing to fail? E.g. can you find a string such that new URL(theString, location.href) throws? |
| 16:31 | <Ms2ger`> | jwalden, I think you were asking: http://stackoverflow.com/questions/34395981/dining-philosophers-from-rust-documentation-do-not-eat-concurrently |
| 16:33 | <Ms2ger`> | Domenic, var theString = "//[]" |
| 16:33 | <jwalden> | interesting |
| 16:33 | <Domenic> | Nice |
| 16:34 | <jwalden> | you guys gotta change that example to something that schedules less deterministically, IMO :-) |
| 16:34 | <Ms2ger`> | jwalden, patches welcome :) |
| 16:34 | <jwalden> | :-P |
| 17:15 | <MikeSmith> | smaug____: https://bugzilla.mozilla.org/show_bug.cgi?id=1213676 |
| 17:21 | <smaug____> | thanks |
| 21:35 | <zcorpan> | hmmm. can we add a linter that checks for trailing whitespace in source? |
| 21:42 | <MikeSmith> | zcorpan: sure we could |
| 22:36 | <MikeSmith> | so I notice that https://html.spec.whatwg.org/multipage/indices.html#all-interfaces is currently broken |
| 22:37 | <MikeSmith> | anybody know how long it's been like that? |
| 22:37 | <MikeSmith> | the spec build isn't emitting any errors about it |
| 22:38 | <MikeSmith> | it's just quietly failing to actually generate it |
| 22:47 | <Domenic> | MikeSmith: yeah annevk filed an issue about that a while ago :( |
| 22:47 | <MikeSmith> | ok |
| 22:47 | <Domenic> | https://github.com/whatwg/html-build/issues/37 |
| 22:47 | <Domenic> | We all felt hopeless in the face of the great wattsi |
| 22:47 | MikeSmith | looks |
| 22:47 | <MikeSmith> | hahah |
| 22:48 | <MikeSmith> | ah yeah I recall this now |
| 22:51 | <MikeSmith> | Domenic: we could replace the script with a static manually-maintained index in the source |
| 22:51 | <MikeSmith> | I think it would not be a big deal to keep it up to date |
| 22:51 | <Domenic> | Hmm |
| 22:51 | <Domenic> | I would really rather move in the direction of more automation... |
| 22:52 | <MikeSmith> | well if we wanted to, we could write a script that checks to make sure nothing's missing from it |
| 22:52 | <Domenic> | what about a script that generates it :) |
| 22:52 | <gsnedders> | MikeSmith: we could replace wattsi with something we understand |
| 22:53 | <gsnedders> | :trollface: |
| 22:53 | <MikeSmith> | well I guess I could adapt the current perl script to generate it pre-process |
| 22:53 | <Domenic> | I guess I wasn't clear why we couldn't just do the preprocessing before wattsi |
| 22:53 | <Domenic> | Then wattsi would take care of figuring out the correct URLs |
| 22:54 | <Domenic> | I see, "Doing this as a pre-process will likely not work since Wattsi seems to generate the IDs for partial interfaces." |
| 22:54 | <Domenic> | Maybe a targeted fix at that problem like adding some placeholder syntax for partial IDs that wattsi (or the script?) has to fill in. |
| 22:55 | <MikeSmith> | yeah |
| 22:55 | <MikeSmith> | I think that statement about not being able to do it pre-process is wrong |
| 22:55 | <MikeSmith> | I am pretty certain I can make it do it |
| 22:56 | <MikeSmith> | at the simplest level, we just make the script output, e.g., <code>BroadcastChannel</code> for each interface |
| 22:56 | <MikeSmith> | then as you said wattsi will figure out the rest |
| 22:57 | <MikeSmith> | anyway, I will try it |
| 22:57 | <Domenic> | The partial interfaces problem makes a bit of sense to me |
| 22:57 | <Domenic> | but yeah definitely doable |
| 22:57 | <Domenic> | thanks for fixing <3 |
| 22:57 | <Domenic> | or well, thanks for working on it <3. no promises yet i suppose :) |
| 22:58 | <MikeSmith> | yeah no promises |
| 22:58 | <MikeSmith> | and worst case we split the partial interfaces out to a separate Partial Interfaces section, and maybe maintain the manually for now |
| 22:59 | <MikeSmith> | hmm nah that would kinda suck I guess |
| 22:59 | <MikeSmith> | anyway I'll mess around with it |