forked from nuchi/firefox-quantum-userchromejs
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Fix for v68+
- Loading branch information
Showing
2 changed files
with
2 additions
and
2 deletions.
There are no files selected for viewing
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
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
b1c169d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting, I had the same problem at about the same time...and just wanted to create a PR for the same change...
b1c169d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hg42 Yeah this was actually my fault as previously upstream fixed it for v62+ this way, but I decided to fix it by switching to panelui-menu for some reason. Now its come back to bite me. 😬
b1c169d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no prob, it"s a lot of guesswork with firefox nowadays...
I lived some hours without all my beloved tweaks (e.g. a multiline bookmarks bar with color coding).
Now I know again, how much I need userChrome.
During this time I started to hate mozilla for another restriction. But fortunately, I found a solution on reddit as soon as I had time to search for it.
I am really glad it wasn"t some new mozilla policy.