Fix the "Replace activities" placement (Issue #374)#380
Open
tomhavra wants to merge 1 commit intoprojecthamster:developfrom
Open
Fix the "Replace activities" placement (Issue #374)#380tomhavra wants to merge 1 commit intoprojecthamster:developfrom
tomhavra wants to merge 1 commit intoprojecthamster:developfrom
Conversation
tomhavra
changed the title
Contributor
|
This either needs testing on more GNOME shell versions, or the change must be made conditional on shell version. |
Author
|
Good point - I hadn’t considered that (I’m still fairly new to GNOME extension I’ve now tested the fix on GNOME 46, 47, and 48 |
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
3 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.
This pull request fixes the bug described in #374, where the extension failed to work when the "Replace Activities" placement option was selected.
Changes made:
Tested on GNOME 48 (X11 and Wayland) and confirmed that the extension now works without errors.
Fixes #374