Skip to content

## Bug: Image paths with parentheses still not rendering correctly after PR #635 #636

@T941

Description

@T941

Describe the bug
PR #635 ("fix/image-paths-with-parens") was merged to address image filenames containing parentheses (e.g. /files/abcd (1).jpg), but the fix does not appear to be working as expected. Images with parentheses in their filenames are still not rendering correctly in the editor.

Steps to reproduce

  1. Open any Wiki page and create or edit a Change Request draft
  2. Insert an image whose filename contains parentheses, e.g. abcd (1).jpg or 1234 (1).png
  3. The image reference appears in the editor as raw markdown: ![](/files/abcd (1).jpg) and ![](/files/1234 (1).png)
  4. The images are not rendered — they remain as broken/unresolved references

Expected behavior
Images with parentheses in their filenames should render correctly in the editor after PR #635 was merged.

Actual behavior
The images still fail to render. The markdown tokens with parenthesized filenames appear unresolved in the Change Request draft view.

Environment

Additional context
The fix in PR #635 updated the imagePattern regex in frontend/src/components/tiptap-extensions/image-extension.js to support one level of balanced parentheses in URLs. However, based on testing with filenames like abcd (1).jpg and 1234 (1).png, the pattern does not yet handle these cases correctly in practice.

Screenshots attached.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions