| 00:16 | <Hixie> | Domenic: which instructions? |
| 00:34 | <Domenic> | Hixie: when you email the subscribe address |
| 00:35 | <Domenic> | Hixie: basically, try to subscribe to whatwg and you'll see it's pretty bad |
| 01:13 | <Hixie> | ah |
| 01:13 | <Hixie> | yeah |
| 01:13 | <Hixie> | dunno what to do about it |
| 01:14 | <Hixie> | Domenic: wait, why is it bad |
| 01:14 | <Hixie> | Domenic: can't you just reply to the e-mail and be done with it? |
| 01:16 | <Domenic> | Hixie: those instructions don't work either. They contradict themselves. The reply to address is different from the one in the body and they tell you to have only that string. Try it. |
| 01:16 | <Hixie> | ok, i sent an e-mail ta whatwg-subscribe⊙wo |
| 01:16 | <Hixie> | i got back an e-mail |
| 01:16 | <Hixie> | i replied to it |
| 01:17 | <Hixie> | now i'm subscribed |
| 01:17 | <Hixie> | i don't understand the problem |
| 01:17 | <Hixie> | i mean, other than the e-mail mentions the website, which doesn't work |
| 01:27 | <Domenic> | Hmm replying didn't work for me |
| 01:27 | <Domenic> | And the reply-to didn't match the instructions in the body of the email |
| 01:27 | <Domenic> | Are there three separate ways to confirm subscription, only one of which works? |
| 01:28 | <Domenic> | Instructions in body for emailing whatwg-request don't work |
| 01:28 | <Domenic> | Clicking on the link doesn't work |
| 01:28 | <Domenic> | But replying does? |
| 01:29 | <Hixie> | there are three, two of which should work |
| 01:29 | <Hixie> | i haven't tried whatwg-request |
| 01:31 | <Hixie> | (the url will work too, you just have to use a browser that doesn't have HSTS information blocking that host) |
| 01:32 | <Hixie> | i sent a help command to whatwg-request⊙wo and that worked too, fwiw |
| 01:53 | <estellevw> | Trying to full understand the "is" attribute, but having a hard time searching for such a popular term. Anyone have a link to a good explanation and the spec? |
| 01:53 | <estellevw> | s/full/fully |
| 01:54 | <estellevw> | just had to ask so that i could find it. http://w3c.github.io/webcomponents/spec/custom/#instantiating-custom-elements |
| 01:54 | <estellevw> | never mind |
| 01:56 | <estellevw> | though if anyone has a good article, that's appreciated |
| 05:14 | <Domenic> | Hixie: hmm my bad, I typoed "request" :( |
| 05:17 | <Hixie> | heh |
| 09:50 | <jsx> | @counter-style is part of css3, right? |
| 10:09 | <Ms2ger> | It's part of CSS, yes |
| 10:19 | <jsx> | ok, Ms2ger, just wanted to make sure its correct if i tag it as CSS3 in MDN |
| 10:19 | <Ms2ger> | That's not particularly useful, but *shrug* |
| 10:21 | <jsx> | alright.. i thought that might help if someone is searching for CSS3 specific things |
| 10:22 | <annevk> | jsx: CSS3 is not a thing per the CSS WG |
| 10:22 | <jsx> | oh! ok |
| 10:23 | <annevk> | jsx: so if we pretend that CSS3 is a thing in MDN, we might want to overhaul that |
| 10:23 | <annevk> | jsx: and instead focus on modules |
| 10:23 | <jsx> | nope, i'm removing it rightaway |
| 10:23 | <jsx> | thanks for the info |
| 10:29 | <jsx> | annevk: is it a political thing like how the whatwg calls it html while the w3c calls it html5? or is this universal. (sorry, i'm very new to this) |
| 10:30 | <Ms2ger> | jsx, no, this is the CSSWG's call, actually |
| 10:31 | <annevk> | jsx: while CSS 2.1 was still being developed, CSS3 (at the time still a thing) was developed in the form of modules |
| 10:31 | <Ms2ger> | jsx, they have version numbers for individual modules, but "CSS3" as a general thing doesn't exist |
| 10:31 | <annevk> | jsx: however, some of those modules turned out to advance quicker than CSS3 as a whole |
| 10:31 | <annevk> | jsx: so versioning (leveling in CSSWG terms) became scoped to modules, rather than CSS |
| 10:32 | <jsx> | like "CSS Counter Styles Level 3" annevk? |
| 10:32 | <annevk> | jsx: exactly |
| 10:32 | <annevk> | jsx: http://www.xanthir.com/b4Ko0 has an explanation from TabAtkins |
| 10:32 | <Ms2ger> | TIL: Chrome still doesn't support setting event types to the empty string |
| 10:32 | <Ms2ger> | Speaking of which... |
| 10:32 | <Ms2ger> | annevk, r? https://github.com/w3c/web-platform-tests/pull/1342 :) |
| 10:33 | <jsx> | thanks annevk, Ms2ger |
| 10:33 | <Ms2ger> | Np |
| 10:33 | <annevk> | Ms2ger: I take it you ran these through a browser already? |
| 10:34 | <Ms2ger> | Er |
| 10:35 | <Ms2ger> | Looks like I broke one since the last time I did |
| 10:36 | <annevk> | Ms2ger: createEvent table does not match https://dom.spec.whatwg.org/#dom-document-createevent |
| 10:38 | <annevk> | Ms2ger: reviewed |
| 10:38 | <Ms2ger> | Thanks |
| 10:38 | <Ms2ger> | Looks like TouchEvent isn't supported in Fx? |
| 10:38 | <Ms2ger> | Oh, I guess it might be preffed off |
| 10:40 | <Ms2ger> | annevk, again? :) |
| 10:40 | <annevk> | Ms2ger: again? |
| 10:40 | <Ms2ger> | I added the missing ones |
| 10:41 | <annevk> | Ah, done |
| 10:41 | <Ms2ger> | Thanks |
| 10:41 | <annevk> | I thought I had said something stupid somewhere |
| 10:43 | <Ms2ger> | No no :) |
| 12:59 | <annevk> | Hixie: stylesheet on whatwg.org has "padding; 0;" |
| 12:59 | <annevk> | Hixie: same stylesheet (tabbed-pages) also has -moz-outline which is dropped in Firefox Nightly |
| 14:59 | <Ms2ger> | The descriptions of those old DOM tests are pure poetry |
| 14:59 | <Ms2ger> | An document type accessed, setNodeValue is called with a non-null argument, but getNodeValue |
| 14:59 | <Ms2ger> | should still return null. |
| 15:53 | <TabAtkins> | annevk: That blog post gets so much mileage. |
| 21:48 | <SimonSapin> | TabAtkins: the things about URLs like css4-backgrounds could be updated, I guess |
| 21:48 | <SimonSapin> | though it might still be relevant for some TR snapshots |