Video DownloadHelper on 2019.02.11

Board for discussions around the Basilisk web browser.

Moderator: satrow

User avatar
rex_a
New to the forum
New to the forum
Posts: 2
Joined: 2019-02-15, 05:28

Video DownloadHelper on 2019.02.11

Unread post by rex_a » 2019-02-15, 05:47

I've been running Basilisk a good while and got the notice a day or so back and updated to 2019.02.11

All seemed good.
One of my extensions was Video DownloadHelper. Today I wanted to download a vid file and discovered there was no icon in the toolbar for V DlH. Checked the extensions page and it was listed there, not disabled, and seemed ok. I've been running Video DownloadHelper ver 6.3.3 That worked before and I think should still be ok.

I uninstalled / reinstalled the extension a couple times - no change. So today I uninstalled 6.3.3 and then installed 6.3.1 . Icon is back in toolbar and it seems to be working.

6.3.3 should still be compatible shouldn't it? Any thoughts on why 6.3.1 works and 6.3.3 doesn't?

coffeebreak
Board Warrior
Board Warrior
Posts: 1853
Joined: 2015-09-26, 04:51
Location: U.S.

Re: Video DownloadHelper on 2019.02.11

Unread post by coffeebreak » 2019-02-15, 10:00

rex_a wrote:Any thoughts on why 6.3.1 works and 6.3.3 doesn't?
Video DownloadHelper 6.3.3 is an xul/webextension hybrid, made specifically to be a bridge to migrate the user's settings from xul to webextension versions of VDH. (You can tell by looking inside the xpi with archiving software such as 7-zip.)
Video Download Helper 6.3.3
vdh6.3.3.png
It was likely affected by the removal of support for webextensions.

User avatar
rex_a
New to the forum
New to the forum
Posts: 2
Joined: 2019-02-15, 05:28

Re: Video DownloadHelper on 2019.02.11

Unread post by rex_a » 2019-02-16, 05:29

Ok. I thought video downloadhelper 6.3.3 was the last xul version. Didn't realize it was a hybrid.

I installed 6.3.1 and it seems to be doing all I've wanted.

One suggestion, the Basilisk update checked the extensions. It disabled one other extension but left vdh 6.3.3 running. Not sure what was being checked but maybe there was a way it could have found and disabled vdh 6.3.3 too.

Locked