Re: [csswg-drafts] CSS properties should apply to some SVG elements as well (#3414)

The CSS Working Group just discussed `CSS properties should apply to some SVG elements as well`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: CSS properties should apply to some SVG elements as well<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3414<br>
&lt;dael> astearns: Is AmeliaBR on?<br>
&lt;dael> astearns: Looks like krit is asking for some things to apply to SVG text<br>
&lt;dael> fantasai: Wanted to ask if we want to deal with them for all our specs. DOesn't make sense for a few prop. If we've got a case with some but not all we've got a case where if you don't spec a prop does it apply?<br>
&lt;dael> chris: That's not what we mean. We don't say it applies to HTML elements, we just say elements<br>
&lt;Rossen> +1 to what fantasai said<br>
&lt;dael> AmeliaBR: Reason it came up is...concern if we rely on SVG spec to mention which prop apply it will regularly get out of date as new prop introduced. Trying to move that into prop definitions and make sure it's covered byt he applies to part of prop definition box<br>
&lt;dael> AmeliaBR: As chris said in cases where we have applies to all elements it can presume to apply to SVG elements. But then there are some places it says applies to but it's CSS box type. It's about being consistent and making sure those boxes are useful<br>
&lt;dael> fantasai: All elements means all elements formatted with css box model. SVG has typicially been outside our spec zone. Incorporating which applies to what SVG makes sense. but if we're going to do it we should do it to all specs.<br>
&lt;dael> fantasai: If we want to do that we should resolve to do that for all specs at once so everything is consistent. And it goes in at once so there's no point where we've got uncertainly.<br>
&lt;dael> fantasai: That's what I'd like tos ee us do<br>
&lt;dael> AmeliaBR: Agree with that strategy. I think it should be thought of in conjunction with some other open issues about redefining how applies to line works. Open issue about if pseudo elements are in all elements<br>
&lt;dael> fantasai: They're not except before and after which in their own definition says that.<br>
&lt;dael> fantasai: I think if we list every pseudo element we could do that. before and after it would be redundant because they say they'r enot a special type.<br>
&lt;AmeliaBR> https://drafts.csswg.org/css-text-3/#word-spacing-property<br>
&lt;dael> AmeliaBR: Specific properties krit brought up, they say applies to inline boxes which is a very CSS term<br>
&lt;dael> AmeliaBR: That's where the issue for those came up. Might come to having to sit down and come up with a set of new terms that can be used for covering the SVG layout/element types as well as the CSS box types<br>
&lt;dael> AmeliaBR: That's prob. first step. A proposal for which categories to use for what makes sense to desc the SVG properites. Then come back to WG for confirmation and then make a giant PR<br>
&lt;dael> fantasai: Makes sense. DOn't rely on all elements to help you out, though. Border applies to all for SVG. We'll have to change things around.<br>
&lt;dael> AmeliaBR: It might change ell elements to all css boxes or something like that.<br>
&lt;dael> AmeliaBR: Not going to figure it out on the call. If anyone has ideas we can brainstorm in the issue. First step is figure out what hte categories should be that makes sense in both contexts.<br>
&lt;dael> AmeliaBR: Once that's decided it's going through every spec and making sure it makes sense<br>
&lt;dael> fantasai: Direction sound good to everyone?<br>
&lt;dael> chris: sgtm<br>
&lt;dael> fantasai: I'll tag this issue against all specs<br>
&lt;dael> astearns: I don't know if that'll be that useful. But mentioning in a comment this will apply to all specs might b sufficient.<br>
&lt;dael> astearns: How many SVG folks will be at F2F? I'm wondering if this is something we can noodle on<br>
&lt;dael> chris: I hope to be<br>
&lt;dael> AmeliaBR: I will be in person<br>
&lt;dael> AmeliaBR: krit though won't be around. not sure about myles or eric<br>
&lt;dael> astearns: Let's see if we can wrap this up by the F2F<br>
&lt;dael> astearns: Anything else on this issue?<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3414#issuecomment-456889797 using your GitHub account

Received on Wednesday, 23 January 2019 17:20:22 UTC