Hello. I'm not a developer by any means so don't have a clue what I should be using as the selectors.

After having issues getting it to install and work on the Marinelli theme, I thought it would just immediately start doing what was needed to get my site looking right in IE, but I was wrong.

I see that I need to put selectors in???????? Can somebody help me and others by giving us details and examples for getting this right? My site is www.pagg.co.uk.

Thanks,
Neil

Comments

dennis best’s picture

dennis best commented

Hi Neil,

To simplify, selectors are those classes and ID's in your stylesheet. Let's say you have a style in your stylesheet that looks like this:

.foo {

-webkit-border-radius: 12px;
-moz-border-radius: 12px;
border-radius: 12px;
}

and you wanted those rounded corners to work in IE, you'd go to /admin/build/themes/css3pie and put the selector
".foo" (without quotes) in the box.

Each selector goes on a different line, so if you have several it would look like this:

.foo
.fee
.box
.container

and so on. That's all. Easy-peasy.

Good luck!

seftonn’s picture

seftonn commented

Thank you Dennis.

I've tried this and it's not working. Any suggestions?

Thanks,
Neil

asb’s picture

asb commented

Same issue here for 6.x-1.0-alpha5 with CSS3PIE installed at ./sites/all/libraries/PIE. Even after manually registering CSS3 IDs and classes, IE8 shows no rounded corners etc.

And btw, shouldn't the module parse the CCS stylesheets on it's own and look for CSS3 styles it actually supports?

asb’s picture

asb commented
Component: User interface » Code
Category: support » bug

This module simply doesn't work as advertised, neither on D6 nor on D7, not even when linking the script into the IDs/classes. Changing to bug report.

blackice2999’s picture

blackice2999 commented
Status: Active » Closed (works as designed)

Hi,

sorry can´t accept as Bug Report... the module works as designed. you dont need to link any script in your css file only add the css classes that you use in your theme file to the admin form... thats it´s no more, no less...

#3 - i dont think that are a parsing feature is generic enough... if you have more than one theme like for "og" or per user theme you run into many problems... duplicate classes / id´s and much more... if you want to provide a feature patch about this and are done with all these problems i dont have any problems to add them.

best regards
Dennis

asb’s picture

asb commented

the module works as designed

If it actually is designed to do nothing at all... yes, it does that. Would be nice to state that on the project page, though.

#1116120: css3pie module not working: because of subtheme?
#1116110: css3pie module: something wrong with paths?

zoon_unit’s picture

zoon_unit commented

What about multiple selectors??

I have selectors like this:
.node-links ul li a {css code here...}

Do all these selectors go on one line?

I too have NEVER been able to get this module to work as stated, even though I've followed the (sparse) directions.

You might get less issues if you add a bit more explanation about selectors to your readme file....

Just sayin...

jjsmyth1984’s picture

jjsmyth1984 commented

I subscribe to this as I am wondering the same thing.

If I get this module working as Advertised it will be amazing for me, so I have my fingers crossed :)

Thanks,

Joe