You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
I was previously confused because #135 (comment) "workaround method" meant nothing to me, and #135 (comment) neither a workaround nor a method was described.
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:
I get that with Finitimus, which I certainly added to Firefox (no parsing problem) long ago – I still use the extension.
3.4
86.0.1
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.The text was updated successfully, but these errors were encountered: