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

Drop the [NoInterfaceObject] for SVGPathSegment #802

Closed
wants to merge 2 commits into from

Conversation

foolip
Copy link
Member

@foolip foolip commented Jul 1, 2020

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.

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.
foolip added a commit to foolip/webref that referenced this pull request Jul 3, 2020
foolip added a commit to foolip/webref that referenced this pull request Jul 3, 2020
@foolip
Copy link
Member Author

foolip commented Jul 13, 2020

@tabatkins do you know who I can poke for review of a change like this?

foolip added a commit to foolip/webref that referenced this pull request Jul 13, 2020
foolip added a commit to foolip/webref that referenced this pull request Jul 22, 2020
@@ -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> {
Copy link
Member

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.

Copy link
Member Author

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.

queengooborg pushed a commit to foolip/webref that referenced this pull request Nov 18, 2020
queengooborg pushed a commit to foolip/webref that referenced this pull request Dec 14, 2020
@saschanaz
Copy link
Member

saschanaz commented Dec 17, 2020

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.

foolip added a commit to foolip/webref that referenced this pull request Jan 21, 2021
foolip added a commit to foolip/webref that referenced this pull request Jan 27, 2021
Base automatically changed from master to main January 28, 2021 15:25
@foolip foolip closed this Apr 1, 2021
@foolip foolip deleted the patch-1 branch April 1, 2021 10:42
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.

2 participants