00:01:02 http://w3c-test.org/tools/runner/index.html 00:02:42 plh: cut-off date for substantive changes is May 31st 00:12:51 RRSAgent, make minutes 00:12:51 I have made the request to generate http://www.w3.org/2016/05/11-html-editors-minutes.html AlexD 00:22:54 http://w3c.github.io/html-aria/ 05:02:30 AlexD has joined #html-editors 17:06:34 RRSAgent has joined #html-editors 17:06:34 logging to http://www.w3.org/2016/05/11-html-editors-irc 17:06:48 Topic: The fun of checking WHATWG commits… 17:07:00 -> https://github.com/whatwg/html/commits/master?page=11 our starting point… 17:07:12 scribe: Travis 17:07:32 Present+ chaals, Léonie, Travis, Arron, Alex, Ade, PLH 17:08:09 LJWatson has joined #html-editors 17:16:29 zakim, agenda? 17:16:29 I see 2 items remaining on the agenda: 17:16:30 7. reviewing whatwg changes [from chaals] 17:16:30 8. pull/350 [from plh] 17:16:39 plh: will need to get pre-implementation info prior to June 21 (so that we can mark at risk) 17:16:44 scribe: Travis 17:17:29 wait! Let's talk about current/cached Bikeshed 17:18:02 arronei: Recent Bikeshed update now has an "index out of range" in a biblio file. 17:18:10 .. only seems to happen in Travis.ci 17:18:13 .. ?? 17:18:28 .. reached out to Tab. Still don't know what the problem is. 17:18:36 .. (problem with Travis.ci?) 17:18:55 .. Have changed to use live Bikeshed to workaround this issue. 17:19:12 .. want to continue investigating how to use the cached copy. 17:19:23 .. but want to fix the license issue and some links. 17:19:50 adrianba: I want to try to help fix this technical issue. 17:20:11 .. we have seen that we can't rely on the live Bikeshed. It causes too many issues. 17:20:25 plh: we're only talking about the editor's draft, not the publishing process. 17:20:46 adrianba: We're protecting ourselves by using Travis.ci to ensure we build clean. 17:20:59 .. so that folks' PRs can be checked and clean. 17:21:21 .. when we started out using the live version it was chaos (Bikeshed was updated a lot and broke us.) 17:21:36 .. we can do a temp workaround. 17:22:17 .. add something to the repo readme to say that we're currently working on the live version; if [customer] has an issue, let us know. 17:22:58 arronei: hope to be able to fix in about a week.. 17:24:37 agenda? 17:24:49 take up agendum 7 17:26:16 Will be reviewing issue now. 17:28:51 plh has joined #html-editors 21:49:41 RRSAgent has joined #html-editors 21:49:41 logging to http://www.w3.org/2016/05/11-html-editors-irc 22:00:07 rrsagent, this meeting spans midnight 22:00:17 Topic: references 22:00:26 PLH: CSS-backgrounds is OK 22:00:39 AE: We can reference CSS-color-3 not 4 22:01:23 AE: CSS generated content will not stabilise soon enough, ditto all the CSS references following that until CSS-style-attr. 22:01:31 PLH: CSS syntax should be OK. 22:02:30 … text is not stable, nor transitions. TL: Why isn't transitions done - it's old. 22:02:41 [but doesnt' work interoperably] 22:03:05 AE: UI3 is OK, 4 no. value is stable. Writing modes is stable but moves slowly. 22:03:14 PLH: Link to CSS 2.2 instead of 2.1? 22:03:42 Content is not stable, images is. 22:03:53 CSS-Ruby isn't stable. 22:10:27 ACTION: PLH to publish a Working Draft of DOM serialisation. 22:12:11 [editing] is unstable, encoding we should shift version, fetch is going to be interesting.] 22:13:20 PLH: WebAppSec convinced the director that they could point to fetch. We would need to examine where we reference fetch. 22:15:04 … An alternative is to say "we're just going to copy definitions into a spec appendix, so we don't have to worry about things shifting" 22:15:15 AD: There are only 4 places we refer to Fetch. 22:17:51 CMN: Can we just drop the dependencies 22:19:05 PLH: FileAPI was accepted for 5.0 22:19:44 … is fullscreen normative? 22:20:28 AE: I'll check to see if things are real normative references. 22:20:45 … think we use Geometry spec. 22:21:01 PLH: HR-Time 1 is good enough. 22:23:25 ARIA reference needs to be sorted, to point to the right one and make sure it advances in time. 22:23:51 … why tdo we reference Japanese layout requirements. 22:24:09 … Why do we reference MathML 1.01? 22:27:09 Why is media-source normative? 22:28:27 - because it extends HTML. 22:28:54 … MIME sniffing we need 22:29:53 … why do we depend normatively on OggSkeleton? 22:31:33 PLH: Selectors 4 - where is that? 22:31:42 AAE: We depend on that. 22:32:02 PLH: Service workers as a normative ref? 22:32:07 AE: We may not need to do that? 22:33:23 AD: Clean up SVG stuff 22:33:33 … no need for 1.2tiny or 1.0 22:33:43 PLH: Should we reference Pointer Events? 22:34:59 … URL is nasty… 22:35:40 ACTION: Chaals to figure out how we point to URL concepts. 22:35:59 AD: We don't need TypedArray anywhere. 22:38:02 AE: WebIDL should point to /TR not haycam's repo. Maybe it's the reference text. 22:39:00 … webworkers and whatwgwiki aren't normative dependencies. 22:39:12 … no idea why we have worklets. 22:39:51 … XHR link is a bug. 22:41:41 … SO, URL, Fetch, DOM, are the likely pain points. 22:45:16 s/URL is nasty/URL is nasty so we should try to keep it as-is/ 22:45:42 s/URL, Fetch, DOM/Fetch, DOM/ 22:51:48 Topic: Looking at diff 22:52:20 Section 4.7.14.12.6 should be marked at risk 22:52:53 Section 4.7.14.12.9 should be marked at risk? 22:53:17 + associated event handlers 22:59:01 datetime and datetime-local at risk? 23:00:41 inputmode? 23:03:52 Drop 4.10.19.3 Autofill 23:08:03 plh will look into section 4.11 and figure what we should drop or mark at risk 23:09:27 and also section 4.12 23:13:40 Editing is a mess, and known to be a mess, but there isn't much of a solution available now :( 23:25:45 rrsagent, make minutes 23:25:45 I have made the request to generate http://www.w3.org/2016/05/11-html-editors-minutes.html chaals