| 12:23 | <MikeSmith> | PSA: the HTML checker now has more options for letting you filter out (drop/ignore/suppress) error messages and warning messages you don’t care about/don’t want to see/don’t consider to be a problem |
| 12:23 | <MikeSmith> | https://github.com/validator/validator/wiki/Message-filtering |
| 12:25 | <MikeSmith> | the mechanism is just to specify a set of regular expressions, and any error message or warning message that matches any of the specified regexes gets filtered out (dropped/ignored/suppressed) |
| 16:05 | <annevk> | Domenic: if you could update https://github.com/whatwg/html/pull/2518 with thoughts today that'd be great |
| 16:05 | <annevk> | Oh, you're in the process of going through stuff, guess it'll happen then |
| 16:12 | <Domenic> | prioritization pings are always nice :) |
| 16:16 | <annevk> | I will have a full eight hours plus again starting tomorrow, so I better have something to do |
| 16:16 | <annevk> | Though those WindowProxy issues might keep me busy for a bit |
| 16:18 | <Domenic> | I also feel like we kinda dropped https://github.com/whatwg/html/issues/2415 which has multiple confused implementers; I've been meaning to get back to that |
| 16:22 | <annevk> | Domenic: and the whole rewrite history and fix lifetime issues? |
| 16:22 | <annevk> | That's my main frustration with service workers, we're exposing all these things but we barely know how they work |
| 16:23 | <Domenic> | sure, yeah, although those are bigger and mostly hurting servo right now in terms of immediately-actionable implementation work |
| 16:23 | <annevk> | I think it's also hurting decisions we make in service workers around navigation and such |
| 16:23 | <Domenic> | whereas 2415 is Edge going "we have an interop problem with Chrome because of this spec area" and then Gecko being like "hmm yes, this does not make any sense" |
| 16:23 | <annevk> | Not history as much, but lifetime for sure |
| 16:23 | <Domenic> | Fair |
| 16:24 | <annevk> | So looking at that issue it's mostly a mkwst issue I think |
| 16:25 | <annevk> | It also reminds me of https://github.com/whatwg/html/issues/125, which is still blocked on smaug_ |
| 16:25 | <Domenic> | Maybe, although it seemed to me CSP is just one of many of these fail-to-load cases, and so likely mkwst will be happy with whatever we decide for the larger question |
| 16:26 | <annevk> | Ah well, the larger one is the issue I just linked |
| 16:26 | <annevk> | I have a plan, I just need answers |
| 16:26 | <Domenic> | https://bugs.chromium.org/p/chromium/issues/detail?id=698559 is the original |
| 16:26 | <Domenic> | I see |
| 16:26 | <annevk> | My plan is that an error page results in an error event and is basically a document with a new opaque origin |
| 17:17 | <smaug_> | one day github has some reasonable way to see needinfo queue |
| 17:41 | <annevk> | Yeah that is annoying |
| 20:04 | <Domenic> | tobie: can we help with https://github.com/heycam/webidl/pull/323 in some way? |
| 20:05 | <tobie> | Think it was waiting for your feedback on my last comment. |
| 20:05 | <tobie> | Domenic: ^ |
| 20:06 | <Domenic> | Oh, dang, I was afraid it was something like that |
| 20:06 | <tobie> | Domenic: np, it took me long to get back to you on it, so no worries. |
| 20:06 | <tobie> | Domenic: should have chased but the sensor work kept me super busy. :-/ |
| 20:09 | <tobie> | TabAtkins: any idea why the STOD section of WebIDL changed recently? Is that tied to some broader changes somwhere I missed? |
| 20:09 | <tobie> | https://s3.amazonaws.com/pr-preview/heycam/webidl/faaaaa9...tobie:61599aa.html#status |
| 20:15 | <Domenic> | tobie: there was a Bikeshed change to stop using mailing lists for WPWG |
| 20:15 | <Domenic> | The "put the text webidl in the subject" is pretty inappropriate though |
| 20:15 | <Domenic> | I'll file a Bikeshed issue... |
| 20:15 | <tobie> | Domenic: ty |