| CSS Validation [message #1005557] |
Sat, 26 January 2013 12:10  |
Eclipse User |
|
|
|
I don't know if this is a bug or configuration issue on my part, but I downloaded the lastest build of xtend yesterday (2.4.0.v201301250856), and I am getting hundreds of this error in all of my CSS files:
extraneous input ' ' expecting RULE_IDENT {...} Xtext Check (fast)
It seems that any css rules that have '.' in the number cause this error, such as:
Furthermore, there does not seem to be a way to turn of the validation on the css files.
Has anybody else seen this issue?
|
|
|
|
|
|
|
|
| Re: CSS Validation [message #1005743 is a reply to message #1005727] |
Mon, 28 January 2013 08:46  |
| Eclipse User |
|
|
|
Hi,
No offense taken ;-) - I guess because the parser is generated upgrading
Xtext to 2.4.0 can't lead to such a problem. So if it works with 2.3.1
it will still work with 2.4.0.
Knowing what Steven has installed would help to find out who is the one
to blame.
Tom
Am 28.01.13 13:31, schrieb Sebastian Zarnekow:
> Sorry Tom, didn't meant to blame e(fx)clipse for that one. The e4 css
> stuff sounds more likely to cause the issue.
>
> Regards,
> Sebastian
>
> Am 28.01.13 13:20, schrieb Tom Schindl:
>> e(fx)clipse is perfectly happy with .9em and translate it to what it is
>> 0.9em ;-) but I'm running with xtext 2.3.1 have not yet tried 2.4.0.
>>
>> It could also be the e4 css editor, which is also based on xtext
>>
>> Tom
>>
>> Am 28.01.13 09:55, schrieb Sebastian Zarnekow:
>>> Am 27.01.13 15:07, schrieb Steven Spungin:
>>>> I do not see any installed plugin with xtext and css in the name.
>>>> Which
>>>> feature would have (or should have) installed the css validator?
>>>
>>> Probably e(fx)clipse? I'm not sure - don't know each and every
>>> application of Xtext.
>>>
>>> Regards,
>>> Sebastian
>>
>
>
|
|
|
| Re: CSS Validation [message #1005871 is a reply to message #1005743] |
Tue, 29 January 2013 02:18 |
| Eclipse User |
|
|
|
Hi Tom,
yes, upgrading to 2.4.0 but still using e(fx)clipse that was compiled to
2.3.1 will lead to all sorts of problems but not this one :-)
Regards,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 28.01.13 14:46, schrieb Tom Schindl:
> Hi,
>
> No offense taken ;-) - I guess because the parser is generated upgrading
> Xtext to 2.4.0 can't lead to such a problem. So if it works with 2.3.1
> it will still work with 2.4.0.
>
> Knowing what Steven has installed would help to find out who is the one
> to blame.
>
> Tom
>
> Am 28.01.13 13:31, schrieb Sebastian Zarnekow:
>> Sorry Tom, didn't meant to blame e(fx)clipse for that one. The e4 css
>> stuff sounds more likely to cause the issue.
>>
>> Regards,
>> Sebastian
>>
>> Am 28.01.13 13:20, schrieb Tom Schindl:
>>> e(fx)clipse is perfectly happy with .9em and translate it to what it is
>>> 0.9em ;-) but I'm running with xtext 2.3.1 have not yet tried 2.4.0.
>>>
>>> It could also be the e4 css editor, which is also based on xtext
>>>
>>> Tom
>>>
>>> Am 28.01.13 09:55, schrieb Sebastian Zarnekow:
>>>> Am 27.01.13 15:07, schrieb Steven Spungin:
>>>>> I do not see any installed plugin with xtext and css in the name.
>>>>> Which
>>>>> feature would have (or should have) installed the css validator?
>>>>
>>>> Probably e(fx)clipse? I'm not sure - don't know each and every
>>>> application of Xtext.
>>>>
>>>> Regards,
>>>> Sebastian
>>>
>>
>>
>
|
|
|
|
|
| Re: CSS Validation [message #1067857 is a reply to message #1005557] |
Wed, 10 July 2013 18:05 |
| Eclipse User |
|
|
|
I'm a bit confused. Did anyone figure out the problem?
I'm having a very similar issue. With e(fx)clipse installed on Eclipse Java EE. I have tried it with only the "e(fx)clipse - Composite - FX Tooling" and get the same results. It says:
Unknown property: "text-decoration"
for this code:
a:link
{ text-decoration: none; color: #ff0000 }
It seems like it's a problem between the EE css plugin and the fx css plugin. If I uninstall fx, the problem goes away. I have to reopen the .css file because it says:
No editor descriptor for id at.bestsolution.efxclipse.tooling.css.CssDsl
but after I reopen it, everything is back to normal. I can once again view the css file with syntax highlighting. It's just obviously lacking the other great qualities I was hoping to get from e(fx)clipse.
|
|
|
Powered by
FUDForum. Page generated in 0.06131 seconds
Home