This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
with this code: html, body { height: 100%; @include box-sizing(border-box); } " @include box-sizing " is underlined with red and highlighting is off, but compiles OK. But with this:
body>footer { position: fixed; z-index: 1; left: 0; bottom: 0; right: 0; @include box-shadow(0, 0, 8px); background: #c72; }
it doesn't complain and highlighting is OK. You can see this in the pictures above.
|
|
|
Also:
body
{
font-family: Verdana, Arial, Liberation Sans, DejaVu Sans, sans-serif;
as you can see, fonts are not recognized and indeed it's underlined with red, but compiles.
|
|
|
Thanks for reporting these issues. There should be a fix up for the 'hyphenated values in mixin arguments' issue in the next 24-36 hours. You can work around the issue with spaces in font names by quoting the font names e.g. font-family: Verdana, Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif; This is recommended for font names with spaces in them -- in fact some sources insist that such names *must* be quoted. However we realise that in practice the unquoted form seems to be acceptable and that users will have existing CSS that uses the unquoted form, so we will still try to get this fixed for you! |
|
|
html, body { height: 100%; @include box-sizing(border-box); } you can put border-box in double or single quotes, "border-box" or 'border-box' |
|
|
thanx. Last build fixed "include" issues. But for font names with spaces -- need to surround with " or '. |
|