Added dataChannel.id text field to peerconnection.html

Added dataChannel.id text field to make it easier to test that Chrome/WebRTC reuses the dataChannel id on the same
peerConnection.

Feature added in issue:
https://code.google.com/p/webrtc/issues/detail?id=2646

BUG=NONE
TEST=Manual P2P call, dataChannel.id is only displayed when
dataChannel.readyState = 'open'.
NOTRY=TRUE

Committed: https://crrev.com/2d454cf9a5f405dfd78cf581f0e414ff628857b8
Cr-Commit-Position: refs/heads/master@{#291887}

[jansson, 2014-07-21 09:25:38]

Could you perform a code review? Thanks!

[tnakamura, 2014-07-21 13:38:26]

https://codereview.chromium.org/405093004/diff/20001/chrome/test/data/webrtc/...
File chrome/test/data/webrtc/manual/peerconnection.html (right):

https://codereview.chromium.org/405093004/diff/20001/chrome/test/data/webrtc/...
chrome/test/data/webrtc/manual/peerconnection.html:117: <input type="text"
id="data-channel-id" size="10"/><br/>
Should the data channel ID field also be disabled/read-only? Or did you want to
allow the user to somehow specify an ID when creating a channel?

[jansson, 2014-07-21 13:54:29]

On 2014/07/21 13:38:26, tnakamura wrote:
>
https://codereview.chromium.org/405093004/diff/20001/chrome/test/data/webrtc/...
> File chrome/test/data/webrtc/manual/peerconnection.html (right):
> 
>
https://codereview.chromium.org/405093004/diff/20001/chrome/test/data/webrtc/...
> chrome/test/data/webrtc/manual/peerconnection.html:117: <input type="text"
> id="data-channel-id" size="10"/><br/>
> Should the data channel ID field also be disabled/read-only? Or did you want
to
> allow the user to somehow specify an ID when creating a channel?
I did not think of that, good point! Will disable it.

[jansson, 2014-07-21 14:00:09]

data-channel-id is now disabled as there is no logic to handle user entered
data.

[tnakamura, 2014-07-21 15:28:41]

lgtm

[jansson, 2014-07-22 06:36:10]

The CQ bit was checked by jansson@chromium.org

[commit-bot: I haz the power, 2014-07-22 06:36:33]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jansson@chromium.org/405093004/40001

[commit-bot: I haz the power, 2014-07-22 06:36:34]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-22 06:36:35]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[jansson, 2014-07-22 08:17:02]

xians@ could you have a look? It does not seem like tnakamura@ has commit rights
to LGTM this.

Thanks!

[jansson, 2014-08-26 11:37:04]

jansson@chromium.org changed reviewers:
+ mcasas@chromium.org
- xians@chromium.org

[jansson, 2014-08-26 11:37:04]

mcasas@ could PTAL?

Submitted a while ago but fell between the chairs, just made a rebase to make
sure it's up to date.

[mcasas, 2014-08-26 11:40:39]

The CQ bit was checked by mcasas@chromium.org

[mcasas, 2014-08-26 11:40:39]

lgtm

[commit-bot: I haz the power, 2014-08-26 11:40:47]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jansson@chromium.org/405093004/60001

[commit-bot: I haz the power, 2014-08-26 11:41:29]

Committed patchset #4 (60001) as 164b1fba6d25048265f2a788a5f3c00df3b1e450

[commit-bot: I haz the power, 2014-09-10 02:42:13]

Patchset 4 (id:??) landed as
https://crrev.com/2d454cf9a5f405dfd78cf581f0e414ff628857b8
Cr-Commit-Position: refs/heads/master@{#291887}