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

Unhandled Error: Security error: attempted to read protected variable #177

Closed
texnikru opened this issue Feb 18, 2014 · 12 comments
Closed

Comments

@texnikru
Copy link

Opera 12.16 x64 (Opera/9.80 (Windows NT 6.2; Win64; x64) Presto/2.12.388 Version/12.16)
Windows 8.1
opera_err

@azproduction
Copy link
Owner

I can not reproduce this error on Mac on both file:// and http:// protocols. Is it possible to configure build with disabled file_protocol?

{
    "file_protocol": false
}

Is there any steps to reproduce this error or live example of this error?

@texnikru
Copy link
Author

Project in public - http://goo.gl/oqXJE7
I cannot disable file_protocol because styles disapper after that.

@texnikru
Copy link
Author

Issue exists only in Opera 12.16

@azproduction
Copy link
Owner

I cannot disable file_protocol because styles disapper after that.

Hm, that is odd. LMD cleanups styles only on errors. And that is why they disappears.

I fixed this issue in branch issue-177. Could you please install lmd from that branch npm i git://github.com/azproduction/lmd.git#issue-177, rebuild you project and verify that everything is ok before release? This bug is pretty untestable.

@texnikru
Copy link
Author

This still fails.

I added some logs and this fails on this line:
console.log(typeof sheets[j].cssRules);

sheets variable and sheets[j] is ok

@texnikru
Copy link
Author

Also file_protocol I'm using for modem connections. It lost styles about after 3 seconds other case.

@azproduction
Copy link
Owner

I isolated this problem It caused by xdomain css files.

@azproduction
Copy link
Owner

At that time I wrote a test for this issue. But anyway let's double check it before release.
Please update lmd npm i git://github.com/azproduction/lmd.git#issue-177 again and rebuild.

PS file_protocol flag is ignored now, css loader supports file:// and xdomain by default.

@texnikru
Copy link
Author

All looking good.

Now File_protocol functionality is enabled by default?
I need to be sure styles will be loaded with slow connections too.

@azproduction
Copy link
Owner

Now File_protocol functionality is enabled by default?

Yes

In all css loaders there is no errorback for css. And there is no way to detect 404 or others (css does not care about status code).
I removed css cleanup on timeout and now there is no errorback for css.

@texnikru
Copy link
Author

Sounds good

@azproduction
Copy link
Owner

fixed in lmd@1.11.5

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