LayoutTests/fast/events/keyboard-event-source-device-event-sender-expected.txt - Issue 1182313006: Populates sourceDevice attribute into KeyboardEvent

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: LayoutTests/fast/events/keyboard-event-source-device-event-sender-expected.txt

Issue 1182313006: Populates sourceDevice attribute into KeyboardEvent (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Rebase Created 5 years, 6 months 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

« no previous file with comments | « LayoutTests/fast/events/keyboard-event-source-device-event-sender.html ('k') | LayoutTests/fast/events/uievent-with-inputdevice.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 Test that mouse events from real mouse device should have a sourceDevice and its firesTouchEvents should be false.	1 Test that keyboard events should have a sourceDevice and its firesTouchEvents sh ould be false.

2	2

3 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".	3 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".

4	4

5	5

6 mousemove	6 keydown

7 PASS event.sourceDevice is non-null.	7 PASS event.sourceDevice is non-null.

8 PASS event.sourceDevice.firesTouchEvents is false	8 PASS event.sourceDevice.firesTouchEvents is false

9 mousedown	9 keypress

10 PASS event.sourceDevice is non-null.	10 PASS event.sourceDevice is non-null.

11 PASS event.sourceDevice.firesTouchEvents is false	11 PASS event.sourceDevice.firesTouchEvents is false

12 mouseup	12 keyup

13 PASS event.sourceDevice is non-null.

14 PASS event.sourceDevice.firesTouchEvents is false

15 click

16 PASS event.sourceDevice is non-null.	13 PASS event.sourceDevice is non-null.

17 PASS event.sourceDevice.firesTouchEvents is false	14 PASS event.sourceDevice.firesTouchEvents is false

18 PASS successfullyParsed is true	15 PASS successfullyParsed is true

19	16

20 TEST COMPLETE	17 TEST COMPLETE

21	18

OLD	NEW