-
Notifications
You must be signed in to change notification settings - Fork 132
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
Drop the [NoInterfaceObject] for SVGPathSegment #802
Conversation
This has been renamed in Web IDL: https://heycam.github.io/webidl/#LegacyNoInterfaceObject However, if the interface is implemented, it would be best to expose it for feature detection.
@tabatkins do you know who I can poke for review of a change like this? |
@@ -1368,10 +1368,10 @@ <h3 id="InterfaceSVGPathSegment">Interface SVGPathSegment</h3> | |||
The <a>SVGPathSegment</a> interface is a base interface that corresponds to a | |||
single command within a path data specification. | |||
|
|||
<pre class="idl">[NoInterfaceObject] | |||
<pre class="idl"> | |||
interface <b>SVGPathSegment</b> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at how this is used, maybe this can even be a dictionary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you're right, that would be fine in this case, and would avoid the need to make values
a FrozenArray<float>
as one would need to do to keep this an interface.
SVGPathElement is now defined by SVG 2, maybe this spec should be dropped. Edit: Per MDN the segment part has been dropped in SVG 2. |
This has been renamed in Web IDL:
https://heycam.github.io/webidl/#LegacyNoInterfaceObject
However, if the interface is implemented, it would be best to expose it for feature detection.