Flexible Layouts don't allow text selection, but must

[charlesh88]

Summary

In Browse mode, object views placed in a Flexible Layout treat all click-drag actions - like when the user is trying to select and copy text - as if the user is editing the layout and dragging an object frame to move it. Instead, this behavior should be confined solely to Edit mode; while in Browse mode the user must be able to click and select text like telemetry values. Display Layouts currently operate this way; Flex Layouts must do the same.

Steps to Reproduce

1. Add a LAD Table or imagery view into a Flexible Layout. Save and exit to Browse mode.
2. Click and drag to select a text element in the layout, observe: a drag proxy for the object view is instantiated and the layout acts as if a drag action is occurring and displays blue drop targets. In fact, that proxy can be dropped onto a drop target in the layout and it will be put into Edit mode.

Environment

• Open MCT Version: release/2.0.5
• Deployment Type: local
• OS:
• Browser:

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

[khalidadil]

Testing instructions can be found in original issue description. I was seeing this behavior with any 2 objects in a flexible layout. Let me know if any clarification is needed!

[ozyx]

Verified Testathon 9/15/22:

Was able to select text on a LAD table embedded in a Flexible Layout

[charlesh88]

Verified fixed Testathon 9/15/22 - WHOOOO!!! This is awesome.