Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
6.8.1
-
None
Description
The commit 80bbaf6fad7376a94bc460eb6e98031bb5266ce1 introduced a QML warning if the "application wide" focus object differs from the "input context" one:
stale focus object 0x302bf2920 , doing manual update
While this leads to correct behavior, it might leak the user input to the log console.
Consider the attached MWE, clicking the buttons gives the following log output (excerpt):
stale focus object 0x302bf3020 , doing manual update Button 6 clicked stale focus object 0x302bf2920 , doing manual update Button 7 clicked Button 7 clicked stale focus object 0x302bf2ca0 , doing manual update
This might give conclusions to what the user entered if access to the console/logfile is given. Is there a "cleaner" way to ensure the correct situation handling as introduced by the commit stated above without having the QML warning? Is there anything "off" in the background of focus handling?
Note: I've marked this to affect Qt 6.8.1 as this is the version I used in the MWE, as the commit is quite old, the issue propably affects all versions starting with Qt 5.9.