We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Has contentAreaContextMenu had its ID changed?

  • 1 wotmołwa
  • 1 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot slidinghorn

more options

There is a known issue for some i3 users that when we click the right-mouse button, the context menu will pop up in a position where the first item in the menu is already highlighted, so when the right mouse button is released, it automatically "selects" that item. So if we want to copy a link, for example, we have to be careful to move the mouse before releasing the button or that link will immediately be opened in a new tab.

What some of us have done in the past is to create a userChrome.css file setting a top (and/or left) margin for that menu, which fixes the issue.

In the latest version(s?) of Firefox, this no longer works (but other userChrome.css rules I have set up continue to work), so I'm assuming that the ID of the context menus has been changed. What is the ID now?

There is a known issue for some i3 users that when we click the right-mouse button, the context menu will pop up in a position where the first item in the menu is already highlighted, so when the right mouse button is released, it automatically "selects" that item. So if we want to copy a link, for example, we have to be careful to move the mouse before releasing the button or that link will immediately be opened in a new tab. What some of us have done in the past is to create a userChrome.css file setting a top (and/or left) margin for that menu, which fixes the issue. In the latest version(s?) of Firefox, this no longer works (but other userChrome.css rules I have set up continue to work), so I'm assuming that the ID of the context menus has been changed. What is the ID now?

Wubrane rozrisanje

Figured it out. The ID has not changed, but apparently now you need to add !important in order for the margin to be recognized.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (1)

more options

Wubrane rozrisanje

Figured it out. The ID has not changed, but apparently now you need to add !important in order for the margin to be recognized.