Hacker Newsnew | past | comments | ask | show | jobs | submit | moho's commentslogin

The author got banned from github and gitlab after DMCA takedowns. The code used to be available in those, but I guess he got tired of starting over?

Anyway, extensions are just signed zip files. You can extract them and view the source. BPC sources are not compressed or obfuscated. The extension is evaluated and signed by Mozilla (otherwise it wouldn't install in release-channel Firefox), if you put any stock in that.


In case the author happens to read these - final statement in native CSS nesting is no longer true.

"The only small difference from Sass: for element selectors you need the & prefix. In Sass you could write a { color: red } inside a parent, but native CSS requires & a { color: red }."

It was true for a bit, but fixed within 2-3 releases iirc. You can now freely nav { a { color: red; } }



While you're there flip general.aboutConfig.enabled to true so you won't have to use the silly config.xhtml URL again.


Alternatively, you can download Firefox Nightly instead of regular.

"about:config" just works in Nightly. No fuss.

You can sideload extensions in Nightly, too, after you activate the developer options. I don't think they've added that to regular, as yet? At least not with as much flexibility.

Anyway, I'm gonna try this mobile desktop mode thing and see how it goes. Thank you to everyone!


Installing extensions from file is available on the release build as well, after enabling dev options.

I think the only difference is nightly allows installing unsigned extensions, which I don't personally have a need for (as getting a personal/non-published extension signed is very easy).


That setting unfortunately resets after restarting the browser. But the width setting stays.


What a great thread!

Thank you and previous poster for sharing how to get that working.


As did Thailand


uBO never had the ability to do CNAME decloaking in Chrome though, the required API (browser.dns/chrome.dns) wasn't there even in MV2. It was always a Gecko-only feature (and a big one!). IIRC Brave rolled its own CNAME decloaking mechanism in its Shields blocker, without exposing a chrome.dns API.


Mull has been officially discontinued by DivestOS back in December, along with most of their other projects. A fork by the name IronFox emerged but it's too new to know whether it's a real contender.


You can access about:config on mobile FF (all versions, including release channel) at this very intuitive URL: chrome://geckoview/content/config.xhtml


Super useful, thanks.

In my case ctrl+shift+j opens a dumb console that only shows messages and doesn't take any input. I had to go to about:addons, hit F12 for the Dev Tools and paste it in the console there. Worked well.


If you go to about:config and set "devtools.chrome.enabled" to true, the cmd-shift-j thing should work


I also have to do this to make it work on Win10 firefox console (F12)


If some addons DISAPPEARED then you have to restart Firefox, go to addon manager menu, find disappeared addons and disable/enable them.

When I say "disappeared" I mean that addon icon or else is disappeared.


This is the step required for me to allow Browser Console for input


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: