Environment:
- @forge/react version: 12.1.1 (also checked against latest, 12.1.2 — no changelog entry indicates this was addressed)
- Module: jira:dashboardGadget, render: native
- Components: CommentEditor (edit view) and AdfRenderer (display view)
Issue 1 — Entity double-encoding:
Typing literal characters like & or < into a CommentEditor field and saving produces corrupted output when rendered back through AdfRenderer — e.g. & comes back rendered as >-style double-escaped text instead of the literal character. This appears to happen in the editor’s own ADF serialization/deserialization, since our app passes the field through unmodified (via useForm’s register(), no custom transform).
Steps to reproduce:
- In a gadget edit form using CommentEditor, type a message containing & or < (e.g. “A & B”).
- Save the gadget config.
- View the gadget; the field is rendered via AdfRenderer.
- Observe the character has been corrupted/double-escaped rather than displayed literally.
Issue 2 — Text not selectable in AdfRenderer read view:
Content rendered via AdfRenderer cannot be highlighted/selected with the mouse cursor, preventing users from copying text out of the rendered output. Native text selection works everywhere else in the product; this appears isolated to AdfRenderer’s read-only rendering.
Expected behavior: Special characters round-trip correctly through CommentEditor → storage → AdfRenderer without corruption, and rendered text should be selectable/copyable like any other read-only text content.
Impact: Users can’t reliably enter certain characters in rich-text fields, and can’t copy displayed message text — both are basic, expected text-editing behaviors.