fix(@desktop/browser): Fix further missing look and feel for browsers #19451
Conversation
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
Member
Jenkins BuildsClick to see older builds (31)
|
Khushboo-dev-cpp
force-pushed
the
fix/browserIncognito
branch
from
70761c7 to
aee5223
Compare
micieslak
changed the title
Khushboo-dev-cpp
force-pushed
the
fix/browserIncognito
branch
from
aee5223 to
434ad3a
Compare
Khushboo-dev-cpp
requested review from
a team,
alexjba,
caybro,
micieslak and
noeliaSD
as code owners
Khushboo-dev-cpp
requested review from
friofry
and removed request for
a team
Khushboo-dev-cpp
force-pushed
the
fix/browserIncognito
branch
from
434ad3a to
9db039e
Compare
dlipicar
approved these changes
Dec 2, 2025
Khushboo-dev-cpp
force-pushed
the
fix/browserIncognito
branch
from
9db039e to
043c0de
Compare
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
incognito mode.
What does the PR do
Affected areas
Architecture compliance
My PR is consistent with this document: QML Architecture Guidelines
Screencapture of the functionality
Screen.Recording.2025-12-02.at.17.10.51.mov
Impact on end user
How to test
Risk