| 04:03 | <MikeSmith> | yoichio: one thing that might help slightly on https://github.com/w3c/selection-api/pull/81 is if you ask the W3C AC rep for Google, TV Raman, to add you as a member of the Web Platform WG |
| 04:03 | <MikeSmith> | ask kochi or somebody for help with that if you need it |
| 04:03 | <botie> | will do |
| 04:04 | <MikeSmith> | silly botie |
| 04:05 | <MikeSmith> | yoichio: I think it’s not strictly necessary for you to be a member of the WG (because Google has already made a blanket RF commitment for the group) but it will help as far as the related (more simple-minded) W3C tools go |
| 05:28 | <yoichio> | It seems the merge succeed |
| 05:48 | <MikeSmith> | yoichio: yes thanks for the ping |
| 05:48 | <MikeSmith> | though by the way whenever you need to my attention about something the best place to reach me is right here |
| 05:50 | <MikeSmith> | github notifications for me are mostly just noise. I get way too many of them to be able to keep up with them properly |
| 05:50 | <yoichio> | Thank you, too. |
| 05:51 | <MikeSmith> | wow https://bugs.webkit.org/show_bug.cgi?id=168774 SVN |
| 05:53 | <yoichio> | I see. I was just going to ping to Ryosuke. |
| 05:59 | <MikeSmith> | ah OK |
| 06:00 | <MikeSmith> | well he’s often around here too, as rniwa |
| 09:07 | <FND> | annevk, re `connectedCallback` order with nested custom elements (http://logs.glob.uno/?c=freenode%23whatwg&s=22+Feb+2017): |
| 09:07 | <FND> | based on https://developers.google.com/web/fundamentals/getting-started/primers/customelements#upgrades, I gather the correct way would be to use `:defined` and/or `whenDefined` |
| 09:07 | <FND> | which I suppose works because elements are upgraded synchronously (i.e. `connectedCallback` fires immediate after the respective `define` invocation)? |
| 12:57 | <annevk> | nox: https://github.com/whatwg/html/pull/2398 |
| 20:22 | <Domenic> | Thoughts welcome on whether we should specify a processing model for <link>'s rel="mask-icon"/color="" or just make it conformant with no processing model. https://github.com/whatwg/html/pull/2230#issuecomment-282396190 |
| 20:23 | <Domenic> | (Currently leaning toward conformant with no processing model) |
| 20:39 | <annevk> | I'd like a processing model at some point |
| 20:56 | <Domenic> | Even with only one vendor? |
| 21:00 | <annevk> | I guess it makes sense to wait for another |
| 21:02 | <Domenic> | Yeah... unsure whether there ever will be one, it's such a specific UI feature |
| 22:25 | <annevk> | I sometimes wish we'd call browsing contexts tabs |
| 22:25 | <AutomatedTester> | that would be awesome if we did |
| 22:27 | <jgraham> | No no no |
| 22:28 | <jgraham> | The whole Window-vs-the-UI-element thing already generates much confusion |
| 22:58 | <smaug> | hmm, about:blank#foo and session history handling |
| 23:54 | <MikeSmith> | Domenic: about the outline-algorithm view in the checker, dunno if you saw but at the end of last week I reverted the change I had made which caused it to show headings for sectioning roots |
| 23:55 | tantek | pops in and what - outline-algorithm? how is that still a topic of conversation or even in existence? or did I accidentally join a several year old log? |
| 23:55 | <MikeSmith> | so it’s back to being conformant representation of the what’s required by the outline algorithm |
| 23:56 | <MikeSmith> | tantek: because it’s in the spec and because I implemented it in the HTML checker |
| 23:57 | <tantek> | yeah that's probably one of the few parts of the WHATWG HTML that makes it look bad |
| 23:57 | <tantek> | talk about a solution looking for a problem |
| 23:58 | <annevk> | Hmm all browsers implement something there |
| 23:59 | <annevk> | They just did not implement this while they did implement corresponding style changes |