Unwanted warning coming

[GoogleCodeExporter]

What version of gwt and gwt-incubator are you using?
gwt 1.5.3 , gwt-incubator-1.5.2008.12.28

When I tried to inject my css like

StyleElement elt = StyleInjector.injectStylesheet
(ResourceManager.getCssBasic().getText());
                    StyleInjector.setContents(elt, 
ResourceManager.getCssTheme().getText());

and tried 
mvn install , its showing so many warning like

core.swt.client.i18n.ResourcesInterface
         Invoking <generate-with 
class='com.google.gwt.libideas.resources.rebind.context.InlineResou
rceBundleGenerator'/>
            Preparing method css
               The following problems were detected
                  [WARN] Line 1281 column 3: encountered "_". Was 
expecting one of: "{" "," "[" "."
":" <HASH> "+" ">"
                  [WARN] Line 3028 column 6: encountered "#15428B". Was 
expectin
g one of: <IDENT> <FUNCTION>
                  [WARN] Line 3029 column 34: encountered ";". Was 
expecting one
 of: "{" "," "[" "." ":" <HASH> "+" ">"
                  [WARN] Line 3030 column 10: encountered "11px". Was 
expecting
one of: <IDENT> <FUNCTION>
                  [WARN] Line 3031 column 18: encountered ";". Was 
expecting one
 of: "{" "," "[" "." ":" <HASH> "+" ">" etc..

Can you help me how can i avoid this warning? Is there any specifc rule 
for css creation?

thanks and regards
suje

Original issue reported on code.google.com by sujeesh...@gmail.com on 20 Feb 2009 at 12:37

[GoogleCodeExporter]

Original comment by ecc%google.com@gtempaccount.com on 2 Mar 2009 at 4:08

[GoogleCodeExporter]

These warnings are generated because the parser is ignoring grammatically 
invalid CSS.  Admittedly, the W3C 
Flute parser is excessively pedantic, but warnings of this type can be fixed by 
ensuring that you are conforming 
to the CSS2 grammar.

Marking as NeedsInfo, but feel free to follow-up with excerpts from your 
original CSS file.

Original comment by bobv%google.com@gtempaccount.com on 3 Mar 2009 at 3:05

• Changed state: NeedsInfo

[GoogleCodeExporter]

I am running into the same issue. Running the CSS though the W3C validator 
tells me
that it is in fact valid.

A simplified css stylesheet is attached which exhibits this bug.

Original comment by christop...@gmail.com on 19 Jun 2009 at 8:19

Attachments:

• site.css