-
Notifications
You must be signed in to change notification settings - Fork 198
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
A constructor operation isn't linked like the extended attribute is #1519
Comments
Yes, Bikeshed needs changes here, haven't gotten to it yet. Thanks for the bug to track it. |
Thanks for confirming, Tab! @Ms2ger FYI I think this should block sending lots of PRs for Bikeshed specs, as probably lots of specs would have links broken without the maintainers noticing. |
Eh, they'll fix on next build, it'll be fine. I'll fix this either Monday or Tuesday. |
Also, it appears the IDs generated for parameters to constructor operations are not correctly scoped to the constructor operation (and hence can overlap with interface members of the same name). |
Okay, "constructor" should be linking/dfning properly now. You can autolink to it either as "constructor()" or as "InterfaceName()". The args problem is due to a bug in widlparser, which plinss is looking into right now. |
And arguments should be working now. |
I still can't get this to work with the latest bikeshed. The argument linking works but it doesn't link the constructor definition given the following markup:
I've tried |
Ah! Sorry, that's because I'll switch it back to "constructor". |
Thank you! |
Done in 7b13078 |
Works a treat. Thank you! |
See whatwg/dom#782 (comment).
I haven't looked into what the problem is, but presumably Bikeshed needs some changes.
@Ms2ger is this something you've run into already?
The text was updated successfully, but these errors were encountered: