W3C home > Mailing lists > Public > www-validator@w3.org > March 2017

Re: so who is right

From: Eric Richards <2eric.richards@gmail.com>
Date: Tue, 21 Mar 2017 21:03:04 +1300
Message-ID: <CA+Dr9BacRBuOaMGys4TYZ4FfQjEbw+xXCLaNzuUzHj3H7y31+Q@mail.gmail.com>
To: "O'Guin, Phaewryn D." <JDO09280@ccv.vsc.edu>
Cc: David Dorward <david@dorward.me.uk>, "www-validator@w3.org" <www-validator@w3.org>
oh silly me, it looks like one fails to find a comment with in a comment.

sorry my mistake. Even so it means the other one does not do its work so well.

On 3/21/17, O'Guin, Phaewryn D. <JDO09280@ccv.vsc.edu> wrote:
> I suspect the problem is elsewhere because I can go to
> https://jigsaw.w3.org/css-validator/#validate_by_input and put in exactly /*
> and the */ and it comes back as perfectly valid. That is a correct CSS
> comment format. Attach the entire file and I'll try to find your problem if
> you'd like.
>
>
> Regards,
>
> Phaewryn (J.D.) O’Guin
> -----Original Message-----
> From: David Dorward [mailto:david@dorward.me.uk]
> Sent: Friday, March 17, 2017 3:06 AM - 3:06 AM
> To: Eric Richards <2eric.richards@gmail.com>
> Cc: www-validator@w3.org
> Subject: Re: so who is right
>
> On 17 Mar 2017, at 1:03, Eric Richards wrote:
>> we have
>> https://jigsaw.w3.org/css-validator
>> which does not like comments in between the /* and the */
>>
>> but then thank goodness
>> https://validator.w3.org
>> finds everything OK
>
> One of those tools validates markup and one validates CSS … so they are
> probably both right as far as their areas of interest are concerned.
> It is difficult to tell what you mean though, and you didn’t provide a test
> case to demonstrate the issue you are having.
>
>
Received on Tuesday, 21 March 2017 08:03:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 March 2017 08:03:49 UTC