| 07:30 | <sideshowbarker> | https://github.com/mdn/content/issues/8515 could just some quick help. Basically just needs a comment in response to the OP’s question. Should only take ~10 minutes. |
| 17:17 | <annevk> | Domenic: thoughts on where we should put a Security/Privacy section? First no-num section? Also, in DOM, should the Historical section become a no-num section? See https://github.com/whatwg/dom/issues/1013 for context. (I'm out now, but I figured I'd leave this here and maybe address it tomorrow. Thoughts from others welcome as well of course.) |
| 17:19 | <Domenic> | annevk: no real opinion, besides that it seems a bit weird that W3C process/groups is influencing our editorial style. I guess I would lean toward leaving it numbered since it is not shared boilerplate that all specs are expected to have? Or is it? |
| 17:25 | <annevk> | Domenic: I guess it kinda is shared, in the sense that a reviewer can access the impact, but the contents would be specific to the document. I'm not quite sure how I feel about it yet and I'm not really volunteering on adding the complicated sections, e.g., to HTML. |
| 17:48 | <Domenic> | Yeah this seems like a "PR welcome" situation at the most. |
| 17:55 | <Eric Portis (he/him)> | Step 4.7. here https://html.spec.whatwg.org/multipage/images.html#updating-the-source-set says: "Parse child's sizes attribute with the fallback width width, and let source set's source size be the returned value." I don't see width defined anywhere, or fallback width used anywhere in the "Parse a sizes attribute" algorithm. Ten bucks says I'm just missing something, though. cc: zcorpan |