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

Inconsistent rules for <title>, <desc> and <metadata> #9

Closed
jarek-foksa opened this Issue Jun 9, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@jarek-foksa

jarek-foksa commented Jun 9, 2016

The spec allows descriptive elements (title, desc and metadata) as children of certain elements (filter, feSpecularLighting) while disallowing them on others (feBlend, feColorMatrix).

For the sake of consistency I would either allow or disallow them everywhere.

@jarek-foksa jarek-foksa changed the title from Inconsistent rules for <title>, <desc> and <metadata> to Inconsistent rules for `<title>`, `<desc>` and `<metadata>` Jun 9, 2016

@jarek-foksa jarek-foksa changed the title from Inconsistent rules for `<title>`, `<desc>` and `<metadata>` to Inconsistent rules for <title>, <desc> and <metadata> Jun 9, 2016

@jarek-foksa

This comment has been minimized.

Show comment
Hide comment
@jarek-foksa

jarek-foksa Jun 9, 2016

Actually, title or desc makes sense as a child of a filter (e.g. to provide a filter name to be displayed by authoring tools or a human-readable description of what the filter does), but I can't think of any situation where I would want to put title or desc inside a filter primitive.

jarek-foksa commented Jun 9, 2016

Actually, title or desc makes sense as a child of a filter (e.g. to provide a filter name to be displayed by authoring tools or a human-readable description of what the filter does), but I can't think of any situation where I would want to put title or desc inside a filter primitive.

@Tavmjong

This comment has been minimized.

Show comment
Hide comment
@Tavmjong

Tavmjong Jun 9, 2016

At our weekly telecon: RESOLUTION: title and desc can be a child of any svg namespaced element except switch

Tavmjong commented Jun 9, 2016

At our weekly telecon: RESOLUTION: title and desc can be a child of any svg namespaced element except switch

@AmeliaBR

This comment has been minimized.

Show comment
Hide comment
@AmeliaBR

AmeliaBR Jun 9, 2016

I'll get the SVG 2 prose description of title & desc updated in the next couple weeks, along with the element metadata that defines allowed child content.

If anyone wants to review the FXTF specs & figure out where changes would be required, that would be wonderful. I'm assuming they've mostly borrowed the definitions.xml files from SVG, but haven't looked too closely.

AmeliaBR commented Jun 9, 2016

I'll get the SVG 2 prose description of title & desc updated in the next couple weeks, along with the element metadata that defines allowed child content.

If anyone wants to review the FXTF specs & figure out where changes would be required, that would be wonderful. I'm assuming they've mostly borrowed the definitions.xml files from SVG, but haven't looked too closely.

@dirkschulze

This comment has been minimized.

Show comment
Hide comment
@dirkschulze

dirkschulze Jun 8, 2017

Contributor

@Tavmjong @AmeliaBR Do you have a link to the resolution?

Contributor

dirkschulze commented Jun 8, 2017

@Tavmjong @AmeliaBR Do you have a link to the resolution?

@AmeliaBR

This comment has been minimized.

Show comment
Hide comment
@AmeliaBR

AmeliaBR Jun 9, 2017

@dirkschulze

The minutes are hardly up to CSSWG standards, but they're here: https://www.w3.org/2016/06/09-svg-minutes.html#resolution04

AmeliaBR commented Jun 9, 2017

@dirkschulze

The minutes are hardly up to CSSWG standards, but they're here: https://www.w3.org/2016/06/09-svg-minutes.html#resolution04

@dirkschulze

This comment has been minimized.

Show comment
Hide comment
@dirkschulze

dirkschulze Jun 10, 2017

Contributor

@AmeliaBR Thanks for the link! This is a FX spec, a joint venture of the SVG WG and the CSS WG. This definitely is in the domain of SVG :)

Contributor

dirkschulze commented Jun 10, 2017

@AmeliaBR Thanks for the link! This is a FX spec, a joint venture of the SVG WG and the CSS WG. This definitely is in the domain of SVG :)

@AmeliaBR

This comment has been minimized.

Show comment
Hide comment
@AmeliaBR

AmeliaBR Jun 10, 2017

@dirkschulze I didn't mean to suggest that SVG WG resolutions were any less valid, only that the minutes were rather sparse and un-edited, so there isn't a lot of detail about the discussion that led up to the resolution.

AmeliaBR commented Jun 10, 2017

@dirkschulze I didn't mean to suggest that SVG WG resolutions were any less valid, only that the minutes were rather sparse and un-edited, so there isn't a lot of detail about the discussion that led up to the resolution.

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