Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of melowe@gmail.com designates
 64.233.182.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=XgMn2COaaGGUUaA0MA8NOvQKVPan31FF7JAGZiqxSnDMU2r+8YqRPB/3dQzC9xfuDI4Zk5obvwQ5hbLukW3fhAdZNBqU7BZRjoHXz68asd4NgVokbR2icDgLpAD2/NrAHRg471bB2ckRBsatk99Fc9JCWWO+9tDA08T8zsVk2SE=
Message-ID: <3e1257da0603240217o1cc60cb2v74179262af65ae4f@mail.gmail.com>
Date: Fri, 24 Mar 2006 11:17:47 +0100
From: "Mark Lowe" <melowe@gmail.com>
To: dev@struts.apache.org
Subject: html taglib autocomplete
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

hello

We've got an app built already in production, and the issue of
autocompletion has come up. For now a simple

window.onload =3D function() {
   var form =3D document.forms['formName'];
   form.setAttribute("autocomplete","off");
}

works okay, but patching the taglib to support autocomplete seems a
slightly better idea if it doesn't mean that we'll need to use a
patched version that forks from the main code base (and therefore
updgrading between struts versions will be harder).

I know that autocomplete is a non standard attribute so might not be
accepted as a patch on the taglib. But if it only rendered if
specified then it wouldn't force users to use non standard stuff.

If such a patch is likely to make it into future versions I'll get on it.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org