@SomeCallMeChris, I'm hoping that it's just -how- things are done, but I'm not certain. As long as they don't drop support for the existing APIs there won't likely won't be huge changes needed for Rikaisama. If however in the future they force developers to exclusively use their new dumbed-down Chrome-like WebExtensions API, then some features such as EPWING support may not be possible. If this turns out to be the case, I would likely support the older API.

@toshiromiballza, I've tested Rikaisama 22.9 using the Firefox Nightly build (the future Firefox 46) and it seems to work OK. Mozilla's original plan was to disable XUL/XPCOM support 12-18 months after their The Future of Developing Firefox Add-ons blog post on 21-August-2015, but they may push that back. Other disturbing plans include dropping support for heavyweight themes such as my favorite FT DeepDark.

(2015-12-17, 10:57 am)cb4960 Wrote: Other disturbing plans include dropping support for heavyweight themes such as my favorite FT DeepDark.

Wow, I had no idea there were themes like this available for Firefox, and I always choose Dark themes whenever possible for everything I use, so this is perfect. Thanks for sharing!

Roketzu Wrote:

cb4960 Wrote:Other disturbing plans include dropping support for heavyweight themes such as my favorite FT DeepDark.

Wow, I had no idea there were themes like this available for Firefox, and I always choose Dark themes whenever possible for everything I use, so this is perfect. Thanks for sharing!

You're welcome! I like to use it together with the Color Transform addon which can transform web content to have light text on a dark background. It works pretty well about 80% of the time, and can quickly be disabled by clicking its status bar icon. I like the orange text on black background option.

(2015-12-17, 11:23 am)cb4960 Wrote:

Roketzu Wrote:

cb4960 Wrote:Other disturbing plans include dropping support for heavyweight themes such as my favorite FT DeepDark.

Wow, I had no idea there were themes like this available for Firefox, and I always choose Dark themes whenever possible for everything I use, so this is perfect. Thanks for sharing!

You're welcome! I like to use it together with the Color Transform addon which can transform web content to have light text on a dark background. It works pretty well about 80% of the time, and can quickly be disabled by clicking its status bar icon. I like the orange text on black background option.

This is great, it's like a much more fleshed out version of that I was using previously. I must have missed it when searching for this type of addon. Thanks again!

By the way, why does Firefox still say Rikaisama is unsigned? It's the latest version.

I think I saw that error on some addons even before signing happened.

Standard release of Firefox has become quite messy over the past year; the new policy for addons finally made me switch to the dev version, though it has a host of problems of its own (rikaisama causes crashes if used in text boxes for me). If someone knows of a better build, I'd like to know... I'd like to keep using Firefox, if only so I can use rikaisama...

As for why it's messing up, I don't know exactly; I do know that it slowly accumulates errors as you upgrade, which is why it's often recommended to completely uninstall it and restart (and considering how often they update now). This doesn't always work for me, though.

(2015-12-13, 11:06 am)z1bbo Wrote: Hi cb I'm getting back to an older problem of audio not replaying, everything else works fine (even import with audio).
the ~rikai_audio.mp3 file is in the temp folder and is getting updated to the last words audio every time I try to play it.

I'm always getting these 2 error lines when trying to play the audio:

• decodeAudioData へ渡されたバッファにデコードできない不正なコンテンツが含まれています。       browser.xul
  
• TypeError: e is undefined        rikaichan.js:2918:22
  

I am using Firefox 42.0 and Rikaisama 22.9 on Windows 7 Pro

update: I've just changed my OS to Windows 10 Pro and now the Audio replay works fine. The problem might have been that I've had some windows media features disabled before!

I'm getting an error that Rikai-sama is unsigned and it's disabled... without hacking Firefox, it won't let me use it. I'm using Firefox 43 and version 22.9 of Rika-sama.

(2015-12-21, 10:21 am)toshiromiballza Wrote: By the way, why does Firefox still say Rikaisama is unsigned? It's the latest version.

Perhaps that message appears because Rikaisama is an "unlisted" addon, that is, one that is not hosted by Mozilla's addon site.

(2015-12-29, 10:17 pm)kraemder Wrote: I'm getting an error that Rikai-sama is unsigned and it's disabled... without hacking Firefox, it won't let me use it. I'm using Firefox 43 and version 22.9 of Rika-sama.

Which operating system do you use? I just added Mac and Ubuntu downloads here. If you are using one of those operating systems, try using the appropriate one and see if it works any better.

Hello Everyone,

Is anyone having a problem with the real-time import not working with the latest Firefox? I'm on version 43.0.2 and when I hit R to import nothing happens--no err or message, no nothing. I checked my settings and they are the same as they have always been.

Any advice would be appreciated

is there an option to unsuspend and/or reposition already existing vocab cards?

(2015-12-30, 2:48 pm)cb4960 Wrote: Perhaps that message appears because Rikaisama is an "unlisted" addon, that is, one that is not hosted by Mozilla's addon site.

Yes, indeed.

xpinstall.signatures.required = false

makes it work for now;

xpinstall.whitelist.required = false

will make it work when they remove xpinstall.signatures.required in 44. If they decide to remove xpinstall.whitelist.required as well, then we won't be able to use Rikaisama unless you upload it to mozilla.org (why isn't it there already anyway?).

more issues thread:
http://forum.koohii.com/thread-13523.html

(2016-01-02, 11:49 am)supermancampus Wrote: Hello Everyone,

Is anyone having a problem with the real-time import not working with the latest Firefox? I'm on version 43.0.2 and when I hit R to import nothing happens--no err or message, no nothing. I checked my settings and they are the same as they have always been.

Any advice would be appreciated

Same here, even tried reverting to an older version of Firefox to no avail.

Edit: Seems like it got fixed by switching the UDP port

Anyone having a problem with the hotkeys not working?

EDIT: It seems it's just the epwing mode.

(2016-01-26, 1:37 pm)kameden Wrote: Anyone having a problem with the hotkeys not working?

EDIT: It seems it's just the epwing mode.

Still seems to be working for me. Firefox 44 + Rikaisama 22.9. Perhaps another addon is using those keys?

Rikaisama was disabled in the latest version of FF.
"Some add-ons have been disabled  The following add-ons have not been verified for use in Firefox. You can find replacements or ask the developer to get them verified.  Learn more about our efforts to help keep you safe online.  Developers interested in getting their add-ons verified can continue by reading our manual."
-EDIT-
Fixed by changing xpinstall.signatures.required to false in about:config. Apparently this will work till FF46.

(2016-02-19, 4:29 am)xd1986k Wrote: Rikaisama was disabled in the latest version of FF.
"Some add-ons have been disabled  The following add-ons have not been verified for use in Firefox. You can find replacements or ask the developer to get them verified.  Learn more about our efforts to help keep you safe online.  Developers interested in getting their add-ons verified can continue by reading our manual."
-EDIT-
Fixed by changing xpinstall.signatures.required to false in about:config. Apparently this will work till FF46.

Hmmm. I'm using Firefox 44.0.2 with xpinstall.signatures.required set to true and Rikaisama is still functioning without issue. Perhaps a simple uninstall/reinstall will fix the issue you are seeing.

(2016-02-21, 4:11 pm)cb4960 Wrote:

(2016-02-19, 4:29 am)xd1986k Wrote: Rikaisama was disabled in the latest version of FF.
"Some add-ons have been disabled  The following add-ons have not been verified for use in Firefox. You can find replacements or ask the developer to get them verified.  Learn more about our efforts to help keep you safe online.  Developers interested in getting their add-ons verified can continue by reading our manual."
-EDIT-
Fixed by changing xpinstall.signatures.required to false in about:config. Apparently this will work till FF46.

Hmmm. I'm using Firefox 44.0.2 with xpinstall.signatures.required set to true and Rikaisama is still functioning without issue. Perhaps a simple uninstall/reinstall will fix the issue you are seeing.

As an update to the above, Firefox just disabled Rikaisama for me as well saying that it could not be verified. Rikaisama is signed, so I'm not sure yet what the issue could be. I sent an email to the Mozilla add-on team, hopefully they can help me to resolve this.

cb4960 Wrote:

cb4960 Wrote:

xd1986k Wrote:Rikaisama was disabled in the latest version of FF.
"Some add-ons have been disabled  The following add-ons have not been verified for use in Firefox. You can find replacements or ask the developer to get them verified.  Learn more about our efforts to help keep you safe online.  Developers interested in getting their add-ons verified can continue by reading our manual."
-EDIT-
Fixed by changing xpinstall.signatures.required to false in about:config. Apparently this will work till FF46.

Hmmm. I'm using Firefox 44.0.2 with xpinstall.signatures.required set to true and Rikaisama is still functioning without issue. Perhaps a simple uninstall/reinstall will fix the issue you are seeing.

As an update to the above, Firefox just disabled Rikaisama for me as well saying that it could not be verified. Rikaisama is signed, so I'm not sure yet what the issue could be. I sent an email to the Mozilla add-on team, hopefully they can help me to resolve this.

A Mozilla engineer was able to shed some light on the issue. Should have a fix within the next few days. The issue was that Rikaisama writes a file to the Rikaisama plugin directory which causes the signature to change, thus causing Firefox to disable the Rikaisama because the computed signature differs from the expected signature. Seems obvious in hindsight.

I have just uploaded version 22.9.2 of the Rikaisama Firefox extension.

Download version 22.9.2 via SourceForge

What's New?

● Fixed issue that caused FIrefox to invalidate and disable Rikaisama.

cb4960

Rikaisama fails to load in Firefox 46+ for using nonstandard and obsolete array comprehension syntax (ref). It can be fixed on line 2755 in rikaichan.js by replacing:

Code:

// Convert the binary hash data to a hex string
var s = [rcxMain.toHexString(hash.charCodeAt(i)) for (i in hash)].join("");

 with:

Code:

var s = [for (i of hash) rcxMain.toHexString(hash.charCodeAt(i))].join("");

I have just uploaded version 22.9.3 of the Rikaisama Firefox extension.

Download version 22.9.3 via SourceForge

What's New?

● Fixed issue described by balloonguy in the previous post.

cb4960