Opened 4 years ago

Last modified 4 years ago

#13012 confirmed Bug

Focus is not properly restored after closing the context menu

Reported by: Irina Owned by:
Priority: Low Milestone:
Component: General Version:
Keywords: IBM Cc: Satya Minnekanti

Description

Steps to reproduce:

  1. create a table
  2. click inside the 1st cell
  3. right click to get a context menu
  4. place the cursor at the edge of the context menu
  5. close the menu without selecting an option by left click, to restore the focus inside the cell
  6. start typing

result: Unable to type in the 1st cell. Path bar displays 'body->table->tbody->tr->td' but focus is not in the cell.

To make it easy to reproduce, remove rounded borders from cke_panel class in moono skin, e.g.

-moz-border-radius: 3px;
-webkit-border-radius: 3px;
border-radius: 3px;

Chrome and FF were used for testing

Change History (4)

comment:1 Changed 4 years ago by Jakub Ś

I very much like your test cases because they are accurate and easy to reproduce but in some very rare cases, I personally think, they focus too much on not important details. Like in this case.

When you select menu option or even when you open context menu selection in table is remembered and focus is moved to menu panel. When select some action it is performed and selection is brought back to its position.

  • In this TC (I have focused on table properties option) I needed to hover over pixel next to border or over border.
  • The "Table Properties" option isn't marked/grayed in this case and when I click in that area I loose menu panel focus (best seen in Google Chrome because it uses these big ugly focus borders).
  • Next I needed to put cursor 1 pixel next to border. It is hard but it is possible to have arrow cursor right next to border (Start moving mouse cursor from outside of menu and stop at this pixel).
  • Result: Elements path shows "th" but cursor is nowhere to be found. I can see this problem even in CKEditor 3.x (it is even easier to reproduce it there)

The questions that came to my mind are: who does that and how many users will such TC affect?

On one hand you might argue that this is some minor bug but on the other hand this is such an edge case that I can't confirm it. I will consult this with my colleagues and if they have different opinion I will confirm it then.

comment:2 Changed 4 years ago by Piotrek Koszuliński

Priority: NormalLow
Status: newconfirmed
Version: 4.4.7

Well... it is a bug, so I confirm it. But it's such an edge case that I don' think we'll ever work on it.

comment:3 Changed 4 years ago by Irina

Thank you for looking into this. I agree this is the minor defect. Unfortunately, we are not using rounded borders in our skin which makes this issue more common. Also some of our products add custom borders so for them its always reproducible. This issue was reported in a customer PMR.

comment:4 Changed 4 years ago by Piotrek Koszuliński

Could you provide an example of styling that your products use? Perhaps something with the styling can be improved or it will raise an importance of this bug.

Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy