When you have a big screen with many detail-regions, I think that it is
more natural for a user to fill out each region one at a time and to be
able to fold/unfold each region without triggering validation. Only when
you're ready filling in each field of this page and when you submit the
On 7/3/07, Henk Vanhoe [EMAIL PROTECTED] wrote:
When you have a big screen with many detail-regions, I think that it is
more natural for a user to fill out each region one at a time and to be
able to fold/unfold each region without triggering validation. Only when
you're ready filling in each
Now it works without problems, thank you!
I already feared that the original behavior is the expected behaviour.
However, I still think that it would be handy to have a detail
functionality where it is possible to fold/unfold the detail without
triggering validation and still being able to
A major concern is:
- Required field is present in the detail
- User collapses with the required field blank
- Submit, and we show an error that the required
field is empty - but the user can't see the field that
has the error!
What's the concern with leaving immediate=false
on the table?
--
BTW, to be clear: the original behavior, where contents
are not submitted with the details are closed, is
currently not a bug - set immediate to false (the default).
What I fixed was the issue where the contents were
showing up blank, which was a bug that would
affect any use of nested
On 6/22/07, Henk Vanhoe [EMAIL PROTECTED] wrote:
Finally, I have found some time to make a testproject where this problem
(bug?) can be duplicated...
There is a jsp in this project
(/detailstamptest/faces/table/changeTable.jspx) which consists of a
table with one element. Next to this element
I've filed the detailStamp bug as:
http://issues.apache.org/jira/browse/TRINIDAD-75
It repros in the Trinidad demo bundle too.
-- Adam
On 6/25/07, Adam Winer [EMAIL PROTECTED] wrote:
On 6/22/07, Henk Vanhoe [EMAIL PROTECTED] wrote:
Finally, I have found some time to make a testproject
OK, the detailStamp bug is fixed.
-- Adam
On 6/25/07, Adam Winer [EMAIL PROTECTED] wrote:
I've filed the detailStamp bug as:
http://issues.apache.org/jira/browse/TRINIDAD-75
It repros in the Trinidad demo bundle too.
-- Adam
On 6/25/07, Adam Winer [EMAIL PROTECTED] wrote:
On 6/22/07,
Finally, I have found some time to make a testproject where this problem
(bug?) can be duplicated...
There is a jsp in this project
(/detailstamptest/faces/table/changeTable.jspx) which consists of a
table with one element. Next to this element there is a 'Show detail'
link. When you click
I have tested this problem again with the latest trinidad from the svn
repository, and now the test results are a little bit different...
When I use CLIENT_STATE_METHOD 'all', it doesn't work anymore and I'm
having this exception message (without stacktrace) when I click on a
'Show detail'
Hi,
I am using an editable table inside a detailstamp facet. The data in the
table comes from a request-scoped managed bean. As I want to avoid
session scoped beans, I use the tomahawk savestate tag to save the state
of my beans. Everything works fine, except that when I change something
in
11 matches
Mail list logo
