LayoutTests/fast/events/menu-key-context-menu-position-expected.txt - Issue 766143002: Fix contextmenu event location for menu key in an iframe

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/menu-key-context-menu-position-expected.txt

Issue 766143002: Fix contextmenu event location for menu key in an iframe (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Added description of testcase. Created 6 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

« LayoutTests/fast/events/menu-key-context-menu-position.html ('K') | « LayoutTests/fast/events/menu-key-context-menu-position.html ('k') | LayoutTests/fast/events/resources/menu-key-context-menu-position-frame.html » ('j') | LayoutTests/fast/events/resources/menu-key-context-menu-position-frame.html » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 Verifies that when element is focused in frames then selection by menu key, cont ext menu should come on focused element. Succeeds if context menu is coming on t he focused element and event co-ordinates are at center of the elements bounding box.

	2

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

	4

	5
	Rick Byers 2015/01/05 18:16:24 If the test was actually working, you'd have 'PASS If the test was actually working, you'd have 'PASS ...' entries here indicating that the shouldBe calls succeeded. Somehow your test isn't actually running - maybe the onload is never called? Deepak 2015/01/06 13:27:02 You are right, runTest was not getting called, so Show quoted text On 2015/01/05 18:16:24, Rick Byers wrote: > If the test was actually working, you'd have 'PASS ...' entries here indicating > that the shouldBe calls succeeded. Somehow your test isn't actually running - > maybe the onload is never called? You are right, runTest was not getting called, so we are not getting PASS for shouldbe() This is due to frameset in body.
	6 PASS successfullyParsed is true

	7

	8 TEST COMPLETE

	9

OLD	NEW