Skip to content
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

[Gecko Bug 1610422] part 1. Pull in missing upstream changes for RTCPeerConnection-ondatachannel.html. #21755

Merged
merged 3 commits into from Feb 17, 2020

Conversation

moz-wptsync-bot
Copy link
Collaborator

It looks like most of the changes from
#16038 we have already, except
some whitespace bits.

Differential Revision: https://phabricator.services.mozilla.com/D60469

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1610422
gecko-commit: adfbba5ae5f7acc18ae9866badd0e2a242bc2ee1
gecko-integration-branch: central
gecko-reviewers: jgraham

…channel.html.

It looks like most of the changes from
#16038 we have already, except
some whitespace bits.

Differential Revision: https://phabricator.services.mozilla.com/D60469

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1610422
gecko-commit: adfbba5ae5f7acc18ae9866badd0e2a242bc2ee1
gecko-integration-branch: central
gecko-reviewers: jgraham
…Channel.html.

This is a clean revert of the changes bug 1609859 made to
RTCPeerConnection-createDataChannel.html.  It's separated out for review ease;
these changes are reinstated 2 changesets later.

Differential Revision: https://phabricator.services.mozilla.com/D60470

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1610422
gecko-commit: ada3f82c018146820be8cef169d5b91ec081ceca
gecko-integration-branch: central
gecko-reviewers: jgraham
…eateDataChannel.html.

The changes are as follows:

1) Add an id (and a change in the test label) in the test that now ends up
reading:

  const channel = pc.createDataChannel('', { negotiated: true, id: 42 });

2) Add some whitespace bits.
3) Removes a bogus test (thus fixing bug 1550497).  The test is bogus because
   `null` converts to 0 when converting to `unsigned short`, and that's a
   perfectly valid id value.

Compared to upstream, that leaves the following local changes:

* Tests for the "id in the unsigned short range, maybe invalid, but
  'negotiated' not set" case.
* A clarification for one of the test descriptions.
* Tests for the "id out of the unsigned short range" case.

These changes are upstreamed in #21285

Differential Revision: https://phabricator.services.mozilla.com/D60472

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1610422
gecko-commit: 1ceab0b9f948b8bdce771c98d0ab1101b5deeb1d
gecko-integration-branch: central
gecko-reviewers: jgraham
Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Firefox project.

@jgraham jgraham closed this Feb 12, 2020
@moz-wptsync-bot moz-wptsync-bot merged commit 2d1c196 into master Feb 17, 2020
@moz-wptsync-bot moz-wptsync-bot deleted the gecko/1610422 branch February 17, 2020 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants