Revision 5ffa5051c36c670be1a38000de442b002920ac12 authored by Joe Downing on 22 March 2018, 07:35:35 UTC, committed by Blink WPT Bot on 22 March 2018, 07:45:48 UTC
This change moves the KeyboardLock API methods to a 'keyboard' namespace on the Navigator object. We are doing this work now as there has been a request for additional keyboard functionality that would also be placed on the new keyboard object and we wanted to move the KeyboardLock methods there for consistency before we launch. KeyboardLock API Spec is here: https://w3c.github.io/keyboard-lock/#API Old calling pattern: Navigator.keyboardLock(); Navigator.keyboardUnlock(); New calling pattern: Navigator.keyboard.lock(); Navigator.keyboard.unlock(); Note: The main logic in the KeyboardLock.cpp class and tests is the same as it was, however the file changed enough that git does not recognize it as a file move. BUG=680809 Change-Id: I234b2ab12d5ecd44c894ed5103863fd96fd548d4 Reviewed-on: https://chromium-review.googlesource.com/969656 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Gary Kacmarcik <garykac@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#544996}
1 parent 1a8c195
extended-payload-length.html
<!doctype html>
<title>WebSockets : Boundary-value tests for the 'Extended payload length' field in RFC6455 section5.2 'Base Framing Protocol'</title>
<meta name=timeout content=long>
<script src=/resources/testharness.js></script>
<script src=/resources/testharnessreport.js></script>
<script src=constants.js?pipe=sub></script>
<meta name="variant" content="">
<meta name="variant" content="?wss">
<div id=log></div>
<script>
async_test(function(t){
var ws = new WebSocket(SCHEME_DOMAIN_PORT+'/echo');
var datasize = 125;
var data = null;
ws.onopen = t.step_func(function(e) {
data = new Array(datasize + 1).join('a');
ws.send(data);
});
ws.onmessage = t.step_func(function(e) {
assert_equals(e.data, data);
t.done();
});
}, "Application data is 125 byte which means any 'Extended payload length' field isn't used at all.", {timeout:20000});
async_test(function(t){
var ws = new WebSocket(SCHEME_DOMAIN_PORT+'/echo');
var datasize = 126;
var data = null;
ws.onopen = t.step_func(function(e) {
data = new Array(datasize + 1).join('a');
ws.send(data);
});
ws.onmessage = t.step_func(function(e) {
assert_equals(e.data, data);
t.done();
});
}, "Application data is 126 byte which starts to use the 16 bit 'Extended payload length' field.", {timeout:20000});
async_test(function(t){
var ws = new WebSocket(SCHEME_DOMAIN_PORT+'/echo');
var datasize = 0xFFFF;
var data = null;
ws.onopen = t.step_func(function(e) {
data = new Array(datasize + 1).join('a');
ws.send(data);
});
ws.onmessage = t.step_func(function(e) {
assert_equals(e.data, data);
t.done();
});
}, "Application data is 0xFFFF byte which means the upper bound of the 16 bit 'Extended payload length' field.", {timeout:20000});
async_test(function(t){
var ws = new WebSocket(SCHEME_DOMAIN_PORT+'/echo');
var datasize = 0xFFFF + 1;
var data = null;
ws.onopen = t.step_func(function(e) {
data = new Array(datasize + 1).join('a');
ws.send(data);
});
ws.onmessage = t.step_func(function(e) {
assert_equals(e.data, data);
t.done();
});
}, "Application data is (0xFFFF + 1) byte which starts to use the 64 bit 'Extended payload length' field", {timeout:20000});
</script>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...