-
Notifications
You must be signed in to change notification settings - Fork 35
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
Port stack trace support from explainer to js api spec #201
Comments
Are you planning on working on this in near future? |
Not having this in the spec is problematic for MDN docs and browser compatibility data. We're supposed to doc what the spec does, so if the spec is not updated we should document browsers that implement as per the explainer as "off-spec". Firefox 100 is such a browser according to https://bugzilla.mozilla.org/show_bug.cgi?id=1759217#c6 Is there an ETA for this to happen? |
Friendly ping! :) Sorry for bugging you again, but it'd be good to know what your plan on this is. Are you planning to working on this? If so, can you let me know the rough timeline? If you are unable to work on this for a long time, I can try working on this, but I'm no expert on JS API formal spec at all, so I guess I would at least very much appreciate your reviews. Also about #189 as well. Please let me know what your plan is. Thanks! |
Hey, sorry about the delay. I should have more time to work on wasm again from July - if you have time before that, I'll try to find time to review. |
@Ms2ger Do you have a plan to, or have availability to work on this in Q3? I am hoping we can advance the proposal to phase 4 by the end of Q3, so I'm wondering about this. Thank you! |
#197
The text was updated successfully, but these errors were encountered: