Sfoglia il codice sorgente

Tests (engine): Manual test adjustments.

Marek Lewandowski 5 anni fa
parent
commit
e84b625359
1 ha cambiato i file con 44 aggiunte e 13 eliminazioni
  1. 44 13
      packages/ckeditor5-engine/tests/manual/tickets/4600/1.md

+ 44 - 13
packages/ckeditor5-engine/tests/manual/tickets/4600/1.md

@@ -1,19 +1,50 @@
-### Ignoring events fired by certain elements [#4600](https://github.com/ckeditor/ckeditor5/issues/4600)
+## Ignoring events propagation
 
-Events are logged in browser's console.
+It's a test for ignoring events fired in elements with a `data-cke-ignore-events` attribute ([#4600](https://github.com/ckeditor/ckeditor5/issues/4600)).
 
-### Case 1: Events are ignored and they are not handled by default listeners.
-1. Move mouse cursor over a left container named `Ignored container with data-cke-ignore-events="true"`.
-2. When cursor is already there, start moving it around within container boundaries, start typing in text field and start clicking on text field and button.
-3. Click on the button.
+Events are logged in the browser's console.
 
-**Expected results**: Only then, when the mouse cursor is over the left container, new logs will stop appearing in the console. Clicking inside it, typing in text field and moving mouse cursor inside the container boundaries should not be logged in the console. The `click` event after clicking the button also should not be logged in the console. The `imageLoaded` event from <img> element from ignored container also should not be logged in the console.
+### Case 1: Events ignoring
 
-One note for `focus` nad `blur` events: they will be logged in the console, but only when container lost focus or gets it back, respectively.
+1. Focus the widget by clicking it.
+1. Move mouse cursor over the left container (`Ignored container with data-cke-ignore-events="true"`).
+1. Keep moving the cursor over the container.
 
-### Case 2: Events are not ignored and they are handled by default listeners.
-1. Move mouse cursor over a right container named `Regular container`.
-2. When cursor is already there, start moving it around within container boundaries, start typing in text field and start clicking on text field and button.
-3. Click on the button.
+	**Expected:** no further "Received mousemove event." logs are added.
 
-**Expected results**: Events should be logged in the console. It shouldn't be possible to focus the text field and type anything there. The `click` event after clicking the button should be logged in the console (with `mousedown` and `mouseup` events). The `imageLoaded` event also should be logged in the console - its target element should point to the <img> element from regular container.
+1. Click on a "Click!" button in the container.
+
+	**Expected:** No "Received click event." gets logged.
+
+1. Click on the text input in the container.
+
+	**Expected:** Text input gets focused.
+
+1. Type few characters into the focused input.
+
+	**Expected:** Text is inserted. No keyboard events are logged.
+
+Note: you might get unexpected `focus` nad `blur` events in the process, it's a [known issue](https://github.com/ckeditor/ckeditor5/issues/8309).
+
+### Case 2: Container without event ignoring
+
+1. Focus the widget by clicking it.
+1. Move mouse cursor over the right container (`Regular container`).
+1. Keep moving the cursor over the container.
+
+	**Expected:** "Received mousemove event." logs are added.
+
+1. Click on a "Click!" button in the container.
+
+	**Expected:** "Received click event." is logged.
+
+1. Click on the text input in the container.
+
+	**Expected:** Click events are logged. Editor decides what to do with the selection.
+
+### Case 3: `imageLoaded` event
+
+1. Reload the page (test).
+1. Check the console.
+
+	**Expected:** There's only **one** `Received imageLoaded event.` log.