Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

fn-F12 is different with Sonoma

  • 2 ответа
  • 0 имеют эту проблему
  • 4 просмотра
  • Последний ответ от GilDawson

more options

Hi--

I recently upgraded from Mojave to Sonoma 14.2, and Firefox 120.0.1.

In Mojave, fn-F12 used to invoke a "Dashboard" with applets like Dictionary and Thesaurus.

With Sonoma, fn-F12 causes the bottom part of Firefox's frontmost window to become a web developer tool, same as ⌥⌘I, instead.

Can I get my Dictionary and Thesaurus back?

--Gil

Hi-- I recently upgraded from Mojave to Sonoma 14.2, and Firefox 120.0.1. In Mojave, fn-F12 used to invoke a "Dashboard" with applets like Dictionary and Thesaurus. With Sonoma, fn-F12 causes the bottom part of Firefox's frontmost window to become a web developer tool, same as ⌥⌘I, instead. Can I get my Dictionary and Thesaurus back? --Gil

Выбранное решение

You can set devtools.f12_enabled => false on the about:config page.

You can open the about:config page via the location/address bar. On the warning page, click "Accept the Risk and Continue" to open about:config.

(edited to set the correct false)

Прочитайте этот ответ в контексте 👍 2

Все ответы (2)

more options

Выбранное решение

You can set devtools.f12_enabled => false on the about:config page.

You can open the about:config page via the location/address bar. On the warning page, click "Accept the Risk and Continue" to open about:config.

(edited to set the correct false)

Изменено cor-el

more options

Thanks, cor-el.

That change works, in that Firefox no longer responds. However, my "Dashboard" still does not appear. Evidently, this is a new feature of Sonoma.

My apology for guessing that Firefox did this, and thanks for making the culprit clear for me.

--Gil