Maximouse

> Ideally, I would make the context menu an instance of a React context menu so that React can take care of this. Not sure how, though. May just have...

> Note that our extension currently hasn't been Chinese-localized yet, so this may be out of scope until that happens. We do have Chinese translations. @LuYifei2011 Is what you're suggesting...

> Okay, this might be either a missing feature or a bug depending on how you look at it. Or a feature. I think it's nice that blocks of the...

> I don't know if this is usually how moving items works, but it'll do. I think it would be a good idea to compare this implementation with a few...

> Perhaps it would be justified to outright refuse to allow custom reporter blocks to placed inside such positions, but i'm not too sure how easy that would be to...

I'm not sure if this is very useful - profile pages don't have that many rows. But if it's added, it should probably be part of the More items per...

> > I'm not sure if this is very useful - profile pages don't have that many rows. But if it's added, it should probably be part of the More...

I like this, but I'm not sure if it makes sense as a standalone addon - someone who enables it will probably want the blocks to be 2.0-styled as well,...

I think #7988 would be the best option if it generated the mappings from [Scratch's translations](https://github.com/scratchfoundation/scratch-blocks/blob/develop/msg/scratch_msgs.js) instead of hardcoding them. That way, it would support multiple languages but could still...

> > I think [#7988](https://github.com/ScratchAddons/ScratchAddons/pull/7988) would be the best option if it generated the mappings from [Scratch's translations](https://github.com/scratchfoundation/scratch-blocks/blob/develop/msg/scratch_msgs.js) instead of hardcoding them. That way, it would support multiple languages but...