New issue
Advanced search Search tips

Issue 790916 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature



Sign in to add a comment

Feature request: ability to EDIT the order and contents of MENUS

Reported by phuber...@gmail.com, Dec 1 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
Likely you know Firefox has HAD an extension enabling the user to customize menus by manually reordering menu entries and by suppressing entries not needed by the user.

Such a feature could make use of chromium more efficient for the end user.

What is the expected behavior?

What went wrong?
N/A

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: beta
OS Version: OS X 10.13.2
Flash Version: 

Just migrated to chromium FROM Firefox (though I've used Chromium on and off for years, always keeping it as a backup browser on Windows, Linux (Ubuntu) and Apple), thanks to Mozilla's FORCED migration to their new Quantum platform. While that new browser is, indeed, very fast, it diverges from many things people turned to Firefox FOR. And Firefox has never had the best compatibility with web sites and common features in general,
 
Status: WontFix (was: Unconfirmed)
This is not functionality we are going to implement. Extensibility and customizability increase the complexity of the codebase and make it harder to maintain. This is the same reason why not every feature in Chrome has a setting available. The extensions system is deliberately limited to just a few UI surfaces for the same reason, and to prevent abuse.
I can understand - but I could HOPE.
HIDING unused menu entries would be useful as well.
But (sigh) I DO understand. ONE program I wrote many years ago, I had given one final new feature to and in Assembly language of course I could do on the fly code modification. It HAD gotten a bit squirrely, to say the least, using a DSECT to overlay CODE, an idea given to me by someone strongly disparaging the practice by another developer. VERY useful technique for doing things few programmers would ever want to encounter in inherited code! Much more difficult, I think, to reverse engineer from a binary.
The current situation has me longing for a FORK of Firefox 56, I'm afraid - OR a fork of Quantum, WITH expanded API's.

Sign in to add a comment