-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
browsersetting bug fixes #11042
Merged
Rash419
merged 5 commits into
CollaboraOnline:master
from
Rash419:preset-browser-setting-bug-fix
Feb 4, 2025
Merged
browsersetting bug fixes #11042
Rash419
merged 5 commits into
CollaboraOnline:master
from
Rash419:preset-browser-setting-bug-fix
Feb 4, 2025
Conversation
This file contains 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
caolanm
approved these changes
Jan 29, 2025
Rash419
changed the title
ui: when using browsersetting return default value if key is not present
browsersetting bug fixes
Jan 30, 2025
I think cypress tests are failing due to my patch. I need to investigate |
Rash419
force-pushed
the
preset-browser-setting-bug-fix
branch
2 times, most recently
from
February 3, 2025 07:13
20b7f7f
to
5acb5c8
Compare
only one cypress test
|
- this fixes a weird bug where sometimes there is darkBackground in light theme Signed-off-by: Rashesh <[email protected]> Change-Id: I9587e7b717bd65d1ff1360b9f1b43ac12133af3f
- The menubar and top toolbar need to be reinitialized if `useBrowserSetting` is enabled. Initially, `initializeBasicUI` is called before the browsersetting are received, meaning we can't determine if `compactMode` is enabled. - To address this, we perform another check before `doclayerinit` and add the necessary UI controls if the conditions are met. Signed-off-by: Rashesh <[email protected]> Change-Id: I8d53486200fdfd49501e821334b56bc1f5b9a93d
- needed because client doesn't know about the `accessibilityState` preference when sending load url message Signed-off-by: Rashesh <[email protected]> Change-Id: I965b255bebe83d3c943842559742e6d8bcef56e8
Rash419
force-pushed
the
preset-browser-setting-bug-fix
branch
from
February 4, 2025 16:44
5acb5c8
to
e495a2a
Compare
caolanm
approved these changes
Feb 4, 2025
Rash419
force-pushed
the
preset-browser-setting-bug-fix
branch
from
February 4, 2025 20:11
e495a2a
to
b33d83a
Compare
Fixes an issue where _onRefresh in Control.Menubar.js throws a null exception because the updatepermission event listener was not removed when removeClassicUI was called. Issue: 1. The client initializes basicUI, but at this stage, the browsersetting message has not been received yet. 2. Since useBrowserSetting is false, it may fallback to localStorage, which could have "compactMode=true", leading to the initialization of the menubar. 3. Later, when the browsersetting JSON is received, it determines the final UI mode. If notebookbar mode is preferred, the menubar and top toolbar are removed. 4. However, while removing events, the updatepermission event was not detached. As a result, when updatepermission fired, _onRefresh was still called on a now-null _map, causing an exception. Fix: - Ensure that the updatepermission event listener is properly removed when removeClassicModeUI is executed. Signed-off-by: Rashesh <[email protected]> Change-Id: Ic5dc86c6b5350670e586966226ba722135a55b0d
- when `browsersetting` is enabled we don't store compactMode preference to localStorage Signed-off-by: Rashesh <[email protected]> Change-Id: Ie5bb5be7abf923b7530d854a8489f5f5c97858c3
Rash419
force-pushed
the
preset-browser-setting-bug-fix
branch
from
February 4, 2025 20:39
b33d83a
to
7077448
Compare
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.
No description provided.