third_party/WebKit/LayoutTests/fast/events/remove-text-node-in-mouseup.html - Issue 2812613004: Fire a click event even when a clicked text node is removed in mouseup

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/fast/events/remove-text-node-in-mouseup.html

Issue 2812613004: Fire a click event even when a clicked text node is removed in mouseup (Closed)

Patch Set: Created 3 years, 8 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 | « no previous file | third_party/WebKit/LayoutTests/fast/events/remove-text-node-in-mouseup-expected.txt » ('j') | third_party/WebKit/Source/core/input/EventHandler.cpp » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 <!DOCTYPE html>

	2 <p>This test ensures Blink does fire a click event on the parent element of a cl icked text node

	3 even when the text node has been removed in mouseup event.</p>

	4 <div id="test"></div>
	yosin_UTC9 2017/04/12 06:10:44 It is better to use w3c test handler to avoid havi It is better to use w3c test handler to avoid having expected.txt hayato 2017/04/12 06:16:06 We can't because the test needs eventSender. We can't because the test needs eventSender. kochi 2017/04/12 06:44:39 I think it's okay to use testharness.js for tests Show quoted text On 2017/04/12 06:16:06, hayato wrote: > We can't because the test needs eventSender. > I think it's okay to use testharness.js for tests that cannot be upstreamed to WPT. hayato 2017/04/12 06:52:22 It would be, but I would prefer consistency with o It would be, but I would prefer consistency with other tests in this directory.
	5 <div id="target" style="display:inline-block" onmouseup="mouseup()" onclick="tes t.innerHTML = 'PASS';">Click Here</div>

	6 <script>

	7 const test = document.getElementById('test');

	8 const target = document.getElementById('target');

	9

	10 function mouseup() {

	11 test.innerHTML = 'FAIL';

	12 target.firstChild.remove();

	13 }

	14

	15 if (window.testRunner) {

	16 testRunner.dumpAsText();

	17 if (!window.eventSender) {

	18 test.innerHTML = 'FAIL - this test requires eventSender';

	19 } else {

	20 eventSender.mouseMoveTo(target.offsetLeft + target.offsetWidth / 2,

	21 target.offsetTop + target.offsetHeight / 2);

	22 eventSender.mouseDown();

	23 eventSender.leapForward(200);

	24 eventSender.mouseUp();

	25 }

	26 }

	27 </script>

OLD	NEW