Tailor context menus to developer needs

[jurijsk]

In my opinion, context menus are underdeveloped and not used for dev needs.
The biggest offender, in my opinion, is the context menu is in Source bar. Most of the option are not relevant for development or debugging. Most of the actions can be removed (Emoji, Save As..., search, define). I doubt that all text manipulations are needed, since all devs know shortcut for those operations. Others are relevant at the file level and make more sense in File tab in side navigator.

It would be much better to have basic operations similar to ones in VS Code, go to definition, find all references, and things of that nature.

It would also be super handy to have context dependent options for DOM object. Especially "Scroll into view".

In general, it would be good to have context menu unified as much as possible. For example, make "Store as global" and "Scroll into view" available from Source tab context menu, not only from Elements. I've create another issue on the scroll into view subject here.

It feels like context menus are neglected at this point, and they can have great value for productivity during debugging.

Will be happy to hear what you think, and would love to get involved in discussion and brainstorming of this subject.

Cheers

AB#39424738

[captainbrosset]

Thanks so much for the feedback. This is very valuable, and I agree with you that some of the menus are too crowded with not so useful options. The Sources tool menu when text is selected is a great example.

I think this would need a careful review of each and every menu, to decide what can and needs to be changed.

Your idea to add things like "go to definition" and "find all references" is good, but DevTools doesn't do the same kind of project indexing that VS Code does, and so can't offer as much as VS Code. But I'm sure there are some good things that could be added.

Good point about having "scroll into view" and "store as global" available across all tools!

We'll definitely keep this on our backlog and evaluate/prioritize with the other things we're doing. Thanks for your input.

[jurijsk]

Ok, I get it regarding indexing. Frankly it's not that needed, simple 'Find in file' as implemented right now does the thing. Usually I miss VS code's F12 ("Go to definition") the moss - quick way jump to between invocations of the function and it definition. I can do that with F3 then search in open.

[captainbrosset]

Makes sense, thanks for confirming.