From: Andrew Ballard 
> On Thu, Jun 4, 2009 at 12:33 PM, Michael A. Peters <>
>> Andrew Ballard wrote:
>>> I just thought I'd toss this out there. Do you know that there is an
>>> effort to remove browser support this attribute (or at least give
>>> user a browser configuration option to ignore it)?
>>> This article discusses some of the issues involved.
>> That page says:
>> "When writing HTML, such authors should declare and validate against
>> custom doctype including the autocomplete attribute (example HTML
>> However, there is currently no way to trigger the same user agent
>> functionality with an attribute in XHTML. This constitutes an
>> obstacle to the adoption of XML-based markup."
>> That page is wrong.
>> It took me 10 minutes in google to find a way to do it in xhtml and
have the
>> xhtml validate. And I didn't have to use a custom DTD. Only thing I
had to
>> do is send the application/xhtml+xml header - which I already send,
>> that's the proper way to serve xhtml 1.1.
> I wasn't really taking a position on the issue. I just thought it
> worth noting that there seems to be a contingent that wants to remove
> the attribute. From what I read, they have already conceded to
> language that says a user-agent may choose to implement it, but is not
> required to do so.

There is nothing to remove. It is a proprietary extension and not likely
to ever be accepted as part of the W3C standards. As such, it won't be
in any W3C DTD, but will always require a custom DTD be supplied
locally. Each browser supplier must decide whether to support it or
leave it out.

>From my viewpoint, the bigger need is to educate administrators of
publicly available computers to disable autocomplete in the browser
configuration. If they would do that, when you go to the workstation in
the library, you can't see the credentials of the last user, and the
next user won't be able to retrieve yours.

Bob McConnell

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to