Skip to content

[fix](ui) Fix query profile displaying as garbled text with html tags in FE UI#61864

Open
wenzhenghu wants to merge 1 commit intoapache:branch-3.1from
HYDCP:apache-3.1-fe-ui-profile-bug
Open

[fix](ui) Fix query profile displaying as garbled text with html tags in FE UI#61864
wenzhenghu wants to merge 1 commit intoapache:branch-3.1from
HYDCP:apache-3.1-fe-ui-profile-bug

Conversation

@wenzhenghu
Copy link
Copy Markdown
Contributor

@wenzhenghu wenzhenghu commented Mar 30, 2026

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary:
After the frontend UI was updated to use innerText to prevent profile truncation by special characters(https://github.com/apache/doris/pull/58613), the profile page started showing garbled text full of </br> and &nbsp; tags.

This is because the backend API QueryProfileController was forcibly injecting these HTML formatting tags into the plain text data. Since the modern frontend <pre> tag naturally handles line breaks and spaces, we should remove these destructive string replacements from the backend to keep the API data clean.

Release note

Fix the issue where the Query Profile page in the Web UI displays garbled text with HTML tags.

Check List (For Author)

  • Test: Manual test
  • Behavior changed: No
  • Does this need documentation: No

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@wenzhenghu wenzhenghu requested a review from morrySnow as a code owner March 30, 2026 05:38
@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Mar 30, 2026

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@wenzhenghu
Copy link
Copy Markdown
Contributor Author

run buildall

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.

2 participants