Script failure

[Ton Plomp]

Sometimes my FireFox 2.0 is taking up to 100% of my processor while viewing LAVA, and sometimes I get an error saying that the script stopt reacting.

If I look at the failure console I see these errors:

1: Warning: Unknown propertye 'filter'. Declaration ignored.

Sourcefile: http://pagead2.googlesyndication.com/pagead......

2: Warning: Unknown propertye 'filter'. Declaration ignored.

Sourcefile: http://forums.lavag.org/style_images/css_14.css

3: Warning: Error during parsing of the value for property 'clear'. Declaration ignarored.

Sourcefile: http://forums.lavag.org/style_images/1/fol...ges/css_rte.css

4: Warning: Error during parsing of the value for property 'cursor'. Declaration ignarored.

Sourcefile: http://forums.lavag.org/style_images/1/fol...ges/css_rte.css

Among others....

Does anybody else have these issues?

Ton

[Michael Aivaliotis]

btw, those are warnings not errors. All web pages generate warnings, even on ni.com. This is a way of life on the web. Some declarations only work for certain web browsers. If a browser does not recognize something, it generates a warning like the one's you indicate.

Sometimes however I have noticed that the Google ads cause pages to pause for a while before they load. Haven't investigated this yet but I will soon.

[crelf]

QUOTE(Michael_Aivaliotis @ May 13 2007, 09:42 AM)

All web pages generate warnings... This is a way of life on the web.

Interesting, isn't it? Even if you try to load an xml file that you created, and know that it's clean, your browser will probably tell you that it has errors, or is unsafe and something was blocked (even though it still displays perfectly) - I never understood that...

[Michael Aivaliotis]

Interpreting web standards isn't my job, thank god, but I think it depends on what version of the standard the browser chose to recognize and how much of it.

[crelf]

QUOTE(Michael_Aivaliotis @ May 13 2007, 11:54 AM)

Interpreting web standards isn't my job, thank god, but I think it depends on what version of the standard the browser chose to recognize and how much of it.

Yeah - it's difficult for a browser to be fully compliant with only one "standard" when so many sites and pages demand it to go outside that standard.