| 09:03 | <bkardell> | I was chatting with some folks at igalia's hackfest and the q came up why is <a href> not in the allowed list for ability to have a shadow dom added to it -- no one could recall. I reached out to some others and beyond some general "I think maybe it had something to do with ... activiation behavior?" we couldn't really seem to recall... Does anyone recall? |
| 11:31 | <annevk> | bkardell: I think in retrospect it's unfortunate that we didn't have ElementInternals before as that is the right place to attach shadow trees |
| 11:40 | <Domenic> | https://hacktoberfest.digitalocean.com/details#spam says if we tag the spam pull requests as "invalid" then they might not get credit for making them |
| 11:43 | <annevk> | Domenic: I saw that, but I don't like this scheme as it puts the onus on us for a problem of their creation |
| 11:44 | <Domenic> | I agree, just not sure what else to do |
| 11:44 | <annevk> | Domenic: it'd be better if they created a GitHub-wide label "hacktoberfest" we'd apply to successful contributions |
| 11:44 | <annevk> | I guess I've been reporting spammy-looking PRs and getting explanations of hacktoberfest... |
| 11:45 | <hsivonen> | Is WPT coverage for focus/blur good? |
| 11:46 | <annevk> | I'd expect it to be improved given recent focus efforts |
| 11:48 | <Domenic> | the actual events themselves are probably the biggest missing piece |
| 11:49 | <hsivonen> | Domenic: as in it doesn't test the focus/blur events? |
| 11:54 | <annevk> | hsivonen: pretty sure there are some tests for those, but there are 6 focus events or so and that's not well covered (or defined) |
| 12:12 | <Domenic> | In particular I think nobody's tried writing tests since webdriver appeared and made a lot of these things actually testable. |
| 13:06 | <hsivonen> | annevk, Domenic: OK. Thanks. I guess mochitest-plain is then the best indication of whether I'm breaking the Web |
| 13:21 | <bkardell> | annevk: but do we remember the reason, or is there a thing we can do to correct this now? |
| 13:21 | <annevk> | bkardell: we don't want to create more edge cases, basically, there's an issue covering <a> somewhere |
| 13:22 | <annevk> | I guess I can quickly find it... |
| 13:24 | <annevk> | bkardell: https://github.com/w3c/webcomponents/issues/511 you were involved in an issue that was duplicated against that... |
| 13:25 | <bkardell> | lolol |
| 13:26 | <bkardell> | thanks annevk |
| 17:31 | <TabAtkins> | re: the hacktoberfest page, lol at a dang *monospace* font having a definitely-monospace "fi" ligature, wtfffff |
| 19:34 | <ondras> | TabAtkins: :) |
| 19:35 | <ondras> | unrelated: is CustomElement allowed to have no constructor() at all? |
| 20:00 | <annevk> | ondras: a custom element needs one, no? |
| 20:05 | <ondras> | annevk: seems to work without... |
| 20:06 | <ondras> | https://jsfiddle.net/mfrgyd29/ |
| 23:18 | <zcorpan> | ["altGlyph", "altGlyphDef", "altGlyphItem", "animateColor", "glyphRef"] are the SVG element names with case fixup in https://html.spec.whatwg.org/multipage/parsing.html#parsing-main-inforeign that are not in https://svgwg.org/svg2-draft/eltindex.html |
| 23:25 | <zcorpan> | SVG attributes with HTML fixup not in SVG 2 ["attributeType", "baseProfile", "glyphRef", "requiredFeatures", "viewTarget", "zoomAndPan"] |
| 23:26 | <zcorpan> | seemingly now new SVG elements or attributes with mixed case that aren't in the html parser list, which is good |
| 23:37 | <zcorpan> | http://software.hixie.ch/utilities/js/live-dom-viewer/saved/7285 |
| 23:39 | <zcorpan> | I guess this is https://github.com/whatwg/html/issues/2168 |