Comment #10 on issue 5695 by sy3620: Context menu for title bar doesn't  
appear when a tab's context menu was open
http://code.google.com/p/chromium/issues/detail?id=5695

I think chrome browser lacks consistency in displaying context menu.


* Current State
---------------------------------------------------------------
  context menu for the 'Tab' : Show up on right mouse button 'Release'
  context menu for the 'App' : Show up on right mouse button 'Press'
---------------------------------------------------------------

This inconsistent concept (one by 'Release' and the other by 'Press')
is not natural (in the UI point of view) and can cause problems.


Currently, when the right mouse button is 'Pressed' on the title bar,
its handler seems to take following two steps in order.

1. Close the current context menu if it exists.
2. Create new context menu.

Processing two operations (Closing and Creating) at one time ('Press')
can cause conflict problems.

- If the current context menu is for an 'App', there's no problem. But
    if it is for a 'Tab', it seems that above two steps come into the  
conflict
    and doesn't work well.


*****Suggestion *****

So, Divide two operations (Closing and Creating) into seperate handlers.
- Closing always on 'Press' and Creating always on 'Release'.

If this concept is applied, no conflict can occur.
- When the  mouse button is 'Pressed', current (for a Tab or for an App.)
    context menu is closed and when the button is 'Released', new context
    menu is created.

And, it is natural that displaying context menu is always done by 'Release'
operation. (MS IE also uses this concept.)


* Suggested State:
---------------------------------------------------------------
  context menu for the 'Tab' : Show up on right mouse button 'Release'
  context menu for the 'App' : Show up on right mouse button 'Release'
---------------------------------------------------------------


I wanna know your opinions about this.



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to