Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Basilisk location bar ceases to function after installing CTR #193
Downloaded Basilisk this morning with the intention to test it thoroughly, but after installing Classic Theme Restorer and importing a backup of my settings created in FF ESR 52.5 the location bar ceases to function. Typed URLs won't load and about:config cannot be accessed either. I even had to copy the verification URL for my email address after registering this morning into Firefox in order to complete the registration since Basilisk wouldn't load the page.
Disabling CTR allows normal use.
As is often the case, the truth lies somewhere in the middle
Yes, CTR was created and intended for Australis plagued Firefox versions (>=29.0a1); versions <=44.0 are supported by CTR v1.5.4beta9 (in the beta channel), but even recent (release/beta) CTR versions do still cater for Fx versions 45.0 - 56.0; to be able to do that (and differentiate between 11 major Fx versions) CTR relies heavily on the reported app version (so as to apply the appropriate set of CSS files...).
It would appear that Basilisk manifests itself to CTR as Fx 55.0 version, so CTR tries to apply to the Basilisk GUI CSS code written and meant for Mozilla Firefox 55.0; and that's where the breakage occurs
If we're talking about complete profiles here, then, given that current Basilisk incarnation is a mix of Fx 51+52+53 code, I suspect many incompatibilities to be present between it and Fx ESR 52 (now at v52.5.0) but nothing fatal that would prevent the imported profile from running in Basilisk; an (experienced) user should be able to fix various broken things easily (via resetting prefs in about:config, downgrading extensions versions etc.). But it's not recommended to migrate complete profiles from Firefox (especially Fx >=53.0) into Basilisk; start from scratch, i.e. a clean profile, then selectively transfer bits from the Fx profile (mainly bookmarks & logins).
However, @Telmesomething wasn't talking about importing the full Fx 52.5.0 profile into Basilisk:
The way I saw it he was referring to a native CTR feature, which is to export its many settings (the extension's, not the browser's) into a local file (.txt | .json), which can then be imported back into a second CTR installation (in the same or different supported browser), thus replicating the initial CTR setup in the second installation...
Yes, that's correct. It was only the CTR settings which I'd imported, not my FF ESR profile.
However, I'm pleased to report that the CTR 22.214.171.124 beta1 update has fixed the problem and I can now run Basilisk with CTR enabled.
I'll install the other extensions I regularly use in Firefox and will update this thread if I come across any more issues concerning extensions.
Thanks for your help guys.
@Aris-t2 We probably don't need to change the urlbar binding code for anything (do you know why Mozilla changed this, to begin with, making it incompatible?) because our fork's front-end won't get the rust/servo treatment, nor need any of the prep work Mozilla has done for it.
Mozilla changed urlbar code multiple times mostly to include new data collection methods and "suggestion" entries, nothing users really required.
I was asking, because Basilisk shows itself as Firefox 55 and some CTR options use different code for every Firefox version.
Good to hear you won't add new/modified bindings. The current code can stay then. I will will push a new CTR build to release soon.
@Aris-t2 Ugh, yeah, more of those search partnerships, no doubt. No, no additional data collection or suggestion "features" are planned, at all. You should be good to push out to release, special-casing Basilisk as you have.
Just a quick update after successfully installing 21 extensions today of which only one of them won't play ball. That's Video DownloadHelper https://addons.mozilla.org/en-US/firefox/addon/video-downloadhelper/ for which there's no toolbar button to be seen anywhere. I tried uninstalling/reinstalling it again by dragging the XPI file from FF 52.5 ESR into Basilisk, but that didn't help either.
I ran a search of their support forums and found a suggestion which dates from September 2016 which was to delete \ "action-button--b9db16a4-6edc-47ec-a1f4-b86292ed211d-vdh-tbbutton\ " and "browser.uiCustomization.state" from the Basilisk prefs.js but it didn't help. In fact it only served to remove all my precious CTR settings. Fortunately I'd taken the precaution of creating a copy of the prefs.js and was able to undo the damage. I tried it with just deleting the first pref, but it didn't change anything.
I'm pleased to say though that Basilisk is a lot faster than FF 52.5 ESR and videos on the BBC News site snap open immediately. On FF ESR I have to wait about 10 seconds for the throbber to disappear before any videos can be viewed.
One observation if I may and that's with popups. My banking site uses them and although Basilisk displays the option to "Allow", there's no permanent way which can be configured from within that step such as the option to "Always allow popups from this site" which Firefox has. One has to manually add an exception to the popup blocker in the about:preferences#content menu.
If you guys need any help with testing, drop me a line.