Parse Errors in oxid.css

Hi again,

A few more errors I would like to clean up.

At /out/azure/src/css/oxid.css I about 10 error codes which mostly relate to “Parse Errors”. I am unsure what is causing these errors:

1675 	#currencies a, #languages a, .flyoutMenu a 	Property zoom doesn't exist : 1
4306 	.itemSlider .slideNav 	Parse Error =90)
4323 	.itemSlider .slideNav:hover 	Parse Error =100)
4362 	.itemSlider .prevItem:hover span.slideBg, .itemSlider .nextItem:hover span.slideBg 	Parse Error =90)
4404 	.itemSlider li a.viewAllHover 	Parse Error =100)
4421 	.itemSlider a.sliderHover, a.sliderHover 	Parse Error =70)
4526 	.ui-dialog .ui-dialog-content 	[COLOR="Magenta"]Property zoom doesn't exist : 1[/COLOR]
5218 	#cookieNote 	Parse Error = 90)
5274 	#betaNote 	Parse Error = 90) 

I have checked for previous posts and search through the online php manual (http://php.net/support.php) and scrolled through stackoverflow posts and the only thing close refers to:

CSS opacity parse errors

Is there a quick fix to these errors? or should I just ignore them. I am eager to learn.

Muchos Gracias :smiley:

During the history of CSS, it happened multiple times that the various browser vendors implemented their own variations, extensions etc. of the official standard. Sometimes those changes were later incorporated into updated versions the standard, sometimes they were not and just went the way of the dodo.

Because of that, if you want your stylesheets to work with a wide range of browsers, current and older, you sometimes need to “say things twice”. For example, to have the opacity of an element working correctly, you might need to add a directive that Internet Explorer 7 understands (in an IE 7-specific syntax) plus a directive that IE 8 understands (in another, IE8-specific syntax) plus a directive according to the standard and so forth.

Of course, IE7 doesn’t understand the syntax variation for IE 8 and vice versa. Luckily, browsers generally just discard CSS directives they don’t understand. As long as your stylesheets do what you want them to do in all browsers you intend to support, you can next to always safely ignore such error messages.

In your specific case, the browser you used complains that it can’t parse things like ‘=90’ oder ‘=100’. That actually might very well be an opacity setting for an older IE version, something like ‘filter:alpha(opacity=90);’ Additionally, it doesn’t seem to know about the non-standard property ‘zoom’. But as I wrote above, as long as everything’s working, no need to worry.

So long,

Henning

Thanks a bundle Henning for such a clear and substantial answer. There may be a ‘Senior Member’ handle next to my name but that just means I have been at it for awhile, but always in a Newbie capacity and answers like yours make the learning curve a lot easier. In fact if I was rich I would just hire someone to do this stuff because it is an art form or craft that is under appreciated by some. I can speak 3 languages but none of them are J sharp or HTML. :stuck_out_tongue:

By the way your English, like many in the forum, is perfect! Perhaps you are a native born English speaking person slumming in Darmstadt?

Cheers,

Don

Hi Don,

thanks for the compliments :slight_smile: I, for my part, may have a “junior member” title here. But I’ve been around the web since 1996, and the last few years I’ve been working as a freelancer (web development, server administration, editorial services, community managerment and so forth). One of my customers is using OXID for his shop, so I come here from time to time to find help or to help others.

I’ve found that it’s not only the nice thing to do to answer question like yours. It’s also a matter of mutuality. How often did I myself benefit from an explanation, a tutorial etc. that somebody put on the web, here in the forums, on StackExchange or at a whole lot other places. So it’s only logical to give something back when I can.

Additionally I’ve found that explaining something to somebody is a very good test of your own knowledge and understanding of a matter. If you explain something or even just imagine to do so, you often stumble upon your own knowledge gaps.

As far as my English is concernd, thanks again :slight_smile: My first language is German. But the lingua franca around the web is English, especially when tech is concerned. So, over the years, I’ve gotten quite fluent, if I may say so myself.

So long,

Henning