Security error" code: "1000 in web content with Skype extension for Firefox

VERIFIED WORKSFORME

Status

()

Firefox
Security
VERIFIED WORKSFORME
8 years ago
7 years ago

People

(Reporter: Sebastian, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; pl; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; pl; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

Security error" code: "1000 is also caused by Skype extension for Firefox. 
For example when on www.multibe.com we are trying to change dynamically style through JS function there is an error 1000 while reading selectors.
I think this is because Skype extension for Firefox adds its JS and CSS files with some HTML code and this causes this serious error.


Reproducible: Always

Steps to Reproduce:
1. http://multibe.pl/register.html  (i.e. while buidling an avatar)
2.
3.
Actual Results:  
FireBug show Security error" code: "1000 

Expected Results:  
Should not be this problem because all JS and CSS files are from the same domain. 
Only Skype adds its own CSS and JS while showing generated webpage and we think this causes this problem.

This problem occurs on almost every version of FireFox with Skype Extension Installed. We have tested it on Windows 7 and XP.
Report this to the skype developer ?

Comment 2

8 years ago
It would help if someone created a simple case demonstrating what leads to the security error, since it could be just a problem in the extension or something to fix in the browser itself.
Summary: Security error" code: "1000 with Skype extension for Firefox → Security error" code: "1000 in web content with Skype extension for Firefox
Sebastian, what skype add-on version do you have?
(Reporter)

Comment 4

8 years ago
(In reply to comment #3)
> Sebastian, what skype add-on version do you have?

Hi Boris,

Now I have Skype v. 4.2.0.166, and I think I used it at the time when I noticed this irritating problem.

However, it seems that the problem has been resolved. With an amendment in the family of FF 3.6 (which I do not remember exactly) the problem disappeared.

Thank you for your comment and for your question. I'm extremely happy that someone from the other end of the world wants to join in and help solve this problem.

All the best

Sebastian
Sebastian, thanks.  Resolving this, since it seems to be working now, but please reopen if you have this problem again!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.