Skip to content

Latest commit

 

History

History
114 lines (75 loc) · 2.67 KB

CG-11-27.md

File metadata and controls

114 lines (75 loc) · 2.67 KB

WebAssembly logo

Agenda for the November 27 video call of WebAssembly's Community Group

  • Where: zoom.us
  • When: November 27, 5pm-6pm UTC (November 27, 9am-10am Pacific Time)
  • Location: link on calendar invite
  • Contact:

Registration

None required if you've attended before. Email Ben Smith to sign up if it's your first time. The meeting is open to CG members only.

Logistics

The meeting will be on a zoom.us video conference. Installation is required, see the calendar invite.

Agenda items

  1. Opening, welcome and roll call
    1. Opening of the meeting
    2. Introduction of attendees
  2. Find volunteers for note taking (acting chair to volunteer)
  3. Adoption of the agenda
  4. Proposals and discussions
    1. Review of action items from prior meeting.
  5. Closure

Agenda items for future meetings

None

Schedule constraints

None

Meeting Notes

Opening, welcome and roll call

Opening of the meeting

Introduction of attendees

  • Ben Smith
  • Ben Titzer
  • Deepti Gandluri
  • Derek Schuff
  • Francis McCabe
  • Jacob Gravelle
  • Limin Zhu
  • Michael Holladay
  • Nick Fitzgerald
  • Pat Hickey
  • Sam Clegg
  • Sergey Rubanov
  • Sven Sauleau
  • Tyler McMullen
  • Ulrik Sorber
  • Yury Delendik

Find volunteers for note taking (acting chair to volunteer)

Adoption of the agenda

Proposals and discussions

Review of action items from prior meeting.

SS: I opened an issue that I'd like to discuss. WebAssembly/spec#915

SS: There is WebAssembly.Module.customSections it returns the custom sections with those bytes. The names are encoded in utf8, which is specified in the wasm spec. There is an API that uses a separate decoder. It looks like that whatwg decoder has special rules. I found some tests that are linked in to the issue. From the wasm point of view it is one section, from the JS point of view it is two sections.

BS: It has to do with how to handle the replacement character?

SS: Yes.

BS: So the question is how to resolve?

SS: It's inconsistent. You have to add special rules.

BT: What you're saying that the decoding of wasm is different than the JS one? Or all others?

SS: Just the JS one.

BS: So the WhatWG decoder converts 0xdc01 to 0xfffd?

SS: They are both way higher than the upper bounds, so they should be equal.

BT: Do you know if the implementations don't match this?

SS: Yes, v8 doesn't pass.

BT: We can do the same thing to match JS and wasm interpretation.

BS: I think this may be a JS thing vs a web thing.

BT: Ok I think this may require follow-up offline.

AI(SS): follow up on the GH issue.

Closure

Closure