Allow Editing of Context Menus
-
Part of me is afraid that this essential feature (element context menu editing) will ended up falling by the wayside. I mean, let's remember the original post asking for users to be able to edit menus is from 2018. We are in 2020, who knows when you're going to be able to remove all the bloat and fix the mess that vivaldi element context menus became? Also, the whole fact that vivaldi's team sort of “rush” this feature, makes me think that adding the context menu customization that everybody wanted is pretty complicated and it's a long way off yet (if it were just some other 3 or 4 months of work away, why not just wait?)
Also, I really think that marketing that vivaldi now allows editing context menus, it's a really poor marketing strategy, cause you're promising something that you're not delivering, which most likely will leave a lot of users frustrated – hence the wave of comments were today talking precisely about that.
-
@ericpa06
please read the thread about the coming mailreader M3 within vivaldi. there a many user who said, share your alpha state of the mailer with us. but M3 is "held back" by @jon , who wants a minimum of security for the existing mails (which is understandable) and a minimum of functionality. so years have passed with nothing to test (for us users)with the context menus I see it similar, only that here already the menus can be adapted for which it is possible and the "difficult menus" can be edited later.
that's why I personally think, it's very good that some of the menus can already be purged now.
and yes, of course I would also like to edit the most frequently used context menu of the website/images, but that will come. and I don't think it will take 2 years again -
this very post is also still marked as "in progress". i don't think that things get left halfway here, they get constantly improved if you've used vivaldi for a while now. you can see how it changed over time and it is a huge damn whole of a lot. also how much time does it take to make a game (vivaldia) from scratch? a lot too but they did it.
which menus are missing? pics, page and links?
-
Was so excited to read context menu customisation was finally in an update... only to realise it didn't include the web link context menu.
As small a feature as it sounds, it's definitely been the one thing stopping me from using vivaldi full time, my muscle memory had become so accustomed over the years to having "open in new background tab" first rather than second on the context menu that I get tripped up by vivaldis standard context priority quite often (of course I know you can ctrl click a link too, but generally only use that for clicking more than one link in quick succession)
Anyway, hoping the feature is not left too much longer, assuming the groundwork to make this happen has pretty much been done with the last update though?
-
@diarx Every context menu (I think there are a total of 11 of them) that relies on web page content is not under the exclusive control of Vivaldi. This is context menu structure that is inherited from Chromium, and MUCH more complex to reconfigure. That said, web page context menues will be customizable. It will simply take more time.
-
this browser already has crazy features and it has no intention to stop, thank you to all the crazy aka ambitious people behind it.
-
totally agree with everything asked in first post - we need customization, re-organization of menus and possibly renaming of items.!
-
@reyn Be patient. This feature request is in progress, and more editable menus have been added in recent builds. More will come in due course, but don't expect it all to be done at once. It is a major task.
-
@Pesala recent builds means post 3.5 release?
-
-
Check out the new menu editing options in Vivaldi 3.7. Web page context menus for links, images and more can now be customized as well.
I think we're getting close to finishing this feature now or can you still find some menus that can't be edited?You can read the full release blog here: https://vivaldi.com/blog/vivaldi-fires-up-performance-2/.
-
-
You mean once again a feature that was available in Firefox legacy (I still use Firefox ESR, supplemented by up--to-date browsers such as better-than-Chrome Vivaldi).
-
One thing to consider is - there should be less things in the context menu by default, and then you can add them back with editable context menus. Or an option for condensed or full context menus.
-
@code3 Not a good route to take. New users would never discover a lot of features if they were not available on the default menus. It is better to include everything except the kitchen sink, and let new users learn how to remove them. After all, if you have never used something you may not even be aware that it is useful.
Blog • Vivaldi Review • Server Status
Win 10 64-bit build 19045.2486 • Snapshot 7.4.3671.3 (64-bit) -
@Pesala Normally I would agree with that, but the context menus are so ginormously large that I think looking to take a few options off, and then “allow full context menus in settings,” could be a good idea.
-
@Pesala @code3 Presto Opera used to have 2 default menu setup, classic & compact. Then we can create more custom setup from those 2 templates.
Currently, compare to presto opera it's a few step backward. But it's a start, hopefully they will consider multiple setup/backup in the future when they are done with all the context menu. Now, it's just very clunky while editing various menu.
-
@dude99 said in Allow Editing of Context Menus:
Presto Opera used to have 2 default menu setup, classic & compact. Then we can create more custom setup from those 2 templates.
I never used that, but that’s exactly what I’m suggesting, and maybe consider compact as default because the menus are getting too long.
Another thing to consider is having a right click bring up compact context menu and a double right click bringing up the classic menu.
-
@code3 Actually, you can only pick one menu setup at a time in presto. But it have a "bug" or "hidden feature" (I don't remember how it works) that allow user to split context menu into 2 columns, so that oversize context menu can become not too "tall".
Example: linked images context menu will have both link & image commands that fill the entire height of the screen. But I can split 'em into link commands on the left column & image commands on the right column. No need for submenu (to hide the image commands), & I can access everything in plain view.
-
@dude99 said in Allow Editing of Context Menus:
But it have a "bug" or "hidden feature" (I don't remember how it works) that allow user to split context menu into 2 columns, so that oversize context menu can become not too "tall".
Break Item?
Used that for SpellChecker.
Would be nice to recover it.
