LayoutTests/imported/web-platform-tests/uievents/order-of-events/README.md - Issue 1213063003: update-w3c-deps import using blink 3b531d5bb326db09a7298b222030cf274590473d:

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/imported/web-platform-tests/uievents/order-of-events/README.md

Issue 1213063003: update-w3c-deps import using blink 3b531d5bb326db09a7298b222030cf274590473d: (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Add rtcpeerconnection-idl-expected.txt Created 5 years, 5 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/imported/web-platform-tests/uievents/interface/README.md ('k') | LayoutTests/imported/web-platform-tests/webrtc/rtcpeerconnection/rtcpeerconnection-idl.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 Order of events

	2 ============================

	3

	4 Testing of how events fire in relation to one another

	5

	6 (this is the big work item)

	7

	8 Expecting to need:

	9 * braindead test (does it work at all?)

	10 * specific functional tests

	11 * specific edge cases

	12

	13 Notes:

	14 * small tests so that they can be given specific names for what's broken if it fails

	15 * include a link to the corresponding test in the spec.

OLD	NEW