Skip to content

Conversation

@tidoust
Copy link
Member

@tidoust tidoust commented Mar 6, 2025

I'm not sure how to fix the values attribute of the SVGPathSegment interface. Or rather, I'm not sure how that attribute is going to be fixed in the spec. I propose to drop it in the meantime.

Note CI tests will fail because another patch is needed for the SVG spec to drop SVGPathElement.

@tidoust tidoust requested a review from dontcallmedom March 6, 2025 07:57
@dontcallmedom
Copy link
Member

I'd have an inclination to keep the values attribute (either with FrozenArray, or falling back to any) - I assume this would help with regard to BCD to have all expected attributes in an implementation.

(I'm surprised the Mozilla WebIDL parser isn't having an issue with the sequence-typed attribute)

@tidoust
Copy link
Member Author

tidoust commented Mar 6, 2025

I'd have an inclination to keep the values attribute (either with FrozenArray, or falling back to any) - I assume this would help with regard to BCD to have all expected attributes in an implementation.

Done using FrozenArray.

@tidoust tidoust merged commit 7db29f8 into main Mar 6, 2025
1 check failed
@tidoust tidoust deleted the patch-20250306075528371 branch March 6, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants