search

Noitidart / Chrome-Store-Foxified

Point and click to install extensions into your browser from the AMO, Chrome Web Store, Microsoft Store, or Opera Addons websites.
https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/?src=github
Mozilla Public License 2.0
363 stars 54 forks source link

No progress beyond 'Parsing' #147

Open grahamperrin opened 3 years ago

grahamperrin commented 3 years ago

A few weeks or months ago, I noticed the extension maybe not working as expected, however I was (over-adventurously) attempting to work with extensions for Chromium-based browsers that, if I understand correctly, rely upon a speech recognition API that's simply not in Firefox. So I took little notice of the problem.

https://github.com/Noitidart/Chrome-Store-Foxified/issues/135#issuecomment-801350850 yesterday @s3hMC wrote:

… stuck on parsing. …

I get that with Finitimus, which I certainly added to Firefox (no parsing problem) long ago – I still use the extension.

image

Memory has been cleared, I have disabled then re-enabled the extension, and Firefox has been restarted. No improvement.

98 was fixed in 2017.

I wonder whether the symptom now is due to incompatibility with recent releases of Firefox.

joshieecs commented 3 years ago

It is due to changes on the Chrome Web Store. It is not parsing the extension in this step, it is parsing the Chrome Web Store page to extract a URL to directly download the .crx file for that extension.

The workaround is to manually download the .crx and use the option on the right under "My Computer" to select the .crx file from the local disk. See my detailed comment for more info.

grahamperrin commented 3 years ago

Thanks. Now, your comment makes sense.

I was previously confused because https://github.com/Noitidart/Chrome-Store-Foxified/issues/135#partial-discussion-header "workaround method" meant nothing to me, and https://github.com/Noitidart/Chrome-Store-Foxified/issues/135#issue-508060658 neither a workaround nor a method was described.