When choosing iD as the editor, maproulette uses Rapid instead of iD Editor

[theadventurer62]

What happened?

While working on some mapping, I noticed that when iD is chose as the editor, Rapid is used instead; These two editors have different maintainers and features, so iD should be available when chosen.

Steps to reproduce

1. Open a task
2. Choose iD Editor
3. Rapid loads up

Environment

Chrome on macOS

Additional information

No response

[CollinBeczak]

The button you are using to set "edit in ID (web editor)" is intended to open another tab in your browser, and is unrelated to the editor you are seeing. The rapid editor you are seeing is an iframe in Maproulette that displays the rapid editor to allow for editing within the Maproulette window, and at the moment it can only display rapid.

We would appreciate if you have any suggestions on how we can make the interface more user friendly or easier to understand.

[theadventurer62]

The button you are using to set "edit in ID (web editor)" is intended to open another tab in your browser, and is unrelated to the editor you are seeing. The rapid editor you are seeing is an iframe in Maproulette that displays the rapid editor to allow for editing within the Maproulette window, and at the moment it can only display rapid.

We would appreciate if you have any suggestions on how we can make the interface more user friendly or easier to understand.

One idea would be to enable a black screen/redirect screen, which has a link to iD editor if the new tab doesn't load.

[jlewin]

Based on this ticket, it seems fair to conclude that users can misunderstand the effect of the external editor buttons Select Default Editor dropdown, especially when there's Edit functionality in the adjacent panel that is unrelated to this setting and tightly coupled with the Rapid editor. For me, the impact of such a split dropdown makes sense but I can see how it might not.

I'll propose one idea just to add to the discussion of changes that might improve confusion. One simple fix to better convey the scope and limitation of the action might be to add additional terms to the panel and button to clarify that the actions are related to external editing. Changing Select Default Editor to Select Default External Editor might provide slightly more awareness of the scope and effect. Further, adding a header above the editor button to indicate it is for invoking an external tool might do some good as well.

A longer-term fix might be dedicated tabs for View, Edit, and External Edit with persistent selection across tasks such that users who prefer and focus on the external editing pattern, wouldn't see an embedded Rapid editor on load of each task. In such a mode, you'd switch to the external editor tab and see actions for invoking the external tools, possibly resolving the ambiguity about the effect.

[CollinBeczak]

What if i did something like this?

This is what it looked like before for reference.... I guess one down side to this is that the task map widget is basically required now to edit. But who doesn't use it. I honestly don't know.