-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge profile UI includes search highlight markup in profile names #1490
Comments
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
(Currently blocked by #1563.) |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
Still happens in 1.6.10. |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
No updates since 1.6.10. |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
Ditto #1490 (comment), still present in 1.6.10. |
Pre-Submit Checklist:
What happened:
<em class="search-result">
tags leak into the profile name fields during a profile merge from a search.What did you expect to happen?:
Names to be free of internal markup.
How did you reproduce it?:
Debug Information:
Version 1.6.5
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
No Module Error
Status: Online
SPN: disabled (module disabled)
Config: 12
Updates: stable (13/33)
Compatibility: WFP State (34)
Goroutine Stack
The text was updated successfully, but these errors were encountered: