|
|
Posted by Christine Forber on 08/10/07 20:59
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
Navigation:
[Reply to this message]
|