07:59:57 RRSAgent has joined #html
07:59:57 logging to https://www.w3.org/2018/06/19-html-irc
08:00:11 Meeting: HTML F2F meeting
08:00:27 Chair: Chaals
08:01:13 present+ Chaals, Steve, Léonie, Bruce, Sanghwan, Job, Scott, Xiaoqian
08:01:21 rrsagent, make minutes
08:01:21 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
08:01:29 rrsagent, set logs world visible
08:07:38 zakim, clear agenda
08:07:38 agenda cleared
08:07:40 xiaoqian has joined #html
08:07:44 agenda: https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/18-06-html.md
08:10:01 More issues: https://github.com/w3c/html/issues?q=is%3Aissue+milestone%3A"HTML5.3+WD4"+is%3Aopen
08:10:07 agenda+ TAG review
08:10:32 agenda+ outstanding issues
08:11:28 agenda+ wwg comparison
08:11:48 agenda+ implementation report.
08:11:59 agenda+ next steps / wwg collaboration (with PLH)
08:12:41 zakim, take up item 1
08:12:41 agendum 1. "TAG review" taken up [from chaals]
08:13:08 SM: The TAG is not going to review HTML5.3
08:13:22 q+
08:13:38 bruce has joined #html
08:13:44 ... Custom Elements is being tracked in #244 on the TAG repo
08:14:15 ... The TAG is doing a wide review of the whole of HTML.
08:14:44 ... If WebPlat wants #244 to be escalated, you should raise it with the TAG chairs.
08:15:11 ... On HTML5.3, we're not happy with @ping.
08:15:23 CMN: It would be good to get a statement to that effect from the TAG then.
08:15:30 ... Privacy also has concerns.
08:15:47 SM: @ping is not well designed I think.
08:16:05 ... Also there is @allowusermedia is a concern.
08:16:51 ... There is something called Permission Delegation in development.
08:17:02 XW: I looked at that, and it doesn't seem that different.
08:17:20 SM: Yes, but @allowusermedia is very specific, we can't keep adding things.
08:17:30 XW: But Permission Delegation isn't ready.
08:17:41 SM: No, so this is something we'd want to do in the future.
08:17:53 rrsagent, make minutes
08:17:53 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
08:17:58 scribe: Léonie
08:18:40 CMN: How many implementations does @allowusermedia have?
08:18:44 XW: One.
08:19:04 CMN: It should be marked at risk.
08:19:14 ... There are two things I'd like the TAG to look at.
08:19:26 ... #1337
08:20:02 ... Should you be able to put any custom attribute into a Custom Element?
08:20:25 ... The argument for is that it's useful for attribute short names.
08:20:36 ... The argument against is that there is no way of knowing which attributes are out there.
08:20:58 ... The question is whether we should sacrifice extensibility for author convenience?
08:21:08 ... It dould be good for the TAG to look into this.
08:21:37 SM: Please add this to the HTML5.3 wide review request issue on the TAG repo.
08:21:52 CMN: The other is #1424 on the ruby elements.
08:22:00 ... Don't think the TAG has a consensus position on this.
08:22:18 XW: #248 on the TAG repo relates to this.
08:22:31 SM: I've had conversations about this.
08:22:32 s/... Don/SW: Don
08:22:41 ... There are different opinions on where it should be.
08:22:46 ... I'd like it to be better.
08:22:50 CMN: I'll raise this too.
08:24:18 zakim, agenda?
08:24:18 I see 5 items remaining on the agenda:
08:24:19 1. TAG review [from chaals]
08:24:19 2. outstanding issues [from chaals]
08:24:19 3. wwg comparison [from chaals]
08:24:19 4. implementation report. [from chaals]
08:24:19 5. next steps / wwg collaboration (with PLH) [from chaals]
08:25:01 LW: So what is the proposed HTML review the TAG is doing?
08:25:13 SM: The TAG has never reviewed it, and so that's what we're doing.
08:25:25 LW: What is the prupose of the review?
08:25:40 SM: On our tracker there is a list of things we look for.
08:25:55 ... How everything connects together, what is still needed, what is obsolete, etc.
08:26:04 XW: Is there a timeline?
08:26:12 SM: No, no timeline.
08:26:18 ... We're under-staffed.
08:26:25 rrsagent, make minutes
08:26:25 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
08:27:10 ... One point to mention is that the WHATWG spec is missing some of the media features that are in the W3C space.
08:27:15 CMN: Examples?
08:27:20 SM: Like EME.
08:27:28 CMN: That's a separate extension.
08:27:31 SM: Why?
08:27:43 CMN: There was a belief that the HTML spec should be modularised.
08:27:51 ... It didn't really work out.
08:28:01 SM: I don't think media should be among them.
08:28:25 s/work out/work out as a complete success - there are some things that it helps and some costs
08:28:27 LW: I think EME was separated in order to enable HTML5 get to Rec.
08:29:03 SF: Ask the WHATWG to incorporate EME?
08:29:21 SM: It's not just EME, there is also Media Loading etc.
08:29:49 CMN: Suggest raising an issue.
08:29:51 zakim, close this item
08:29:51 I see a speaker queue remaining and respectfully decline to close this agendum, tink
08:30:05 q-
08:30:10 zakim, close this item
08:30:10 agendum 1 closed
08:30:11 I see 4 items remaining on the agenda; the next one is
08:30:11 2. outstanding issues [from chaals]
08:30:14 zakim, take up item 4
08:30:14 agendum 4. "implementation report." taken up [from chaals]
08:30:28 CMN: We have things in the report that no-one has looked at.
08:30:36 ... Bruce?
08:30:41 SM: Mine are not there.
08:31:21 -> http://w3c.github.io/test-results/html53/implementation-report.html Implementation report
08:31:34 LW: The report itself needs updating because we've made more commits since I created the stub.
08:31:54 -> http://w3c.github.io/test-results/html53/implementation-report.html Implementation report source
08:32:20 CMN: Please look at your changes, make sure they are in the report if they are substantive, and that the test results are provided with links to the tests.
08:32:26 rrsagent, make minutes
08:32:26 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
08:33:43 https://wpt.fyi/results/
08:34:52 zakim, close this item
08:34:52 agendum 4 closed
08:34:53 I see 3 items remaining on the agenda; the next one is
08:34:53 2. outstanding issues [from chaals]
08:37:26 zakim, take up item 2
08:37:26 agendum 2. "outstanding issues" taken up [from chaals]
08:39:22 CMN: Programmer3000 deleted their account after it was blocked, so we've lost their issues.
08:39:26 SM: Is that a bad thing?
08:39:35 CMN: I think so.
08:39:47 ... They were often abusive, but their issues were sometimes useful.
08:40:10 BL: I have lots in my emails.
08:40:47 LW: That's a very time consuming thing to do, is it really worth it?
08:40:54 CMN: Yes, I think so.
08:41:00 BL: I can do this.
08:41:51 LW: As we go through issues do we plan to add them to milestones?
08:41:59 CMN: Good question.
08:42:09 ... We should get a WD update out next week.
08:42:17 ... Then set another WD milestone.
08:43:06 LW: If we move the current milestone deadline to Friday, the WD next week will include al we do here this week.
08:43:23 CMN: I'll do that, and create a new WD milestone for the end of July.
08:43:35 rrsagent, make minutes
08:43:35 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
08:43:59 Scott_O has joined #html
08:44:56 -> https://github.com/w3c/html/milestone/21 current milestone (due Friday)
08:45:32 CMN: If you have an assigned issue and can get it done this week, that would be good.
08:45:44 ... There are also issues that are unassigned, all from Programmer3000
08:46:11 ... #1338, #1344, and #1363
08:46:26 ... Will bump the to the next milestone.
08:46:35 BL: WFM
08:47:33 ... Any others we should bump?
08:48:45 Scott_O_ has joined #html
08:59:06 bruce has joined #html
09:00:26 (WiFi fun ensues after scribe was kicking off)
09:00:49 tink has joined #html
09:01:02 chaals2 has joined #html
09:02:25 ... Of those that are assigned, how confident is everyone that they'll be done?
09:02:37 SOH: 4 of mine have PRs.
09:02:44 ... I'll work more on the Custom Elements examples this week.
09:03:02 ... Will start on #1405
09:03:14 ... Also #1392
09:03:31 ... So I think I can make progress this week.
09:03:48 ... I've also been looking at #300, which has been bumped to the When It's ready milestone.
09:04:03 XW: #1299 we can take the changes from the WHATWG.
09:04:18 ... #1384 and #1382 I can do this week.
09:04:32 CMN: #1424 to be discussed on Thursday with the I18n people.
09:04:47 ... #1423 needs implementations.
09:05:32 ... Think it can be closed because there are no implementations.
09:05:45 ... thead should allow you to keep the header in place whilst you scroll around.
09:05:59 ... Actually, I'll assign it to When It's Ready.
09:06:10 LW: We should open a corresponding issue on the WHATWG.
09:06:19 ... #1229 is to go through the IDL and compare it to the WHATWG spec.
09:06:40 ... Bruce, could you take this one?
09:06:53 BL: Ok...
09:06:59 rrsagent, make minutes
09:06:59 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
09:16:17 /join chaals
09:22:27 CMN: #1389 I'll get done.
09:22:40 ... That's all the open issues in the current milestone.
09:23:07 TOPIC: I18n issues
09:23:14 -> https://github.com/w3c/html/issues?utf8=✓&q=label%3Ai18n-comment+ i18n issues
09:23:34 rrsagent, make minutes
09:23:34 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
09:23:55 LW: All open issues, or just those from wide review?
09:23:58 ... All of them.
09:24:17 s/... All of them./CMN: ... All of them./
09:24:44 s|https://github.com/w3c/html/issues?utf8=✓&q=label%3Ai18n-comment+|https://github.com/w3c/html/labels/i18n-comment
09:25:14 ... #1424 we've dealt with ^^
09:25:28 ... #1292 allow span in the title element
09:25:47 ... Would be good, but you can't change title, so it's unlikely to happen.
09:26:04 ... It's marked "When It's ready, but think we should assume that won't happen.
09:26:13 LW@ Proposal to close?
09:26:19 CMN: Not sure.
09:26:28 SF: If we keep it open it gives false hope.
09:26:31 CMN: Yes.
09:26:50 ... Think tracking real issues is a good thing to do.
09:27:05 LW: Not sure this is the way to track such things.
09:27:21 SF: Could close it and use a specific label.
09:27:28 CMN: So suggest a label?
09:27:38 LW: "good idea", "unlikely"?
09:27:57 CMN: Will add "if only".
09:28:08 JVA: What makes this one hard to solve?
09:28:25 BL: The title element is so widely implemented and supported, changing it is too much to ask.
09:28:33 SF: The way thebrowser parses it would need to change.
09:28:58 s/SF: The way thebrowser parses it would need to change./SF: The way the browser parses it would need to change./
09:29:47 rrsagent, make minutes
09:29:47 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
09:30:10 CMN: Ok, labelled "if only" and closed.
09:30:26 XW: We should keep it open.
09:30:44 CMN: There is no point in keeping it open, but we just want to have a way of recalling it later.
09:30:52 XW: But if it's closed it won't happen.
09:30:58 CMN: We don't expect anything to happen.
09:31:20 SM: It doesn't have to happen inside the title element.
09:31:51 ... Quick test suggests it's just treated as text.
09:32:05 CMN: I know, I don't think we cansolve the problem, do you?
09:32:13 SM: No.
09:32:22 XW: We should keep it open.
09:32:25 LW: I disagree.
09:33:02 CMN: Open issues are the things we intend to do.
09:33:26 XW: What if someone raises the same issue again?
09:34:12 LW: We'd point them to the closed issue, like we would in any other situation.
09:34:21 SM: Open it in WICG?
09:34:29 CMN: There is no workable proposal though.
09:34:40 SM: True, but there is a use case.
09:35:29 CMN: Proposal: Close the issue?
09:35:33 +1
09:35:53 CMN: Show of hands +5 and -1.
09:36:18 SM: We might want some guidelines around this.
09:36:35 XW: Maybe I18n can track?
09:36:42 CMN: They'll get a notification when we close it.
09:37:42 rrsagent, make minutes
09:37:42 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
09:37:59 CMN: #1039 assigned to Xiaoqian.
09:38:24 ... Terence has a PR against this.
09:38:31 CMN: We merged it.
09:38:36 XW: So why is it assigned to me?
09:38:46 CMN: It's a wide review issue.
09:38:51 ... We should look at it again.
09:39:31 LW: If Terence addressed the original issue, it makes sense to assign this to him now.
09:40:20 scribe: xiaoqian
09:40:32 scribe: tink
09:40:49 cCMN: #1011
09:40:59 XW: Can do tht for the next milestone.
09:41:18 s/XW: Can do tht for the next milestone./XW: Can do that for the next milestone.?
09:41:30 CMN: #970 will assign to myself.
09:42:10 ... To improve definition of string using content from the Charmod spec.
09:42:28 ... #820 how should RTL ables be processed.
09:42:41 ... This is "When It's Ready" bcause implementations are generally borked.
09:42:58 ... Would be good to take it up but not sure we should right now.
09:43:40 ... #269 assigned to Sanghwan.
09:44:27 s/Sanghwan/Sangwhan/
09:44:35 rrsagent, make minutes
09:44:35 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
09:44:53 SM: We could potentially put it back.
09:45:08 ... If someone else wants to take it, I' ok with that.
09:45:26 s/... If someone else wants to take it, I' ok with that./... If someone else wants to take it, I'm ok with that./
09:45:37 rrsagent, make minutes
09:45:37 I have made the request to generate https://www.w3.org/2018/06/19-html-minutes.html tink
09:46:21 SOH: In the issue Firefox has it in development, others mixed signals.
09:46:34 JVA: Looks like Firefox implemented it about three months ago.
09:47:24 CMN: Sangwhan can you test for the next milestone?
09:47:35 SM: I need a mobile to test with.
09:48:22 ... But yes, I think so.
09:49:25 CMN: #226 assigned to Bruce.
09:49:26 Scott_O has joined #html
09:50:59 BL: Can do it for the next milestone.
09:51:14 CMN: I'll also talk to I18n about it.
09:51:27 ... That's the last of the i18n issues.
09:51:59