Ok, I have seen couple of posts and now I see your frustration. I can give you some other perspective. What you are doing is a really nice user story, but development is an ongoing fight between time and goals. Sometimes and actual patches wait for review for years (not only blender, open source projects in general), keep that in mind when you find some paper cut
Nevertheless what you have here is a kind of easy patch, once you have a design. I bet this can sum up to 8 hours of (junior, advanced junior) developer work if you include review and back and fourht.
If I really wanted to disect bisect and inspect your solutions and bring it closer to design:
add an operator do menu Node on the top: good, no objections. Can we do more:
modifier key when move: ok, fine, it would work like duplicating objeccts in blender, but this is more work, probably new operator is needed, we may remove the old one Remove From Frame
right click context menu: ok, fine but do we show it all the time, and black it yout when you do not have frame selected (wasted space, unused in most situations - bad) or allow for changes in menu layout (changes memory - bad). UI team has strong some guidelines about it
And this is only 30 minutes of thining. That would be 30 minus of developer time out of mentioned 8h.
yes, blender chat is more developer oriented chat, but there are also channels like #support, so not everything is developer oriented.
Module teams use chat to communicate. UI team uses mentioned channel
Thank you for pointing that out. Guess this is a paper-cut then.
I suspect someone thought the full Node menu was a bit tall, so the context menu attempts to be shorter, but as @grzelins suggested, if you open the context menu on a node that’s within a frame, it would make sense to show that option.