fixed missing new line before string error causes#186
Merged
Conversation
hoxyq
approved these changes
Jun 30, 2025
hoxyq
left a comment
There was a problem hiding this comment.
Please add a test that covers this logic.
There are screenshot tests also, but the last time I checked, screenshots are downloaded from some Google's CDN, which requires authorization, so we probably can't add more :(
5dfb164 to
2be5236
Compare
Author
|
I don't see a neat way to test this very UI centric feature. I'd suggest upstreaming it as is. |
hoxyq
approved these changes
Jul 4, 2025
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixing Error Causes of String Type Printed To Console Without New Line
The bug is caused by error type being a "span" to which a "text" "cause" is appended, without appending a new line beforehand.
That "span" actually creates a new line if the last span within it contains more than one element.
To solve it, I wrap all "causes" with divs.
Test plan
For the code:
Before:
Notice the cause in the second line in the first error is appended directly to the stack trace:
After:
Also tested more complicated use cases with ignored frames and such.
Upstreaming plan
devtools-frontendrepo. I've reviewed the contribution guide.