Muralidhar Y. wrote:
Why value is not a reserved parameter is as following :-
One of the most imp point is that tapestry html pages can be directly opened
in the browser and can give the same look and feel as they are seen when
deployed.
But if you declare value as reserved parameter html developers cannot use
value parameter when writing html . So thet cannot customise the text on the
submit button.
Yes they can, but they can only use a hard coded value in the value,
not, say, an OGNL expression. If the value needs to be dynamic (e.g.
i18n'ed), it must be stated in the page specification if the "value"
attribute was reserved.
In your case if there are 2 value parameters in html it should not be a
problem. Html takes what ever the first occurrence is. And all tapestry
components make sure that their parameters occur first than what had written
in html by html developers.
Yes, it's a problem, two "value" attributes is not valid (X)HTML.
I'll just stick to my custom component that reserves the "value" parameter.
Best wishes,
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
