| 05:55 | <MikeSmith> | JakeA: when you are around I want to ask you about what days are best for Service Workers meeting at TPAC |
| 05:55 | <MikeSmith> | I am talking with the W3C meeting planners about the schedule |
| 05:55 | <MikeSmith> | the choice is either Monday and Tuesday or Thursday and Friday |
| 05:57 | <MikeSmith> | I think the Web Components discussions are scheduled for Monday, so that suggests we should either try to get the SW room for Thursday and Friday, or else ask that the Web Components discussions be rescheduled for Thursday and Friday so that we could do Monday and Tuesday, if that turns out to be preferable |
| 06:08 | <GPHemsley> | oh, I see what the problem is here... if jsdom/whatwg-url throws a 'TypeError: Invalid URL', the Live URL Viewer doesn't blank out the other fields from the previous run, thus resulting in weird results and a likely mismatch with the browser |
| 06:08 | <GPHemsley> | I think the real problem may be that jsdom/whatwg-url is throwing at all |
| 06:09 | <GPHemsley> | "A validation error |
| 06:09 | <GPHemsley> | indicates a mismatch between input and valid input. User agents, especially conformance checkers, are encouraged to report them somewhere. " |
| 06:09 | <GPHemsley> | "A validation error does not mean that the parser terminates. Termination of a parser is always stated explicitly, e.g., through a return statement. " |
| 06:14 | <GPHemsley> | filed https://github.com/jsdom/whatwg-url/issues/92 |
| 06:36 | <zcorpan> | igrigorik: (I figured something out for the <hr> thing, https://bugs.chromium.org/p/chromium/issues/detail?id=728499#c9 ) |
| 08:37 | <JakeA> | MikeSmith: avoiding clashing with security stuff would be great too. Other than that, I don't mind which day. |
| 08:41 | <MikeSmith> | JakeA: OK |
| 08:42 | MikeSmith | checks webappsec days |
| 08:43 | <MikeSmith> | JakeA: so yeah WebAppSec meets Monday-Tuesday https://www.w3.org/2017/11/TPAC/Overview.html#Schedule |
| 08:43 | <MikeSmith> | thus I will ask for Thursday-Friday |
| 12:28 | <zcorpan> | Domenic: MikeSmith: sorry for confusion with <menu>. I commented in the spec PR when I meant to comment in the wpt PR, and figured we should wait with merging either PR until we have heard something from mozilla folks |
| 12:28 | <MikeSmith> | ah OK |
| 16:32 | <Domenic> | Oh awesome zcorpan that you got Chrome to update for the <hr> spec change. That makes me hopeful about further UA stylesheet alignment. |
| 17:02 | <smaug> | Domenic: I thought blink was implementing context menu |
| 17:02 | <smaug> | perhaps plans changed |
| 17:02 | <Domenic> | smaug: they were, then plans changed, yeah :( |
| 17:02 | <Domenic> | https://bugs.chromium.org/p/chromium/issues/detail?id=87553&desc=2#c64 |
| 17:04 | <Domenic> | If Mozilla believes this feature is valuable, maybe the right thing to do is find someone at Mozilla to move it into some other spec repo (WICG?) and keep the code... Certainly Blink implements a lot of single-vendor features via that route... |