267411 - Context menu key sometimes fails to work in textarea

Status: VERIFIED DUPLICATE of bug 175568

(Firefox :: Keyboard Navigation, defect)

Description

[Rowne-Wuff Mastaile]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041028 Herojavelina/1.0RC1 (Firefox/1.0 [Moox-M1 Nightlies] polymorph)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041028 Herojavelina/1.0RC1 (Firefox/1.0 [Moox-M1 Nightlies] polymorph)

First of all, I apologize if this has already been reported and/or fixed, I
searched thouroughly but found nothing on this.

On most keyboards these days one would find a 'right mouse' key, I wish I knew
the proper name for this key but unfortunately I don't.  It's on Windows
keyboards however and situated next to the Windows key at the right end of the
keyboard.  Pressing it brings up the context menu of the focused program.

I've found that in almost every case in Firefox it works, even with a default
textarea (which is our problem spot, so to speak, I shall get to that in a
moment).  I created a page at http://mastaile.mine.nu/textarea.html just to test
as I wouldn't want to pester unless I had ran my own tests and that works perfectly.

Yet at phpBB sites (and a few incredibly rare other occurances), this key
refuses to function in the text areas.  Click the Quick Reply field at
mozillaZine and hit the key, the cursor flickers as though it recognizes
something but there's hide nor hare of the menu.  I've tried this with a fresh
profile too, to no avail.

The reason I discovered this is because I tend to be an avid keyboarder and I
use context-menu extensions with forums.  It's not a major issue anyway, just a
bug that could be fixed, if you can even find out what's causing it, I
couldn't... odd as it is, I even tried copying over the script.  Nothing...

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Aaron Leventhal]

We need a reproducable test case. Can you attach one?

Also, please check to see if the cases that fail are always down farther in the
page. There's a bug where the context menu is pushed down off the bottom of the
screen if you're scrolled into a document and press the context menu key.

By the way, you can also use Shift+F10 on Windows and Linux to get the context
menu. On Mac it's Ctrl+space.

Comment 2

[Rowne-Wuff Mastaile]

Attachment: phpBB textarea.

Comment 3

[Rowne-Wuff Mastaile]

Thanks for the informative and polite reply, you've clinched it.  Dead on the
money, so to speak.  Apparently it /is/ a duplicate of the 'context menu
off-screen' bug, I just didn't know it at the time.  A little explanation is in
order; to be able to supply an attachment I had to locally save a forum page and
butcher the code, removing all unnessescary elements and leaving only the parts
that were required as an example.  That HTML there doesn't show the context menu
but if certain <td> fields are removed, the context-menu can just barely be seen
at the bottom of my screen at my resolution.  This seems to be the case with
every phpBB though, I've come across it at every one of them I've been to.  So
I'm putting this down to bad HTML in the forum template.

What I might do is make a post on the mozillaZine forums, asking if anyone knows
whether it might be possible to write a 'fixed screen position for <textarea>
context menus' extension.  Unless you have any ideas at all that might help? 
Anyway, thanks for your time and for the reply.

(In reply to comment #1)
> We need a reproducable test case. Can you attach one?
> 
> Also, please check to see if the cases that fail are always down farther in the
> page. There's a bug where the context menu is pushed down off the bottom of the
> screen if you're scrolled into a document and press the context menu key.
> 
> By the way, you can also use Shift+F10 on Windows and Linux to get the context
> menu. On Mac it's Ctrl+space.

Comment 4

[Aaron Leventhal]

This is probably a DUP of bug 175668.

If you build your own Mozilla you could try applying the patch in that bug and
see if it gets fixed for you.

Comment 5

[Troodon]

(In reply to comment #4)
The correct bug is bug 175568.

Comment 6

[Aaron Leventhal]

*** This bug has been marked as a duplicate of 175568 ***