Problem
When using an app, it is currently not predictable whether displayed text can be selected and copied. Similar-looking widgets behave differently, creating an inconsistent user experience.
| Widget | Enabled State | Selectable | Copyable |
|---|---|---|---|
| ----------------------------- | ---------------------- | ---------------- | --------------- |
| Multiline Text Input | Enabled | ||
| Multiline Text Input | Disabled | ||
| ----------------------------- | ---------------------- | ---------------- | --------------- |
| Single Line Text Input | Enabled | ||
| Single Line Text Input | Disabled | ||
| ----------------------------- | ---------------------- | ---------------- | --------------- |
| Table Record | N/A | ||
| Variable | N/A |
Impact
Users often need to copy values such as IDs, serial numbers, order numbers, URLs and system-generated text. The current behavior forces app builders to use workaround widgets solely to make text copyable.
Additionally, users cannot easily tell in advance whether content can be selected and copied, which leads to frustration and unnecessary trial-and-error.
Suggested Improvement
Implement a consistent text interaction model across all widgets that display textual content:
- Any visible text-values should be selectable unless a specific security setting disables it.
- Any selectable text should also be copyable.
- Disabled or read-only states should not prevent users from copying displayed information.
- Variables should support text selection and copying in the same way as Table Records and Text Inputs.
Expected Benefits
- More intuitive and predictable user experience.
- Reduced need for app-builder workarounds.
- Faster data transfer between applications.
- Improved usability for operational and shop-floor workflows where copying identifiers and reference values is common.
- Consistent behavior across all text-displaying widgets.
Example Principle
If a user can see text (values not labels), they should generally be able to select and copy it, regardless of which widget is used to display it. Exceptions should be explicit and configurable rather than widget-dependent.