Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No progress beyond 'Parsing' #147

Open
grahamperrin opened this issue Mar 19, 2021 · 2 comments
Open

No progress beyond 'Parsing' #147

grahamperrin opened this issue Mar 19, 2021 · 2 comments

Comments

@grahamperrin
Copy link

grahamperrin commented Mar 19, 2021

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.

#135 (comment) 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

  • Chrome Store Foxified 3.4
  • Firefox 86.0.1
  • FreeBSD 14.0-CURRENT.

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
Copy link

joshieecs commented Mar 20, 2021

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
Copy link
Author

Thanks. Now, your comment makes sense.

I was previously confused because #135 (comment) "workaround method" meant nothing to me, and #135 (comment) neither a workaround nor a method was described.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants