New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 613818 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome doesn’t collapse context menu separators if they are at the end of the context menu box

Reported by zambonif...@gmail.com, May 21 2016

Issue description

If you use the `contextMenus` API available to extensions and apps, Chrome collapses all context menu items of type “separator” into one. I believe that if a separator is at the end of a context menu box, it should disappear, but it currently doesn’t (50.0.2661.102 stable).

I’ve attached both the `.crx` and the source of an app demonstrating this problem. You will, however, need to install from the `.crx` to actually see the problem.
 
context.crx
1.1 KB Download
context.zip
920 bytes Download
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Tested this issue on Ubuntu 14.04 using chrome latest stable- 50.0.2661.102 by following steps mentioned below.
1. Downloaded the file context.zip
2. Loaded the context.zip file by enabling developer mode. 
3. Launched app from chrome://extensions and observed a blank tab opens without any content.

zambonifofex@ - Will you mind providing a scree-cast or screen-shot of this issue for better understanding where we can reproduce it from chrome TE end.

Thanks!
Hello.

I cannot provide a screenshot because the context menu isn’t captured on screenshots (at least in my OS, Ubuntu 16.04).

However, you did forget something: the context menu! You should right-click the blank window to see the problem.

You may need to use the .CRX instead of the .ZIP, since chrome automatically adds extra items to the context menu for unpacked extensions.
Project Member

Comment 3 by sheriffbot@chromium.org, May 24 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: rnimmagadda@chromium.org
Labels: -Needs-Review Needs-Feedback
Owner: ----
@zambonifofex: Could you please have a look at the attached video and let us know if this is the correct procedure to repro this issue.

Thank you.
613818.ogv
4.9 MB Download
Are you sure you are using the CRX and not loading it from the source? “Reload”, “Simulate browser restart”, “Inspect” and “Inspect background page” are exactly the items I told Chrome adds for unpackaged apps. When these are there, you cannot see the problem.
Here’s a video.
context.webm
7.7 MB Download
Project Member

Comment 7 by sheriffbot@chromium.org, May 26 2016

Labels: -Needs-Feedback Needs-Review
Owner: rnimmagadda@chromium.org
Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Platform>Extensions
Labels: -Pri-3 -Needs-Review M-53 OS-Mac OS-Windows Pri-2
Owner: ----
Status: Untriaged (was: Unconfirmed)
Able to repro this issue on Windows 7, MAC (10.11.5) & Ubuntu Trusty (14.04) for Google Chrome Canary Version - 53.0.2753.0

This is a Non-Regression issue existing since M46 - # 46.0.2455.0.

Before this build, upon launching the provided app, the window just closes off.
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 9 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: asargent@chromium.org
Labels: -Pri-2 Hotlist-GoodFirstBug Pri-3
Status: Available (was: Untriaged)
It would be nice to fix this, but marking as low priority since there is a pretty easy workaround. 

The code that controls this is ContextMenuMatcher::AppendExtensionItems in chrome/browser/extensions/context_menu_matcher.cc if anyone wants to have a look. Patches welcome!
Cc: -asargent@chromium.org
Status: Fixed (was: Available)
Tested this on Mac (10.12.5) and Ubuntu Trusty (14.04) for Chrome Stable 59.0.3071.115.
See screenshots. This appears to be fixed. 


tested_linux.png
41.8 KB View Download
tested_mac.png
39.3 KB View Download

Sign in to add a comment