Chris's Wiki :: blog/web/FirefoxQuantumAddons Commentshttps://utcc.utoronto.ca/~cks/space/blog/web/FirefoxQuantumAddons?atomcommentsDWiki2018-04-01T15:14:56ZRecent comments in Chris's Wiki :: blog/web/FirefoxQuantumAddons.By Jukka on /blog/web/FirefoxQuantumAddonstag:CSpace:blog/web/FirefoxQuantumAddons:31c65e5a087d4f5d8caa01fa0652db45da8133a4Jukka<div class="wikitext"><p>Your list looks quite exhaustive, but you're not alone.</p>
<p>I guess maintenance is a problem. And even Firefox moves too fast nowadays.</p>
<p>For these reasons, I have actually put an entry to my coding TODO list: "write your own browser". Not from scratch, of course; WebKit provides a robust base and you can implement a capable browser in Python in less than 10k LOC with PyQt5.</p>
<p>If nothing else, completing the TODO item would be a nice exercise in understanding what is actually going on within browsers.</p>
</div>2018-04-01T15:14:56ZBy Chris Siebenmann on /blog/web/FirefoxQuantumAddonstag:CSpace:blog/web/FirefoxQuantumAddons:3e58e94dda023bcec335acfc141c374ffddc4b87Chris Siebenmann<div class="wikitext"><p>My <code>about:home</code> problem is that <code>about:home</code> itself is currently the
same as <code>about:newtab</code> (what you get for new tabs, which is locked to
a choice of either a blank page or the 'Firefox Home'). My actual home
page is a <code>file:///</code> URL and for good reasons there's no way for addons
to open such URLs. The net result is that Foxy Gestures has no way to
do an 'open new window' that creates the same thing that I'd get with
Ctrl-N. It can't provide the URL directly, and telling Firefox to use
<code>about:home</code> gets the wrong result.</p>
<p>The terrible hack around this is to run a local web server that holds
your home page/new tab page and then have Foxy Gestures or things inject
this URL for new pages and new tabs. The WebExtensions API does let you
use HTTP and HTTPS for at least new windows, and it works fine. I just
hate the idea of having a little web server running just for this (and
having to depend on it).</p>
<p>(Since I was already hacking in new WebExtensions APIs, I added another
one that basically invokes the Ctrl-N 'New Window' Firefox code. This only
works in my own builds, but that's the only place that I really care.)</p>
</div>2018-03-31T19:46:44ZBy Opk on /blog/web/FirefoxQuantumAddonstag:CSpace:blog/web/FirefoxQuantumAddons:8115478a37aa7274d43ec8a337eade3fbf494d5dOpk<div class="wikitext"><p>You don't elaborate on your about:home problems but one of the main things that has kept me on the old 52 ESR release in most places is that the New Tab Override plugin was broken in 57. I use a local file for my bookmarks where the file contains quite a bit of JavaScript that I don't want to lose. Some of the problems stem from the fact that I want this file displayed for new tabs.</p>
<p>There's also New Tab Homepage which solves some problems by pulling the local file into it's storage area but the JavaScript doesn't work. I had to put images inline in the HTML in base64 for them to work.</p>
<p>Where I do have 57, I have to middle-click on the home icon to open new tabs.</p>
</div>2018-03-31T10:16:04ZBy nxadm on /blog/web/FirefoxQuantumAddonstag:CSpace:blog/web/FirefoxQuantumAddons:64f4c05222172d47223d5c921ca5466f6abd00c9nxadm<div class="wikitext"><p>"media.autoplay.enabled"</p>
<p>I actually don't understand why this isn't false by default. Zero issues with it.</p>
<p>Thank you for the list!</p>
</div>2018-03-31T07:59:35Z