Page 1 of 2

Basilisk update 2019.02.11

Posted: 2019-02-11, 13:23
by Moonchild
Basilisk has been updated to v2019.02.11

http://www.basilisk-browser.org/releasenotes.shtml

This is a development and security release.
  • Removed experimental WebExtension support from the browser.
    Please check your add-ons; you may need to find alternatives for extensions that are no longer supported.
    For background to this change, please see the related forum announcement in this board.
  • Removed more telemetry code from the platform.
  • Finalized spec compliance of the IntersectionObserver API, and enabled it by default.
    Related this, also fixed a number of browser crashes.
  • Switched to the new ffmpeg decode API to avoid dropping of frames.
  • Removed Mozilla-proprietary AudioContext constructor, improving spec compliance of WebAudio.
  • Aligned Element.ScrollIntoView() with the spec.
  • Fixed a buffering issue in the WebP decoder that caused intermittent browser crashes.
  • Changed the Add-on Manager to the same one used by Pale Moon, unifying add-on handling.
    Note: Some extensions that modify/style the Add-on Manager will have to be updated to work with Basilisk 2019 versions as a result.
  • Improved resource-efficiency for internal stopwatch timers.
  • Improved handling of incorrectly-encoded CTTS in media files, resolving some playback issues of videos.
  • Updated SQLite lib to 3.26.
  • Improved the Cycle Collector and Garbage Collector.
  • Set the Incremental Garbage Collection time slice to 20 ms for more efficient JavaScript memory handling (regression fix).
  • Improved fullscreen navigation bar handling in the situation it has focus when switching to full screen.
  • Aligned instanceof with the final ES6 spec.
  • Fixed a potential use-after-free in IndexedDB code. (DiD)
  • Improved proxy handling to avoid localhost getting proxied. (CVE-2018-18506)
  • Fixed several potentially-exploitable memory safety hazards and crashes. (DiD)
  • Improved Windows DIB clipboard data handling.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 13:37
by Al6bus

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 14:38
by Nick2018
I WANT MY EXTENSIONS BACK!!!! I AM NOT HAPPY!!!!! :sick: :evil: WHY NO WARNING BEFORE THE UPDATE THAT YOU WOULD LOOSE EXTENSIONS!?!?!?! I WAS ABLE TO KEEP MOST OF MY EXTENSION BUT U-BLOCK ORIGIN IS GONE AND JAVA SCRIPT IS GONE WITH NO WARNING!!!! I WOULD NOT HAVE UPDATED IF I AT LEAST HAD A WARNING!!!! AND IF I HAD LOST ALL OF THE OTHERS I WOULD HAVE NEVER BEEN ABLE TO FIND THEM AGAIN!!!! I TRIED THE NEW FIREFOX AND HATED IT!!!! I AM LEFT WITH EITHER PALE MOON OR BASILISK BUT EXTENSIONS HAVE DISAPPEARED AND I CAN'T FIND THEM TO EVER RE-INSTALL AGAIN.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 15:04
by kelendral
Nick2018 wrote:I WANT MY EXTENSIONS BACK!!!! I AM NOT HAPPY!!!!! :sick: :evil: WHY NO WARNING BEFORE THE UPDATE THAT YOU WOULD LOOSE EXTENSIONS!?!?!?! I WAS ABLE TO KEEP MOST OF MY EXTENSION BUT U-BLOCK ORIGIN IS GONE AND JAVA SCRIPT IS GONE WITH NO WARNING!!!! I WOULD NOT HAVE UPDATED IF I AT LEAST HAD A WARNING!!!! AND IF I HAD LOST ALL OF THE OTHERS I WOULD HAVE NEVER BEEN ABLE TO FIND THEM AGAIN!!!! I TRIED THE NEW FIREFOX AND HATED IT!!!! I AM LEFT WITH EITHER PALE MOON OR BASILISK BUT EXTENSIONS HAVE DISAPPEARED AND I CAN'T FIND THEM TO EVER RE-INSTALL AGAIN.
Chill.
Download Classic Add-ons Archive
Find XUL version of addon.
Install and be happy.

That or if you've kept your installs nearly identical, you should be able to just grab the addon from your Pale Moon install.

-
My own issue.
It seems that the changes are incompatible with the settings used with Classic Theme Restorer and the changes to the addon page have no left my profile broken since all addons show as disabled and no way to change state. Neither the enable nor disable button do anything.
Classic Theme Restorer: Options: Add-on Manager: Show Add-on version : UNCHECK
Resolved the issue.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 15:26
by Isengrim
Nick2018 wrote:WHY NO WARNING BEFORE THE UPDATE THAT YOU WOULD LOOSE EXTENSIONS!?!?!?! I WAS ABLE TO KEEP MOST OF MY EXTENSION BUT U-BLOCK ORIGIN IS GONE AND JAVA SCRIPT IS GONE WITH NO WARNING!!!! I WOULD NOT HAVE UPDATED IF I AT LEAST HAD A WARNING!!!!
If any of these extensions were Web Extensions, that is why they are gone. There was plenty of warning about that beforehand.

If your extensions were actual XUL extensions... I'm not sure why those would have been removed, but you should be able to find them again in the repositories kelendral mentioned. You can find the "legacy" version of uBlock Origin on gorhill's GitHub repository.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 15:38
by JustOff
kelendral wrote:It seems that the changes are incompatible with the settings used with Classic Theme Restorer and the changes to the addon page have no left my profile broken since all addons show as disabled and no way to change state. Neither the enable nor disable button do anything.
Classic Theme Restorer: Options: Add-on Manager: Show Add-on version : UNCHECK
Resolved the issue.
Or just update CTR, as this was already addressed in v1.7.8.2019.01.21.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 16:03
by TransmitHim
Isengrim wrote:
Nick2018 wrote:WHY NO WARNING BEFORE THE UPDATE THAT YOU WOULD LOOSE EXTENSIONS!?!?!?! I WAS ABLE TO KEEP MOST OF MY EXTENSION BUT U-BLOCK ORIGIN IS GONE AND JAVA SCRIPT IS GONE WITH NO WARNING!!!! I WOULD NOT HAVE UPDATED IF I AT LEAST HAD A WARNING!!!!
If any of these extensions were Web Extensions, that is why they are gone. There was plenty of warning about that beforehand.

If your extensions were actual XUL extensions... I'm not sure why those would have been removed, but you should be able to find them again in the repositories kelendral mentioned. You can find the "legacy" version of uBlock Origin on gorhill's GitHub repository.
I think Nick's point is that the browser gives no warning, upon running the update that this will be an issue. Not every one who uses a browser keeps up with the development forum for it (i've only come here and registered now because of this issue).

This update has wiped out about 2/3 of my extensions, many of which I consider to be an essential part of a functional web browser. I only started using Basilisk because I didn't like the changes Mozilla made to Firefox with Quantum and didn't want to have to dick around with custom CSS files to keep it how I wanted. Now I find Basilisk forcing me to dick around with GitHub to keep extensions I like working.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 17:19
by ron_1
TransmitHim wrote:
I think Nick's point is that the browser gives no warning, upon running the update that this will be an issue. Not every one who uses a browser keeps up with the development forum for it
How about the home page of the browser? It's in the release notes. If changes like this bothers somebody, it might be a good idea to start reading the release notes before installing.

Here's the link for uBo that works on Basilisk (and PM): https://github.com/gorhill/uBlock/releases/tag/firefox-legacy-1.16.4.8
Tell us what extensions don't work, many people here would be happy to help.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 17:53
by Nick2018
Thank you to all of you for helping out. I may have seen the warning but I did not understand fully what was going to happen. I found u-block origin on github but I am still searching for a toggle switch for java script on-off and an older version of ForecatFox(Fix). If anyone knows how I could get these and get them for other people it would be greatly appreciated. Or can I go back to an older version of Basilisk and still be able to find these?

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 18:12
by ron_1
ForecatFox(Fix): http://legacycollector.org/firefox-addons/583250/index.html

I'd suggest: a) bookmarking the above website & b) saving the .xpi file to your hard disk to avoid this problem in the future.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 20:15
by Moonchild
Al6bus wrote:
no new release notes :coffee:
Or you could understand that a website update might take some time to be globally visible.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 20:18
by Moonraker
Moderator note: DO NOT quote entire previous posts, please.

I have a problem with this archive because i cannot see the contents of this archive and i do not wish to download 35mb of data just for 1 or 2 extensions..is there any old full themes in there?..this is an issue and i think a full catalogue should be provided beforehand.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 20:19
by Moonchild
Nick2018 wrote:I WANT MY EXTENSIONS BACK!!!! I AM NOT HAPPY!!!!! :sick: :evil:
And I want a sprinkle donut and some coffee. Oh, and throw in a slice of mudcake!
WHY NO WARNING BEFORE THE UPDATE THAT YOU WOULD LOOSE EXTENSIONS!?!?!?!
https://forum.palemoon.org/viewtopic.php?f=61&t=21298 Date Jan 21st 2019.
This information was also echoed on a few popular tech blogs.

Re: Basilisk update 2019.02.11

Posted: 2019-02-11, 21:55
by New Tobin Paradigm
Anyone with half a brain could figure out this was going to be the end result eventually. Albeit not for the reasons the mozis (not a typo) outside this forum would falsely claim.

Dozens and dozens of posts about WebExtension technology here and Mozilla's continued destruction paving the way for more and more regressive technology.

As well as the most damning of all, relying on experimental support for a feature of a perpetually beta quality software product on a rolling release.

Tisk tisk. Perhaps you should have considered that in your add-on selection process. Hmm?

Re: Basilisk update 2019.02.11

Posted: 2019-02-12, 01:40
by abelenki
thanks for the update!

only two extensions stopped working for me in 2019.02.11:

Adblock Plus
anonymoX

by following the site, suggested in this thread:

http://legacycollector.org/firefox-addons/

i just downgraded to Adblock Plus 2.8 and anonymoX 2.5.3.1, and they started to work again. so far, no problems at all.

Re: Basilisk update 2019.02.11

Posted: 2019-02-12, 03:20
by us66mo
Thanks for the update!

All of my extensions (I only use 7 of them) work fine, but when I go to the "Extensions" part of the "Add-ons" tab, they are all listed by name with (disabled) after the extension name, although they are all working. Or is this the expected behaviour?

Thanks!

Re: Basilisk update 2019.02.11

Posted: 2019-02-12, 09:41
by spencer1
us66mo wrote:Thanks for the update!

All of my extensions (I only use 7 of them) work fine, but when I go to the "Extensions" part of the "Add-ons" tab, they are all listed by name with (disabled) after the extension name, although they are all working. Or is this the expected behaviour?

Thanks!
I had that same problem. Do you have the CTR extension? If so, open it up and click "Add-on manager" on the left-side menu. Then play around with those settings until things get back in line. Here's a screen shot of my CTR after I got the add-on page back to the way it was before the update: https://i.imgur.com/OmRXoBg.jpg

Re: Basilisk update 2019.02.11

Posted: 2019-02-12, 09:52
by Moonchild
Aris has created an update of CTR to solve addon-manager issues with Basilisk 2019 versions.
See https://github.com/Aris-t2/ClassicTheme ... r/releases

Re: Basilisk update 2019.02.11

Posted: 2019-02-12, 16:29
by Terryphi
Baslisk update 2019.02.11 has disabled British English Dictionary. This is a consequence of dropping webextension support. Does anyone know the location of a compatible UXL version?

Re: Basilisk update 2019.02.11

Posted: 2019-02-12, 16:35
by yami_