Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Đã giải quyết

alt-d stops working until I restart Firefox

phsiii

On two different Windows machines, current Firefox (153.0.1), the alt-d shortcut stops working: it does nothing until I restart Firefox. Then it works again for a while. I've tried about:keyboard and it's not reset there. I tried all combinations: Clear, Reset, setting it to alt-d explicitly. None of those worked. But when I set it to alt-a, that worked--but then resetting back to alt-d again didn't work. That shortcut is muscle memory at this point, so it's quite distressing. Not sure what diagnostics might be available to help here, happy to try anything.

Full disclosure: Both machines are Windows 10 but since that's stable, I find it hard to believe that's related.

On two different Windows machines, current Firefox (153.0.1), the alt-d shortcut stops working: it does nothing until I restart Firefox. Then it works again for a while. I've tried about:keyboard and it's not reset there. I tried all combinations: Clear, Reset, setting it to alt-d explicitly. None of those worked. But when I set it to alt-a, that worked--but then resetting back to alt-d again didn't work. That shortcut is muscle memory at this point, so it's quite distressing. Not sure what diagnostics might be available to help here, happy to try anything. Full disclosure: Both machines are Windows 10 but since that's stable, I find it hard to believe that's related.
Đọc câu trả lời này trong ngữ cảnh

Giải pháp được chọn

There's some preliminary investigation in bugzilla.mozilla.org/2050947 — potentially linked to update notification panel consuming that shortcut — while the other one should be unaffected.

Tất cả các câu trả lời (11)

If you compare that to Ctrl+L — does that one keep working, or it also ceased to function over time / at the same moment?

Will try that when it breaks again! Of course now after doing it repeatedly it won't misbehave for weeks...

Giải pháp được chọn

There's some preliminary investigation in bugzilla.mozilla.org/2050947 — potentially linked to update notification panel consuming that shortcut — while the other one should be unaffected.

OK, it happened again, and <ctrl>L still works. I have NOT restarted that browser just in case there's something useful to try.

That Bugzilla says "Notably from bug 2059992 comment 3 if your browser console shows the same?" and then shows something but I'm not sure how to reproduce that, or whether it would help for me to do so.

It would be interesting to open Browser Console (Ctrl + Shift + J) and see if there's anything relevant at the end, esp. in red like Uncaught Error.

Like'a'dis:

Uncaught Error: PanelUI._onNotificationButtonEvent: couldn't find notification

   _onNotificationButtonEvent chrome://browser/content/customizableui/panelUI.js:1222
   handleEvent chrome://browser/content/customizableui/panelUI.js:393
   customEventDelegator chrome://global/content/elements/popupnotification.js:179
   slotContents chrome://global/content/elements/popupnotification.js:186

...and then Firefox hung and I had to restart it. It did have an update pending, and of course now <cntrl>D works fine and produces no console output.

Nice, that looks exactly as the already suspected change, I tracked the lines from a different report to the same bug — it seems whenever there's a pending update its button (also Alt–D access key) clashes with the existing app shortcut.

I'll add your logs to the ticket timeline, thanks for confirming!

Thanks, jbr! Should I close this, or leave it open? Is there a canonical report I can add myself to so I get notified when a fix is released?

You can just mark the post with the bugzilla link as a "solution", so it's surfaced for others searching the same. Thanks!

I will update this thread once there's any update in tracking of the bug, and you can also of course subscribe to "CC" in the bug to follow any updates in the timeline.

Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.