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

New WebIDL types like CancelablePromise cause <types> to disappear #352

Closed
arunranga opened this issue Oct 27, 2014 · 8 comments
Closed

Comments

@arunranga
Copy link

See http://w3c.github.io/filesystem-api/Overview.html#directory-webidl and in particular, the "move" method.

Highlight the "move" method and check out the selection source.

If you remove the "Cancelable" part of "CancelablePromise" it shows the . It is supposed to look like this:

CancelablePromise move((DOMString or File or Directory) path, (DOMString or Directory or DestinationDict) dest)

but respec.js seems to shed the "" until I remove the "Cancelable" and leave it as Promise<void> in which case it shows up as intended.

@arunranga
Copy link
Author

Whoops, some clarification needed:

Somehow, respec doesn't allow you to use CancelablePromise<void>

It strips the "<void>" leaving just CancelablePromise fu(...)

@darobin
Copy link
Member

darobin commented Oct 27, 2014

Ah, I believe that @tobie fixed that for Promise, I presume the same can be applied here.

@tobie
Copy link
Member

tobie commented Oct 28, 2014

Actually, I had fixed that in w3c/webidl2.js#15, not here.

halindrome added a commit that referenced this issue Oct 29, 2014
add new parametric types for issue #352
@halindrome
Copy link
Contributor

This should be fixed in version 3.2.26 - I pushed that this morning.

@arunranga
Copy link
Author

When will the fix be reflected in http://www.w3.org/Tools/respec/respec-w3c-common.js ?

Is there any action I need to take? Sorry if I've missed something.

@halindrome
Copy link
Contributor

As far as I know that is reflected now. I pushed version 3.2.26 days ago.

On Fri, Oct 31, 2014 at 10:15 AM, Arun Ranganathan <notifications@github.com

wrote:

When will the fix be reflected in
http://www.w3.org/Tools/respec/respec-w3c-common.js ?

Is there any action I need to take? Sorry if I've missed something.


Reply to this email directly or view it on GitHub
#352 (comment).

Shane McCarron
halindrome@gmail.com

@darobin
Copy link
Member

darobin commented Oct 31, 2014

On 31/10/2014 12:44 , Shane McCarron wrote:

As far as I know that is reflected now. I pushed version 3.2.26 days ago.

Nope. Not sure which crank you used but the sync hasn't happened.

Robin Berjon - http://berjon.com/ - @robinberjon

@halindrome
Copy link
Contributor

Auto sync was apparently broken. This is fixed now.

On Fri, Oct 31, 2014 at 2:35 PM, Robin Berjon notifications@github.com
wrote:

On 31/10/2014 12:44 , Shane McCarron wrote:

As far as I know that is reflected now. I pushed version 3.2.26 days ago.

Nope. Not sure which crank you used but the sync hasn't happened.

Robin Berjon - http://berjon.com/ - @robinberjon


Reply to this email directly or view it on GitHub
#352 (comment).

Shane McCarron
halindrome@gmail.com

shikhar-scs pushed a commit to shikhar-scs/respec that referenced this issue Feb 19, 2018
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

No branches or pull requests

4 participants