| 13:01 | <zcorpan> | annevk: Domenic: MikeSmith: should we still do https://github.com/whatwg/html/issues/2335 ? |
| 13:04 | <annevk> | zcorpan: probably not |
| 13:04 | <zcorpan> | annevk: why not? |
| 13:04 | <annevk> | zcorpan: we should just decide what's best when doing something new |
| 13:13 | <zcorpan> | annevk: seems reasonable, but more likely to fall into the existing name/content pattern |
| 13:14 | <zcorpan> | e.g. https://github.com/w3c/csswg-drafts/issues/2750 |
| 13:16 | <annevk> | zcorpan: do you think a warning in HTML would have prevented that? |
| 13:16 | <zcorpan> | annevk: he cited the spec for how to extend <meta>, so yes |
| 13:17 | <zcorpan> | well |
| 13:17 | <annevk> | zcorpan: don't think he works for Apple though |
| 13:17 | <zcorpan> | now that it redirects to whatwg :) |
| 13:17 | <zcorpan> | correct |
| 13:18 | <zcorpan> | ok, I see what you mean |
| 13:19 | <zcorpan> | I don't know if whoever implemented that thing read the spec before doing that, but probably not |
| 13:21 | <zcorpan> | but at least sometimes proposals are discussed before they ship, and then people are more likely to read the spec, and not so likely to find this open issue out of the 1000+ open issues |