3 ms·
Now someone just has to make this into an extension – firefox extensions are just as easy to make as chrome extensions, so it shouldn’t be an issue.
by kuschku 11y ago
Now someone just has to make this into an extension – firefox extensions are just as easy to make as chrome extensions, so it shouldn’t be an issue.
- insin 11y agoJust tried this out of curiosity and you're right: https://github.com/insin/show-me-the-react https://github.com/insin/show-me-the-react npm install -g jpm git clone git@github.com:insin/show-me-the-react.git cd show-me-the-react jpm run
- Cymen 11y agoNice! I wrote the Chrome version -- I'll link the README to your extension for Firefox.
- insin 11y agoShowing/hiding the button or changing its state for the current tab seems so comparatively painful to do with a Firefox addon (versus Chrome's declarativeContent API) that the fork is no better than using the bookmarklet which does this, at the moment.
- Cymen 11y agoAh! I was wondering how you did that (and what Firefox supported). The Chrome page actions are a little buggy in UX -- when you click the icon, sometimes the URL autocomplete comes down. Maybe it is supposed to and you can put something there programmatically but I don't like it when it drops down. So a fixed icon might not be so bad.