New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667901 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 662005



Sign in to add a comment

[TreatNullAs=EmptyString] doesn't work with USVString

Project Member Reported by foolip@chromium.org, Nov 22 2016

Issue description

https://w3c.github.io/webrtc-pc/#peer-to-peer-data-api

The "[TreatNullAs=EmptyString] USVString label" argument can't be implemented currently, because the relevant generated code will look like this:

  V8StringResource<TreatNullAsEmptyString> label;
  label = toUSVString(info.GetIsolate(), info[0], exceptionState);

The problem is that toUSVString returns a WTF::String, and so no special handling of null happens.

Support was added in  issue 379009 .
 

Comment 1 by foolip@chromium.org, Nov 22 2016

Blocking: 662005
Labels: Needs-Feedback
Owner: foolip@chromium.org
Status: Assigned (was: Untriaged)
The WebIDL spec (https://heycam.github.io/webidl/#TreatNullAs) currently forbids this:

The [TreatNullAs] extended attribute must not be associated with a type that is not DOMString.

I agree that it seems reasonable for this to apply to USVString (and probably ByteString) as well. I have a mostly complete patch to change this on the bindings side if you think the spec ought to be updated to allow this. WDYT?

Comment 3 by foolip@chromium.org, Apr 11 2017

Status: ExternalDependency (was: Assigned)
I've filed two issues, either Web IDL or WebRTC needs to change:
https://github.com/heycam/webidl/issues/340
https://github.com/w3c/webrtc-pc/issues/1118

Comment 4 by foolip@chromium.org, Apr 11 2017

Labels: -Needs-Feedback
Status: WontFix (was: ExternalDependency)
Spec-side issues fixed, [TreatNullAs=EmptyString] is no longer used in WebRTC.

Sign in to add a comment