Archived

This topic is now archived and is closed to further replies.

  • 0

Resolved IE8 hacks


Question

Posted · Report post

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 30px9 15px 10px9 !important; } becomes:

.fbox {padding: 15px 30px9 15px 10px9 !important; }

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

Share this post


Link to post
Share on other sites

6 answers to this question

Posted · Report post

The topic was marked as resolved.

Share this post


Link to post
Share on other sites

Posted · Report post

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

Share this post


Link to post
Share on other sites

Posted · Report post

I already mentioned that an extra space does not help.

Share this post


Link to post
Share on other sites

Posted · Report post

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

Share this post


Link to post
Share on other sites

Posted · Report post

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).

Share this post


Link to post
Share on other sites

Posted · Report post

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

Share this post


Link to post
Share on other sites