Skip to content

fix: use innerHTML instead of textContent in createElement helper#92

Open
simgunz wants to merge 1 commit intoawslabs:devfrom
simgunz:fix/createElement-innerHTML-rendering
Open

fix: use innerHTML instead of textContent in createElement helper#92
simgunz wants to merge 1 commit intoawslabs:devfrom
simgunz:fix/createElement-innerHTML-rendering

Conversation

@simgunz
Copy link

@simgunz simgunz commented Mar 17, 2026

Issue #, if available: N/A

Description of changes:

The createElement utility in main.js names its third parameter innerHTML but assigns it via el.textContent, which escapes HTML. This causes dynamically injected elements (report filter controls, non-match table rows, PDF navigation buttons) to render as raw HTML strings instead of interactive UI components.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Before the fix:
Screenshot_20260317_134132

The createElement helper named its third parameter 'innerHTML' but
assigned it via textContent, causing HTML strings (filter controls,
table rows, PDF navigation) to render as escaped text instead of
being interpreted as HTML.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant