Sherry Williams | 3 Nov 2010 06:37

http://www.oldtrinityfc.com/

Dear Webmaster,

My name is Sherry, and my company Topspot-Promotions represents online sport sites in various domains. We
are looking at reputable sites to offer them profitable opportunities to help promote some of my clients sites.

We would like to know if you are interested in working with us on this. For further details please don't
hesitate to contact me.

Cheers,
Sherry Williams 
Advertising Consultant
Business Development Department
Sherry.Williams <at> topspot-promotions.net
http://www.topspot-promotions.net

Sasha Saveliev | 2 Nov 2010 20:34
Picon
Favicon

webkitdirectory in input

Hello.

I found problem in your validator.
Google Chrome 7 supports directory uploads with input attribute "webkitdirectory". I develop little
example 
of this feature: http://html5blog.ru/examples/directory-upload.php
And validate this with your validator: http://validator.w3.org/check?
uri=http://html5blog.ru/examples/directory-upload.php&charset=
(detect+automatically)&doctype=Inline&group=0&user-agent=W3C_Validator/1.1
Is it true that there is error: Attribute webkitdirectory not allowed on element input at this point? Is 
attribute "webkitdirectory" is part of HTML5?

Sorry for my English.

David Dorward | 3 Nov 2010 11:49
Picon
Favicon
Gravatar

Re: webkitdirectory in input


On 2 Nov 2010, at 19:34, Sasha Saveliev wrote:
> Is it true that there is error: Attribute webkitdirectory not allowed on element input at this point?

Yes

> Is attribute "webkitdirectory" is part of HTML5?

No

--

-- 
David Dorward
http://dorward.me.uk

Tatham Oddie | 3 Nov 2010 22:48
Picon
Gravatar

RE: webkitdirectory in input

"webkitdirectory" is a proprietary solution. It is specific to Chrome. It is
_not_ part of any standard.

_If_ it gets standardised, it will probably be called "directory".

Until then, it will not validate.

--
Tatham Oddie
au mob: +61 414 275 989, us cell: +1 213 280 9140, skype: tathamoddie
If you're printing this email, you're doing it wrong. This is a computer,
not a typewriter.

-----Original Message-----
From: www-validator-request <at> w3.org [mailto:www-validator-request <at> w3.org] On
Behalf Of Sasha Saveliev
Sent: Wednesday, 3 November 2010 6:35 AM
To: www-validator <at> w3.org
Subject: webkitdirectory in input

Hello.

I found problem in your validator.
Google Chrome 7 supports directory uploads with input attribute
"webkitdirectory". I develop little example of this feature:
http://html5blog.ru/examples/directory-upload.php
And validate this with your validator: http://validator.w3.org/check?
uri=http://html5blog.ru/examples/directory-upload.php&charset=
(detect+automatically)&doctype=Inline&group=0&user-agent=W3C_Validator/1.1
Is it true that there is error: Attribute webkitdirectory not allowed on
(Continue reading)

Sherry.Williams | 4 Nov 2010 06:44

http://www.dampsfootball.com/

Dear Webmaster,

My name is Sherry, and my company Topspot-Promotions represents online sport sites in various domains. We
are looking at reputable sites to offer them profitable opportunities to help promote some of my clients sites.

We would like to know if you are interested in working with us on this. For further details please don't
hesitate to contact me.

Cheers,
Sherry Williams 
Advertising Consultant
Business Development Department
Sherry.Williams <at> topspot-promotions.net
http://www.topspot-promotions.net

gachris | 5 Nov 2010 14:18
Picon
Favicon

url strings, should be ignored

6 errors because words in URL strings are undefined.
when the validator should not be even reading url strings

example:
http://validator.w3.org/check?uri=http%3A%2F%2Fhome.earthlink.net%2F%7Ebeta-quadrant%2Fazalt05.html&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.1

David Dorward | 5 Nov 2010 22:39
Picon
Favicon
Gravatar

Re: url strings, should be ignored


On 5 Nov 2010, at 13:18, gachris <at> earthlink.net wrote:

> 6 errors because words in URL strings are undefined.
> when the validator should not be even reading url strings

Incorrect.

To quote from the URL you included:

An entity reference was found in the document, but there is no reference by that name defined. Often this is
caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing
semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG
in "Ampersands in URLs": http://www.htmlhelp.com/tools/validator/problems.html#amp

--

-- 
David Dorward
http://dorward.me.uk

Ville Skyttä | 6 Nov 2010 09:24
Picon
Picon
Favicon

Re: "No Referer header found!" ?!?

On Monday 13 September 2010, jason.vas.dias <at> gmail.com wrote:

> I do think that it is a bug that the error text suggests that
> validator.w3.org is available through HTTPS, when it isn't.

I don't think the error text suggests that.  Anyway, the current development 
version tries to document issues related to https for icons and the 
uri=referer mechanism more prominently.

http://dvcs.w3.org/hg/markup-validator/rev/a2884dc7aa27
http://dvcs.w3.org/hg/markup-validator/rev/3705099f9260

Ville Skyttä | 6 Nov 2010 09:59
Picon
Picon
Favicon

Re: bug: case-insensitive checking of IDs

On Tuesday 19 October 2010, Michael(tm) Smith wrote:
> I notice that HTML4 checking performed by the markup validator is raising
> false-positive "duplicate ID" errors for IDs the match case insensitively.
> 
> Is that intentional? If so, why? I know that browsers certainly don't
> process IDs case insensitively, and I'm not aware of other UAs that do.
> 
> If it's not intentional, is it a known issue, or should I raise a new bug
> for it?

It's not intentional, and it was not a known issue at least to me.  But I 
believe it's an issue that needs fixing in OpenSP, that's where the message 
comes from, and I can't think of a sane workaround offhand in validator that 
we could apply in the meantime.

Ville Skyttä | 6 Nov 2010 19:25
Picon
Picon
Favicon

Re: IDN-support for the validate by URI (IRI) feature

On Tuesday 24 August 2010, Martin Janecke wrote:
> Can you please make the http://validator.w3.org/ accept IDNs in its
> validate by ~URI~ field?

The current development version at http://qa-dev.w3.org/wmvs/HEAD/ has some 
fixes in it that make IDN's much more likely to work.


Gmane