WebAssembly spec compatibility issues

gistfile1.txt

A summary of the issues for WebAssembly that Dan has been thinking about:

  - CSP -- https://github.com/WebAssembly/content-security-policy/pull/13
    - When the checks happen
    - What the checks are
  - Resource limits -- https://github.com/WebAssembly/spec/issues/607
   - Should we align resource limits?
    - How should the limit on local variables be interpreted?
    - What are the magic numbers? (These have already had to rise due to lack of implementation)
    - Memory objects limit -- do we have consensus that there should be no limit? https://github.com/WebAssembly/design/issues/1167
  - Copyable but not transferrable Memory
    - In the last CG meeting, we got consensus that we already has consensus, just needs spec https://github.com/WebAssembly/meetings/issues/209
  - Limitations on Module serialization
    - HTTPS-only for IndexedDB -- https://github.com/WebAssembly/spec/pull/711#issuecomment-370874198
    - Same agent cluster for postMessage -- Discussed at the April 3rd CG meeting; Dan's impression of consensus was to restrict it
  - Limitations on Response types for the streaming API -- does this have cross-browser consensus? -- https://webassembly.github.io/spec/web-api/index.html#compile-a-potential-webassembly-response
  - Known bugs in existing implementations (missing testing)
    - Non-enumerable methods
    - EnforceRange edge cases
    - Minor details about exported functions (filed bugs, checked in tests)

WebAssembly/spec#745