Skip to content

Comments

Backport "FIX(client): resolve list tags, etc. polluting log" to 1.4.x#5621

Merged
Krzmbrzl merged 1 commit intomumble-voip:1.4.xfrom
Krzmbrzl:backport/1.4.x/pr-5619
Apr 9, 2022
Merged

Backport "FIX(client): resolve list tags, etc. polluting log" to 1.4.x#5621
Krzmbrzl merged 1 commit intomumble-voip:1.4.xfrom
Krzmbrzl:backport/1.4.x/pr-5619

Conversation

@Krzmbrzl
Copy link
Member

@Krzmbrzl Krzmbrzl commented Apr 9, 2022

Backport

This will backport the following commits from master to 1.4.x:

Questions ?

Please refer to the Backport tool documentation

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

(cherry picked from commit ae097d6)
@Krzmbrzl Krzmbrzl merged commit 3960373 into mumble-voip:1.4.x Apr 9, 2022
@Krzmbrzl Krzmbrzl deleted the backport/1.4.x/pr-5619 branch November 9, 2022 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants