-
Notifications
You must be signed in to change notification settings - Fork 439
Issues: WebAssembly/spec
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Possibly incorrect encoding in WAST->JS conversion for elem.wast in wasm-3.0 branch
#1776
opened Aug 7, 2024 by
ddegazio
Fix CSS so the specification shows on narrow viewports without horizontal scrolling.
#1774
opened Aug 6, 2024 by
matj1
[JS API] 'run a host function' and 'create a host function' don't consistently handle completion records
#1743
opened Apr 9, 2024 by
dschuff
Missing ability to access built older versions of the WebAssembly specification in archivable form
#1736
opened Mar 1, 2024 by
20kdc
Clarification regarding value parameter for WebAssembly.Global etc.
#1660
opened Jun 2, 2023 by
manoskouk
assert_invalid and assert_malformed produce inconsistent JS tests
#1647
opened May 4, 2023 by
backes
[wasm-js-api-2] js-api Memory.grow requirement cannot be fulfilled via the core specification
#1635
opened Mar 28, 2023 by
alimpfard
relax the var to allow utf8 encoding in the wat syntax
i18n-tracker
Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
#1618
opened Mar 4, 2023 by
bobzhang
Add text syntax for defining multiple locals of the same type
#1588
opened Feb 8, 2023 by
alexcrichton
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.