[JSFIELD-29] Propagate the readonly flag to the JF field implementation Created: 06/Feb/23 Updated: 06/Feb/23 Resolved: 06/Feb/23 |
|
| Status: | Resolved |
| Project: | Java Script UI (App and Dialog Fields) |
| Component/s: | None |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | 1.2.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Adrien Manzoni | Assignee: | Adrien Manzoni |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Description |
|
Currently the JS field doesn't consider the readonly flag, due to its nature (it's a Iframe). As the JS field implementation is highly customizable, the idea is to propagate the JS field definition readonly flag to the JS field, so the developer can implement the related logic in the JS field. |