6 replies to this topic

[hansinke]

I normally can put a \9 after a CSS command to make a IE8 hack. Unlucky it is stripped in the preprocessor of custom code. So that does not work out. I can remove the hacks and distribute them to style.css but that is a dirty fix.

Can you fix the problem or is there a proper work-around?

Example:
.fbox {padding: 15px 30px\9 15px 10px\9 !important; } becomes:
.fbox {padding: 15px 30px9 15px 10px9 !important; }

Adding an extra space 30px \9 results in a compile error!

[hansinke]

I already mentioned that an extra space does not help.

[Rob]

I will forward this to our developers, but our NavBar is already set for IE8. What did you intend to hack?

[hansinke]

Indeed I had a problem in IE8 with the navbar displaying both the navigation and the text displayed whenever it was used on mobile.
Also I did use other margins/paddings for my boxes and sometimes use different fonts (not all are rendering nice).

[Simon_P]

The custom CSS box runs the code through the less compiler which checks for valid CSS. Your 'hack' is not valid CSS add it to customise plugin style.css

[hansinke]

That is a very clever idea! It also helps with the custom taxonomies!

[Danny]

The topic was marked as resolved.