FIX(client): resolve list tags, etc. polluting log#5619
Merged
Krzmbrzl merged 1 commit intomumble-voip:masterfrom Apr 9, 2022
Merged
FIX(client): resolve list tags, etc. polluting log#5619Krzmbrzl merged 1 commit intomumble-voip:masterfrom
Krzmbrzl merged 1 commit intomumble-voip:masterfrom
Conversation
As reported in mumble-voip#4491, mumble-voip#4986 and mumble-voip#5430, since the changes to the chat in the 1.4.x release, some tags would "pollute" the rest of the log, i.e. cause future log entries to be contained within them. The source of the issue seems to be that the `insertBlock` method of `QTextCursor` appears to correspond to the `<p>` HTML tag. The `<p>` tag may only contain inline elements, but `QTextEdit` will not fail outright when inserting block-level elements and will instead attempt to correct the invalid input which results in the behaviour reported in the above issues (as far as I can tell). My proposed solution is to use the `insertFrame` method for all messages. Fixes mumble-voip#4491
Member
|
Ah great! This bug was getting annoying 👀 |
Member
|
Thank you very much for fixing this ❤️ |
Member
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 22, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved. Added minimum icon size for channel status icons which now scale since PR mumble-voip#5772 Initially, icons were too small at 100% scale.
1 task
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 22, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved. Added minimum icon size for channel status icons which now scale since PR mumble-voip#5772 Initially, icons were too small at 100% scale.
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 22, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved. Added minimum icon size for channel status icons which now scale since PR mumble-voip#5772 Initially, icons were too small at 100% scale.
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 22, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved.
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 22, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved.
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 25, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved.
dexgs
added a commit
to dexgs/mumble
that referenced
this pull request
Aug 25, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved. Fixes mumble-voip#5818
Krzmbrzl
added a commit
that referenced
this pull request
Aug 27, 2022
Hartmnt
pushed a commit
to Hartmnt/mumble
that referenced
this pull request
Sep 1, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved. Fixes mumble-voip#5818
Krzmbrzl
pushed a commit
to Krzmbrzl/mumble
that referenced
this pull request
Sep 8, 2022
Fixed chat log scaling issue introduced by PR mumble-voip#5619 (my fault, whoops) The bug fixed by that commit is still fixed after this PR, but the regression introduced has been resolved. Fixes mumble-voip#5818 (cherry picked from commit ece450a)
Member
|
It seems like these changes may have caused a regression in selection behavior: #6045 (comment) |
Contributor
Author
Member
|
Yes they are - this also wasn't a call to action from me to you but rather a note for future visitors. I just stumbled upon this during bisecting the linked issue and this might become relevant again once we try to fix the current bug :) |
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.
As reported in #4491, #4986 and #5430, since the changes to the chat in
the 1.4.x release, some tags would "pollute" the rest of the log, i.e.
cause future log entries to be contained within them.
The source of the issue seems to be that the
insertBlockmethod ofQTextCursorappears to correspond to the<p>HTML tag. The<p>tagmay only contain inline elements, but
QTextEditwill not fail outrightwhen inserting block-level elements and will instead attempt to correct
the invalid input which results in the behaviour reported in the above
issues (as far as I can tell).
My proposed solution is to use the
insertFramemethod for allmessages.
Fixes #4491
Checks