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
Should we make Range a subclass of StaticRange? #1
Comments
@dtapuska mentioned that |
I recall that we were talking about changing Range to be a subclass of StaticRange... ie: interface StaticRange I don't recall what the resolution was in January. |
I recall it being mentioned, but there were concerns about changing the definition of Range. I don't recall details or specific concerns, however. |
@garykac thanks for the comments! I'm currently working on |
This issue was moved to w3c/staticrange#1 |
According to the StaticRange.idl I found (not sure if that's the latest one) there are some duplicate methods with Range.See @dtapuska comments below, do we still want to make it
interface Range : StaticRange
?BTW would it be better to have the an idl inside this explainer?Here is the idl #2 (comment)
The text was updated successfully, but these errors were encountered: