RE: not render any client specific attributes [was: IE's autocomplete]

2002-11-21 Thread James Mitchell
Gin Chen, is this what you were thinking?

!--Might work with either Map or Collection.--
%
  ArrayList list = new ArrayList();
  list.add(customField1, anything I may need);
  list.add(customField2, other stuff);
  pageContext.setAttribute(customHtml, list);
%

  First Name:html:text property=userFirstName
 customAttrs=customHtml/br

  Last Name:html:text property=userLastName
 customAttrs=customHtml/

would render:

  First Name:input type=text
 name=userName
 customField1=anything I may need
 customField2=other stuffbr

  Last Name:input type=text
 name=userName
 customField1=anything I may need
 customField2=other stuff



--
James Mitchell
Software Engineer/Struts Evangelist
http://www.open-tools.org

If you were plowing a field, which would you rather use? Two strong oxen or
1024 chickens?
- Seymour Cray (1925-1996), father of supercomputing


 -Original Message-
 From: David Graham [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 21, 2002 11:54 AM
 To: [EMAIL PROTECTED]
 Subject: RE: IE's autocomplete


 How would this attributes tag work/look like?  Can you post an example of
 what you're thinking of?

 Dave






 From: Chen, Gin [EMAIL PROTECTED]
 Reply-To: Struts Users Mailing List [EMAIL PROTECTED]
 To: 'Struts Users Mailing List' [EMAIL PROTECTED]
 Subject: RE: IE's autocomplete
 Date: Thu, 21 Nov 2002 11:07:40 -0500
 
 that makes sense.
 but how about including an attributes tag that allows a map of attribute
 name/values?
 that might be helpful while maintaining the whole not render any client
 specific attributes.
 -Tim
 
 -Original Message-
 From: David Graham [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 21, 2002 10:49 AM
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: RE: IE's autocomplete
 
 
 Struts tags will not render any client specific attributes.  The tags
 conform to the HTML 4.01 spec.  The autocomplete attribute is IE specific
 and therefore won't be supported by Struts.  It would be pretty easy to
 extend a Struts tag to support this attribute if you are using IE.
 
 David
 
 
 
 
 
 
  From: edgar [EMAIL PROTECTED]
  Reply-To: [EMAIL PROTECTED]
  To: 'Struts Users Mailing List' [EMAIL PROTECTED]
  Subject: RE: IE's autocomplete
  Date: Thu, 21 Nov 2002 10:20:08 -0500
  
  The tags are pretty simple, I would submit a bug report as an
  ENHANCEMENT with a diff of the changes required to render the attribute.
  
  
  Edgar
  
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
  Sent: Thursday, November 21, 2002 7:50 AM
  To: 'Struts Users Mailing List'
  Subject: RE: IE's autocomplete
  
  
  
  Thanks Robert...
  
  I realise Struts is a server side framework but take the Struts notation
  for say an input box e.g. html:text property=name size=35/ It
  supports the attributes 'alt', 'disabled' and various
  Javascript-specific extensions which are not all supported or rendered
  the same in different browsers... I have read several mails inquiring
  about the same thing, if the 'autocomplete' extension will be accessible
  through Struts in the future... The auotcomplete function is a security
  risk or is percieved as such by many people, it would seem more like
  common sense to cater for it in whatever means possible, even if it
  simply serves to make STRUTS more attractive as a rapid development
  framework for people who are going to use IE to view the application and
  where security is an issue. HTML has a standard way of disabling it,
  e.g. input type=text autocomplete=off ... this is how it's
  disabled in many banking applications etc. where security is a big
  concern...
  
  I'd appreciate any input on this that anyone might have, Thanks, David
  
  
  
  
  
 Robert Taylor
  
 [EMAIL PROTECTED]   To:  Struts Users
  Mailing List [EMAIL PROTECTED]
  cc:
  
 21/11/2002 12:35 Subject: RE: IE's
  autocomplete
 Please respond to
  
 Struts Users Mailing
  
 List
  
  
  
  
  
  
  
  
  David, Struts is a server side framework, and therefore does not
  directly control the behavior of the client. Struts, JSTL, EL, etc...,
  facilitate rendering data in the client. So unless HTML or Javascript
  has a standard way to disable MS IE's *autocomplete* for input forms,
  you are at the mercy of the client.
  
  robert
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 6:24 AM
To: [EMAIL PROTECTED]
Subject: IE's autocomplete
   
   
Hi,
   
I'm trying to get the definitive answer on this, will STRUTS have
functionality to disable MS IE's *autocomplete* for input forms in the
  
near future? Has anyone had experience disabling this by any other
means?
   
Thanks,

RE: not render any client specific attributes [was: IE's autocomplete]

2002-11-21 Thread edgar
I believe this will be in JSP 2.0 as an option in the TLD.

 Mark Roth wrote
 One thing we did notice is that struts tags have a LOT of attributes
:) 
   Many of them simply echo their value straight to HTML.  We've added
a 
 feature to JSP 2.0 called dynamic attributes to help reduce the
number 
 of attributes one needs to declare for a tag.


-Original Message-
From: James Mitchell [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, November 21, 2002 12:45 PM
To: 'Struts Users Mailing List'
Subject: RE: not render any client specific attributes [was: IE's
autocomplete]


Gin Chen, is this what you were thinking?

!--Might work with either Map or Collection.--
%
  ArrayList list = new ArrayList();
  list.add(customField1, anything I may need);
  list.add(customField2, other stuff);
  pageContext.setAttribute(customHtml, list);
%

  First Name:html:text property=userFirstName
 customAttrs=customHtml/br

  Last Name:html:text property=userLastName
 customAttrs=customHtml/

would render:

  First Name:input type=text
 name=userName
 customField1=anything I may need
 customField2=other stuffbr

  Last Name:input type=text
 name=userName
 customField1=anything I may need
 customField2=other stuff



--
James Mitchell
Software Engineer/Struts Evangelist
http://www.open-tools.org

If you were plowing a field, which would you rather use? Two strong
oxen or 1024 chickens?
- Seymour Cray (1925-1996), father of supercomputing


 -Original Message-
 From: David Graham [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 21, 2002 11:54 AM
 To: [EMAIL PROTECTED]
 Subject: RE: IE's autocomplete


 How would this attributes tag work/look like?  Can you post an example

 of what you're thinking of?

 Dave






 From: Chen, Gin [EMAIL PROTECTED]
 Reply-To: Struts Users Mailing List 
 [EMAIL PROTECTED]
 To: 'Struts Users Mailing List' [EMAIL PROTECTED]
 Subject: RE: IE's autocomplete
 Date: Thu, 21 Nov 2002 11:07:40 -0500
 
 that makes sense.
 but how about including an attributes tag that allows a map of 
 attribute name/values? that might be helpful while maintaining the 
 whole not render any client specific attributes.
 -Tim
 
 -Original Message-
 From: David Graham [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 21, 2002 10:49 AM
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: RE: IE's autocomplete
 
 
 Struts tags will not render any client specific attributes.  The tags

 conform to the HTML 4.01 spec.  The autocomplete attribute is IE 
 specific and therefore won't be supported by Struts.  It would be 
 pretty easy to extend a Struts tag to support this attribute if you 
 are using IE.
 
 David
 
 
 
 
 
 
  From: edgar [EMAIL PROTECTED]
  Reply-To: [EMAIL PROTECTED]
  To: 'Struts Users Mailing List' [EMAIL PROTECTED]
  Subject: RE: IE's autocomplete
  Date: Thu, 21 Nov 2002 10:20:08 -0500
  
  The tags are pretty simple, I would submit a bug report as an 
  ENHANCEMENT with a diff of the changes required to render the 
  attribute.
  
  
  Edgar
  
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]
  Sent: Thursday, November 21, 2002 7:50 AM
  To: 'Struts Users Mailing List'
  Subject: RE: IE's autocomplete
  
  
  
  Thanks Robert...
  
  I realise Struts is a server side framework but take the Struts 
  notation for say an input box e.g. html:text property=name 
  size=35/ It supports the attributes 'alt', 'disabled' and 
  various Javascript-specific extensions which are not all supported 
  or rendered the same in different browsers... I have read several 
  mails inquiring about the same thing, if the 'autocomplete' 
  extension will be accessible through Struts in the future... The 
  auotcomplete function is a security risk or is percieved as such by

  many people, it would seem more like common sense to cater for it 
  in whatever means possible, even if it simply serves to make STRUTS

  more attractive as a rapid development framework for people who are

  going to use IE to view the application and where security is an 
  issue. HTML has a standard way of disabling it, e.g. input 
  type=text autocomplete=off ... this is how it's disabled in 
  many banking applications etc. where security is a big concern...
  
  I'd appreciate any input on this that anyone might have, Thanks, 
  David
  
  
  
  
  
 Robert Taylor
  
 [EMAIL PROTECTED]   To:  Struts
Users
  Mailing List [EMAIL PROTECTED]
  cc:
  
 21/11/2002 12:35 Subject: RE: IE's
  autocomplete
 Please respond to
  
 Struts Users Mailing
  
 List
  
  
  
  
  
  
  
  
  David, Struts is a server side framework, and therefore does not 
  directly control the behavior of the client. Struts, JSTL, EL, 
  etc..., facilitate rendering data in the client