Stopping browser prompts in forms

[Christine Forber]

I have created a form that incorporates AJAX to provide suggestions from
the database contents for the given field. The problem is that many
browsers do their own "suggestions" based on previous values used for
that field. These browser suggestions sometimes completely hide the AJAX
suggestions. Is there some way to turn off this browser behaviour in the
form? (Yes, I know how to do it with my browser, but if it is happening
to me, it is happening to my customers and I want to stop that behaviour
only for the AJAX enabled fields in this particular form.)

Not sure if the solution is html or javascript, so sent this message to
both groups.

Thanks,
Christine

[Gregor Kofler]

Christine Forber meinte:

I have created a form that incorporates AJAX to provide suggestions from
the database contents for the given field. The problem is that many
browsers do their own "suggestions" based on previous values used for
that field. These browser suggestions sometimes completely hide the AJAX
suggestions. Is there some way to turn off this browser behaviour in the
form? (Yes, I know how to do it with my browser, but if it is happening
to me, it is happening to my customers and I want to stop that behaviour
only for the AJAX enabled fields in this particular form.)

Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.

Gregor

--
http://www.gregorkofler.at ::: Landschafts- und Reisefotografie
http://www.licht-blick.at ::: Forum für Multivisionsvorträge
http://www.image2d.com ::: Bildagentur für den alpinen Raum

[Thomas 'PointedEars' Lahn]

Gregor Kofler wrote:

Christine Forber meinte:

>[AJAX for auto-completion is hindered by built-in auto-completion]
Is there some way to turn off this browser behaviour in the
form? (Yes, I know how to do it with my browser, but if it is happening
to me, it is happening to my customers and I want to stop that behaviour
only for the AJAX enabled fields in this particular form.)

Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.

If that was the case (I have not tested it), the attribute should be either
be declared (which however fails when parsed as tagsoup-HTML) or its value
set through a properly feature-tested DOM element property, because using it
as above would create invalid markup. Although no recent browser (I know
of) uses a validating (XML) parser, validity is crucial for a AJAX Web
application iff it uses XML or an XML application as underlying markup language.
PointedEars
--
realism: HTML 4.01 Strict
evangelism: XHTML 1.0 Strict
madness: XHTML 1.1 as application/xhtml+xml
-- Bjoern Hoehrmann

[Christine Forber]

Gregor Kofler wrote:

Christine Forber meinte:

>I have created a form that incorporates AJAX to provide suggestions
from the database contents for the given field. The problem is that
many browsers do their own "suggestions" based on previous values used
for that field. These browser suggestions sometimes completely hide
the AJAX suggestions. Is there some way to turn off this browser
behaviour in the form? (Yes, I know how to do it with my browser, but
if it is happening to me, it is happening to my customers and I want
to stop that behaviour only for the AJAX enabled fields in this
particular form.)

Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.

I only want to indicate when this feature should be turned off. Checked
and autocomplete="off" works in both FireFox and IE.

Many thanks.
Christine

[Gregor Kofler]

Thomas 'PointedEars' Lahn meinte:

Gregor Kofler wrote:

>Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.

If that was the case (I have not tested it), the attribute should be either
be declared (which however fails when parsed as tagsoup-HTML) or its value
set through a properly feature-tested DOM element property, because using it
as above would create invalid markup.

Well, I never stated that it is valid. However, Google [1] uses this
proprietary attribute in their smart suggest version, and it is, well
....er... recommended in various AJAX publications. My own smart suggest
version seems to work without worrying about autocomplete attributes.

Gregor
[1]
http://www.google.com/webhp?complete=1&hl=en

--
http://www.gregorkofler.at ::: Landschafts- und Reisefotografie
http://www.licht-blick.at ::: Forum für Multivisionsvorträge
http://www.image2d.com ::: Bildagentur für den alpinen Raum

[Thomas 'PointedEars' Lahn]

Gregor Kofler wrote:

Thomas 'PointedEars' Lahn meinte:

>Gregor Kofler wrote:

>>Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.

If that was the case (I have not tested it), the attribute should be either
be declared (which however fails when parsed as tagsoup-HTML) or its value
set through a properly feature-tested DOM element property, because using it
as above would create invalid markup.

Well, I never stated that it is valid.

And you have not stated that it is not Valid, hence my remark.

However, Google [1] uses this proprietary attribute in their smart
suggest version,

IBTD. That Google uses some code is hardly a sign of interoperability of
it. Google's code is compacted bloat-code.

and it is, well ...er... recommended in various AJAX publications.

Which only proves once more that there are no good books about JavaScript
and related concepts. Too many scriptkiddies think they are the real experts.

My own smart suggest version seems to work without worrying about
autocomplete attributes.
[...]
[1]
http://www.google.com/webhp?complete=1&hl=en

Testing a snippet in one Web browser or a number of Web browsers is hardly
an indication of its quality, especially regarding interoperability among
(X)HTML user agents.
PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f8*******************@news.demon.co.uk>

[Gregor Kofler]

Thomas 'PointedEars' Lahn meinte:

Gregor Kofler wrote:

>Thomas 'PointedEars' Lahn meinte:

>>Gregor Kofler wrote:
Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.
If that was the case (I have not tested it), the attribute should be either
be declared (which however fails when parsed as tagsoup-HTML) or its value
set through a properly feature-tested DOM element property, because using it
as above would create invalid markup.

Well, I never stated that it is valid.

And you have not stated that it is not Valid, hence my remark.

"Some browsers know something..." sounds pretty non-standard compliant
to me. Anyway, I should have pointed that out.

>However, Google [1] uses this proprietary attribute in their smart
suggest version,

IBTD. That Google uses some code is hardly a sign of interoperability of
it. Google's code is compacted bloat-code.

ACK. You don't even have to rate their JS efforts. A simple search
produces a webpage with 292 errors, no doctype declaration, deprecated
markup (center-tags) etc.
But then: the OP could have used this very search engine and gotten
everything that can be said to solve this problem...

Gregor

--
http://www.gregorkofler.at ::: Landschafts- und Reisefotografie
http://www.licht-blick.at ::: Forum für Multivisionsvorträge
http://www.image2d.com ::: Bildagentur für den alpinen Raum

[Christine Forber]

Gregor Kofler wrote:

Thomas 'PointedEars' Lahn meinte:

>Gregor Kofler wrote:

>>Thomas 'PointedEars' Lahn meinte:
Gregor Kofler wrote:
Some browser know a "autocomplete"-attribute for input fields.
autocomplete="off" might help.
If that was the case (I have not tested it), the attribute should be
either
be declared (which however fails when parsed as tagsoup-HTML) or its
value
set through a properly feature-tested DOM element property, because
using it
as above would create invalid markup.
Well, I never stated that it is valid.

And you have not stated that it is not Valid, hence my remark.

"Some browsers know something..." sounds pretty non-standard compliant
to me. Anyway, I should have pointed that out.

>>However, Google [1] uses this proprietary attribute in their smart
suggest version,

IBTD. That Google uses some code is hardly a sign of interoperability of
it. Google's code is compacted bloat-code.

ACK. You don't even have to rate their JS efforts. A simple search
produces a webpage with 292 errors, no doctype declaration, deprecated
markup (center-tags) etc.
But then: the OP could have used this very search engine and gotten
everything that can be said to solve this problem...

I tried a Google search, but was obviously not using the right search
terms as I didn't find the suggestion to use autocomplete. Which is why
I posted here. I know better than to just post here without at least
trying Google first!

Christine

[Purushotham Reddy]

Hi,
This is Purushotham, After being a lot of research i have found a
solution for turning off the automatic suggestions based on browser
cache values. The solution is set the "autocomplete" property of textbox
to off.

*** Sent via Developersdex http://www.developersdex.com ***