-1

I guess I started this by marking the associated bug report invalid, and
adding the comments I received privately from the original reporter.

The reasons I am -1 on this are:

1) The attributes for which this has been suggested are not valid per the
W3C standards. I do not believe that Struts should be catering to
non-standard solutions. Yes, I realise that some browsers support
"extensions" to the standard. However, suppose that attribute 'foo',
currently supported by browser X, is eventually standardised such that the
standard values are not consistent with what browser X supported. What
should we do now?
2) name collisions
3) syntax validation
4) duplication
5) XHTML (need to ignore when value is set)


----- Original Message -----
From: "Arron Bates" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, December 09, 2001 11:27 PM
Subject: Freetext attribute for all tags...


> Idea...
>
> There was just that too and fro in "additional properties needed on
> html:image..." bug in that there was the argument over what to support
> and what not to support... if there was a standard property (ie:
> "freetext", "freeform", "uglytext" or something) where developers could
> add a string to be included in the tag as they provide it (with an extra
> space at the front and back to avoid collisions).
>
> If a developer wants to include something to be rendered for one reason
> or another, Struts not supporting it or otherwise, they can without
> issue and code hacks that will have to be re-done the next version of
> the tag, tld etc...
>
> It means that the html:image and html:text can do whatever and the
> developer can still get the width, height and wrap stuff that he needs
> for nice formatting.
>
> Probably not *proper* for all the die -hards out there... but certainly
> useable, especially for html creatives that seek that extra level of
> control that Struts hasn't been around yet, doesn't want to or whatever.
>
> Just an idea.
>
>
> Arron.
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to