You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Howdy, since I don't use the url bar in firefox, I tried to move the toolbar button to the addonbar, but it seems the toolbar button is kinda weird, unlike most other plugins which provide a toolbar button, this is placed next to the menu button, and not in the area where the other toolbar buttons are. Also the toolbar button does not show up in browser.uiCustomization.state which would allow me to fiddle with it's position directly.
It would be really nice if your fine plugin would also work for vimperator and pentadactyl users. thanks for your great work!
The text was updated successfully, but these errors were encountered:
Hi. Yes, the toolbar button creation is based on the old way of creating a button (and not using sdk etc). It requires some minor rewrites to get it done properly. As majority of the people stick with the default urlbar option, this wasn't a priority for the project.
Will look into that, please expect some delay.
Compatibility with other extensions - looks like a lot of work, unfortunately.
great! i think there's no issue with compatibility with other plugins, if you implement the button the way it is usually implemented, that is what other plugins also expect.
thanks for your great tool btw!
Howdy, since I don't use the url bar in firefox, I tried to move the toolbar button to the addonbar, but it seems the toolbar button is kinda weird, unlike most other plugins which provide a toolbar button, this is placed next to the menu button, and not in the area where the other toolbar buttons are. Also the toolbar button does not show up in browser.uiCustomization.state which would allow me to fiddle with it's position directly.
It would be really nice if your fine plugin would also work for vimperator and pentadactyl users. thanks for your great work!
The text was updated successfully, but these errors were encountered: