Bug 251817

Summary: www/firefox Ctrl-Alt-R should enter Reader view, should not restart Firefox
Product: Ports & Packages Reporter: Graham Perrin <grahamperrin>
Component: Individual Port(s)Assignee: freebsd-gecko (Nobody) <gecko>
Status: Open ---    
Severity: Affects Some People CC: debdrup
Priority: --- Flags: bugzilla: maintainer-feedback? (gecko)
Version: Latest   
Hardware: Any   
OS: Any   
See Also: https://bugzilla.mozilla.org/show_bug.cgi?id=1829544
Attachments:
Description Flags
Enter Reader View
none
Restart (Developer) none

Description Graham Perrin freebsd_committer freebsd_triage 2020-12-13 16:12:46 UTC
Created attachment 220531 [details]
Enter Reader View

Control-Alt-R is assigned to two menu commands: 

1. Enter Reader View
2. Restart (Developer)

I did not realise the conflict until I aimed for a Reader view of a page; Firefox unexpectedly restarted. 

Please, can we remove the shortcut from 'Restart (Developer)'?

Thanks
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2020-12-13 16:13:23 UTC
Created attachment 220532 [details]
Restart (Developer)
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2021-01-31 03:30:39 UTC
If it helps, <https://www.reddit.com/r/freebsd/comments/kc9j55/firefox_restart_developer_ctrlaltr_conflict_with/gkt6fyu/>: 

> This happens to me on an Ubuntu box!

<https://new.reddit.com/r/freebsd/comments/kc9j55/firefox_restart_developer_ctrlaltr_conflict_with/> originally found: 

>> … No such conflict with Firefox in Manjaro: …
Comment 3 Daniel Ebdrup Jensen freebsd_committer freebsd_triage 2022-05-14 15:07:11 UTC
If it's related to Developer Tools, it isn't disabled by setting DisableDeveloperTools in distribution/policies.json as documented on https://github.com/mozilla/policy-templates - so whatever's responsible for this seems to be in the keybinds themselves.

Another datapoint is that according to reports from #Firefox on Libera IRC, it doesn't happen on Firefox for Windows, even with developer mode enabled.

Someone with more intimate knowledge of the Firefox sources might be able to patch this behaviour, and hopefully get the patch applied upstream (since it doesn't appear to be a problem with the port, specifically).
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2023-04-29 16:50:16 UTC
<https://bugzilla.mozilla.org/show_bug.cgi?id=1829544#c3> there's a question, can someone from @gecko respond?

Thanks