Re: Issue 31c: Meta generator

Daniel Glazman, Fri, 18 May 2012 20:58:56 +0200:
> Le 18/05/12 20:43, John Foliot a écrit : 

> Not worth a "public warning", and too great power given to chairs w/o
> control, IMHO.

As a more helpful thing talk about: What are your insights, as a 
WYSIWYG HTML generator vendor,  with regard to the meta generator 
exception? 

Because BlueGriffon inserts a meta generator, and it only gives the 
author two options: Empty or non-empty @alt. But if BlueGriffon works 
with some HTML were the @alt already is lacking, then it does nothing 
about it AFAICT. Which in turn means that the page will still get a 
‘valid’ stamp from the validator.

Further more, the fact that BlueGriffon inserts the meta generator 
*also* means that the validator will never report an error for code 
such as this:

<a href=foo ><img src=bar ></a>

To see the difference, you might compare the validation of a page 
without meta generator, [1] with a validation of the same code *with* 
the meta generator. [2]

Is it helpful to the BlueGriffon users that [2] makes it validator? Or 
does it hurt them?

Btw, I feel that one negative effect is on the the validator itself: 
Essentially this gives the validator two modes. And we all know how 
difficult it can be to keep modes in sync ... 

For instance: I would much rather discuss why the validator doesn't 
issue a warning or error for the following code:

<a href=foo ><img src=bar alt="" ></a>

But I feel that the confusing meta generator exception hampers progress 
and discussion on other, more important issues related to validator. So 
if you as authoring tool vendor have something to bring to the table in 
this issue, then I think it could be really helpful.

[1] http://tinyurl.com/868cr8h

[2] http://tinyurl.com/bufe9v8

-- 
Leif Halvard Silli

Received on Friday, 18 May 2012 19:33:56 UTC