New issue
Advanced search Search tips

Issue 847230 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Context-menu hard to access at the bottom of the screen

Reported by orsch...@gmail.com, May 28 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. Went to LinkedIn
2. Typed a reply with a misspelled word
3. Right mouse click on the word to correct it

What is the expected behavior?
I expected the context menu to open completely.

What went wrong?
Instead it opened with most entries not visible. 

See this video:

https://www.useloom.com/share/a4a8acccc2b942228c46444fd9f27252

An issue with GTK/GNOME or Chrome?

Did this work before? N/A 

Chrome version: 66.0.3359.181  Channel: stable
OS Version: Fedora 28
Flash Version:
 
Labels: Needs-Triage-M66
Cc: vamshi.kommuri@chromium.org
Labels: Needs-Feedback Triaged-ET
Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 66.0.3359.181 and on the latest 69.0.3443.0 using Ubuntu 14.04 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://in.linkedin.com/ and signed into it
3. Clicked on "Reply" for a random post.
4. Typed a word which is misspelled, right clicked on it.
We were able to see all the entries in the menu. Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and let us know if anything missed from our end. Also please check the same in a new profile with out any apps and extensions, let us know if the issue still persists. 
847230.ogv
2.2 MB View Download

Comment 3 by orsch...@gmail.com, May 29 2018

Hey vamshi! :-)

Please compare your recording with mine. You opened the menu while being at the top of the screen. I recorded while being at the bottom edge. Can you retry please?

Thanks!
Project Member

Comment 4 by sheriffbot@chromium.org, May 29 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback
As per comment #3 we have tested this issue and unable to reproduce this on reported chrome version 66.0.3359.181 and latest chrome stable 67.0.3396.62 using ubuntu 14.04. Attaching Screencast for reference.

@ Reporter: Could you please upgrade your chrome browser and let us if the issue still persists.

you can download latest chrome builds here :https: ""//www.chromium.org/getting-involved/dev-channel"".


Thanks.!
847230.webm
4.2 MB View Download

Comment 6 by orsch...@gmail.com, May 31 2018

Thanks! Let's close for now. I tested again and also cannot reproduce anymore. :-(

Video: https://www.useloom.com/share/90717245b9ad4e098eb582787618274c
Project Member

Comment 7 by sheriffbot@chromium.org, May 31 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
As per comment#6 by reporter the issue no longer seems to be reproducible from his end too, hence closing this issue and marking it as Won't fix.

Thanks!

Sign in to add a comment