Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

text-overflow property is missing from attribute index #711

Closed
SebastianZ opened this issue Jul 5, 2019 · 5 comments
Closed

text-overflow property is missing from attribute index #711

SebastianZ opened this issue Jul 5, 2019 · 5 comments

Comments

@SebastianZ
Copy link

The attribute index of SVG 2 is missing the text-overflow property.

Sebastian

@AmeliaBR
Copy link
Contributor

AmeliaBR commented Jul 5, 2019

Do any browsers support text-overflow as a presentation attribute?

In general, we had resolved not to add new presentation attributes unless there is a compat reason to do so.

@SebastianZ
Copy link
Author

SebastianZ commented Jul 7, 2019

Do any browsers support text-overflow as a presentation attribute?

If the example I created on the MDN documentation page is correct, then Firefox 67, Chrome 75, and Edge 44 do not support it.

In general, we had resolved not to add new presentation attributes unless there is a compat reason to do so.

Ok, so I assume that this one should be removed again then. (And I should remove the MDN page again.)

Sebastian

@AmeliaBR
Copy link
Contributor

AmeliaBR commented Jul 7, 2019

There's nothing to remove (yet). The entry in the text chapter describes how the CSS property (set with CSS) would apply to SVG text.

Of course, if no browser has implemented that, either, we may need to mark it as risk. But that will get bundled with changes to defer all SVG multi-line text functions to a future version of the spec. Even though text-overflow would be useful even without the other new properties, e.g., for text on a path.

Re MDN: Yes, remove it from the attributes section. It would be helpful to have information in the regular CSS text-overflow page, that it is defined to be valid on SVG, but support is poor.

@AmeliaBR AmeliaBR closed this as completed Jul 7, 2019
@SebastianZ
Copy link
Author

There's nothing to remove (yet). The entry in the text chapter describes how the CSS property (set with CSS) would apply to SVG text.

Oh, yeah, I missed that. So then it's missing from the properties index. 😉

Of course, if no browser has implemented that, either, we may need to mark it as risk.

I've now tested the example given in the spec. in all three mentioned browsers and unfortunately they also do not support the property.
So I've filed a request for implementation in Gecko. For Chromium/Blink there was already one filed. If you test it in Safari and it also doesn't work there, I can also file an enhancement request in WebKit's bug tracker.

But that will get bundled with changes to defer all SVG multi-line text functions to a future version of the spec. Even though text-overflow would be useful even without the other new properties, e.g., for text on a path.

Off-topic for this issue, but is there some central place where all the ideas for a future SVG spec. and the features removed from SVG 2 are collected and discussed?

Re MDN: Yes, remove it from the attributes section. It would be helpful to have information in the regular CSS text-overflow page, that it is defined to be valid on SVG, but support is poor.

I removed the page again. As no tested browser currently supports the property and annotation 36 indicates that it's value seems to be controversial and therefore may be removed from the spec., I decided now not to document it for now and rather wait for whether it get's traction.

Sebastian

@SebastianZ
Copy link
Author

Off-topic for this issue, but is there some central place where all the ideas for a future SVG spec. and the features removed from SVG 2 are collected and discussed?

Ah, remembered it. That was https://www.w3.org/community/svgcg/. Just joined the group now.

Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants