[
https://issues.apache.org/jira/browse/MYFACES-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559800#action_12559800
]
Stephen Cunliffe commented on MYFACES-1804:
---
A few notes.
1.) This will affect
[
https://issues.apache.org/jira/browse/TOBAGO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559763#action_12559763
]
Matthias Weßendorf commented on TOBAGO-599:
---
feel free to contribute...
> Netbea
The changes made in trunk of 1.2.6 plugins are necessary to make this
solution work.
I think that the spec is wrong, the component type of HtmlColumnTag
should be javax.faces.HtmlColumn and not
javax.faces.Column. But we need to be according to the spec if we want
a release, so is a fact that the
ah, good.
please do it.
so, we can keep the 1.2.6 plugins, right?
Don't have time to look deeper at it, sorry
-M
On Jan 16, 2008 2:25 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote:
> Hi
>
> Checking one test for h:column headerClass and footerClass (a test for
> see if issue 4 of JSR 252), after
Hi
Checking one test for h:column headerClass and footerClass (a test for
see if issue 4 of JSR 252), after MYFACES-1790
does not work.
The change from javax.faces.HtmlColumn to javax.faces.Column let this
code on shared without effect:
org.apache.myfaces.shared.renderkit.html.HtmlTableRenderer
[
https://issues.apache.org/jira/browse/MYFACES-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-1790.
-
Resolution: Fixed
fixed at revision 612591
> HtmlColumnTag.getComponentType returns th
[
https://issues.apache.org/jira/browse/MYFACES-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559686#action_12559686
]
Leonardo Uribe commented on MYFACES-1790:
-
Hi
Checking one test for h:column hea
demos for showDetail* components missing from demo index
Key: TRINIDAD-903
URL: https://issues.apache.org/jira/browse/TRINIDAD-903
Project: MyFaces Trinidad
Issue Type: Bug
C
skin selector af|selectBooleanRadio:disabled does not work
--
Key: TRINIDAD-902
URL: https://issues.apache.org/jira/browse/TRINIDAD-902
Project: MyFaces Trinidad
Issue Type: Bug
Trinidad demos use deprecated styleClass="AFDataText"
-
Key: TRINIDAD-901
URL: https://issues.apache.org/jira/browse/TRINIDAD-901
Project: MyFaces Trinidad
Issue Type: Bug
Compone
[
https://issues.apache.org/jira/browse/TRINIDAD-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-900.
-
Resolution: Fixed
Fix Version/s: 1.0.6-core
> typo in skin-selectors on
[
https://issues.apache.org/jira/browse/TOBAGO-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559631#action_12559631
]
Guido Dubois commented on TOBAGO-572:
-
Oh, sorry! I tried it this morning with no downl
typo in skin-selectors on af|panelAccordion::title-disabledlink
---
Key: TRINIDAD-900
URL: https://issues.apache.org/jira/browse/TRINIDAD-900
Project: MyFaces Trinidad
Issue Type: B
skinning keys for tr:navigationPane not documented (hint=buttons, choice, list)
---
Key: TRINIDAD-899
URL: https://issues.apache.org/jira/browse/TRINIDAD-899
Project: MyFaces
skinning keys af|input*:readOnly:disabled:content do not work
-
Key: TRINIDAD-898
URL: https://issues.apache.org/jira/browse/TRINIDAD-898
Project: MyFaces Trinidad
Issue Type: Bug
Netbeans 6 plugin
-
Key: TOBAGO-599
URL: https://issues.apache.org/jira/browse/TOBAGO-599
Project: MyFaces Tobago
Issue Type: Wish
Environment: Windows
Reporter: Ricardo S. Tanaka
Create a netbeans 6 pl
[
https://issues.apache.org/jira/browse/TOBAGO-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-598.
-
Resolution: Fixed
> el in labelWidth did not work in tx:* tags
> ---
[
https://issues.apache.org/jira/browse/TRINIDAD-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-893.
-
Resolution: Fixed
Fix Version/s: 1.2.6-plugins
> Added 3 new parameters
el in labelWidth did not work in tx:* tags
---
Key: TOBAGO-598
URL: https://issues.apache.org/jira/browse/TOBAGO-598
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects Vers
Trinidad Table detailStamp flexibility
--
Key: TRINIDAD-897
URL: https://issues.apache.org/jira/browse/TRINIDAD-897
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Components
Af
Change the behavior of range select box to blur after range change
--
Key: TRINIDAD-896
URL: https://issues.apache.org/jira/browse/TRINIDAD-896
Project: MyFaces Trinidad
Issue T
[
https://issues.apache.org/jira/browse/MYFACES-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer updated MYFACES-1804:
Status: Patch Available (was: Open)
> Pressing a download button corrupts other button a
Pressing a download button corrupts other button actions in Internet Explorer
-
Key: MYFACES-1804
URL: https://issues.apache.org/jira/browse/MYFACES-1804
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/TOBAGO-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559454#action_12559454
]
Bernd Bohmann commented on TOBAGO-572:
--
1.0.14-SNAPSHOT from 16.01.08?
> Duplicate co
[
https://issues.apache.org/jira/browse/TOBAGO-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber reopened TOBAGO-505:
-
This fix in LabelExtensionTag breaks use of el expr in labelWidth attribute
eg:
breaks with follo
To clear up some things:
In RI viewRoot.createUniqueId() is unique per request, not per view as
it suggests.
Regards,
Volker
2008/1/16, Volker Weber <[EMAIL PROTECTED]>:
> The id counter in viewRoot.createUniqueId() are resetted (at least in
> RI) on every request.
> If on rerendering a new
The id counter in viewRoot.createUniqueId() are resetted (at least in
RI) on every request.
If on rerendering a new id is requested you get a already, on first
rendering created, existent id.
This is the case e.g. on tab switch, change of rendered attribute, ...
Regards,
Volker
2008/1/16
I'm pretty sure I've read somewhere that user-generated ids should never start
with "_", ie that is reserved only for ids generated by the JSF framework
itself. That means that UIViewRoot.createUniqueId is also an *internal* API
only that should not be called by anything outside the JSF framewor
Hello Volker,
my experience is you should assign uniqueIds to components.
What is the diffence between components created by application from a
tag and inside a component?
If not you get maybe some errors like this:
If this component was created dynamically (i.e. not by a JSP tag) you
should ass
not in MyFaces with JSP. In MyFaces, the uniqueId counter for dynamic
component generation is stored in between requests, and the ids for
components stem from a different counter. I wonder if Facelets uses
the same approach.
regards,
Martin
On 1/16/08, Volker Weber <[EMAIL PROTECTED]> wrote:
> B
Bernd,
i don't know how facelets component creation, rerendering works, but
to my experience the assigning of viewRoot.createUniqueId() ids to
componets created by application wil result in dublicateIdException on
rerendering.
Regards,
Volker
2008/1/15, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
31 matches
Mail list logo
