third_party/WebKit/LayoutTests/imported/wpt/input-events/inputevent-constructor.html - Issue 2570203004: Fix low risk nullable => non nullable change for NavigatorLanguage.language

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: third_party/WebKit/LayoutTests/imported/wpt/input-events/inputevent-constructor.html

Issue 2570203004: Fix low risk nullable => non nullable change for NavigatorLanguage.language (Closed)

Patch Set: Revert InputEvent Created 4 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 <!DOCTYPE html>

	2 <title>InputEvent Constructor Tests</title>

	3 <script src="/resources/testharness.js"></script>
	dtapuska 2016/12/15 17:00:03 Shouldn't imported tests first be added to the git Shouldn't imported tests first be added to the github repository and then pulled into this directory? foolip 2016/12/15 22:43:33 Until now, yes, but https://crbug.com/657117 is ab Show quoted text On 2016/12/15 17:00:03, dtapuska wrote: > Shouldn't imported tests first be added to the github repository and then pulled > into this directory? Until now, yes, but https://crbug.com/657117 is about making it possible to write tests directly in our copy and have them exported, so we're creating real test CLs for jeffcarp@ to take through the process. lunalu@, since InputEvent and its data attribute is defined in https://w3c.github.io/uievents/#interface-inputevent I think putting this test in wpt/uievents/ would be more appropriate.
	4 <script src="/resources/testharnessreport.js"></script>

	5 <script>

	6 test(function() {

	7 var e = new InputEvent('type');

	8 assert_equals(e.inputType, '');

	9 assert_equals(e.data, null);

	10 assert_equals(e.dataTransfer, null);

	11 assert_false(e.isComposing);

	12 }, 'Test InputEvent constructor without inputEventInit dictionary');

	13

	14 test(function() {

	15 var e = new InputEvent('type', { data: null, isComposing: true });

	16 assert_equals(e.data, null, 'inputevent.data should be non null');

	17 assert_true(e.isComposing);

	18 }, 'Test InputEvent construtor with inputEventInit dictionary');

	19 </script>

OLD	NEW

« no previous file with comments | « third_party/WebKit/LayoutTests/W3CImportExpectations ('k') | third_party/WebKit/Source/core/frame/NavigatorLanguage.idl » ('j') | no next file with comments »