Weird behavior of signed extension
First of all: You can install an extension as
- a temporary extension for testing and debugging
- signed extension from addons.mozilla.org (*.xpi)
- signed extension from anyother website (*.xpi)
- unsigned extension from anywhere (*.xpi)
Yesterday I’ve recognized a very strange behaviour between the temporary extension and the signed/unsigned extension. The temporary extension is working fine, but the signed and unsigned extension is making problems. When you unpack the signed/unsigned extension and load it as temporary extension, it's working fine.
That isn't the normal behavior, because a temporary installation of an extension doesn’t fully mimic the behavior of a signed extension. If an extension works as temporary extension, it also works as signed/unsigned version and not the other way around. In my opinion this is highly unusual
At the moment the replacement of JavaScript files is working fine in all situations, but not with CSS and Font Awesome.