[
https://issues.apache.org/jira/browse/MYFACES-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799116#action_12799116
]
Jakob Korherr commented on MYFACES-2435:
I know, but spec says that every child
Wrong property name in payload for ajax callback functions
--
Key: MYFACES-2481
URL: https://issues.apache.org/jira/browse/MYFACES-2481
Project: MyFaces Core
Issue Type: Bug
I had the chance to talk to Werner about this issue and he thinks that
the name name was used in an older version of the spec. Created
MYFACES-2481 and provided a patch for this.
- Michael
Michael Kurz schrieb:
Hi,
I found a minor issue with client side error and event handling in the
ajax
hrm,
there was some renaming done; I guess there is no change list on the
spec, right ?
On Tue, Jan 12, 2010 at 12:07 PM, Michael Kurz michi.k...@gmx.at wrote:
I had the chance to talk to Werner about this issue and he thinks that the
name name was used in an older version of the spec.
Found it on the archives of the open mailing list (jsr-314-o...@jcp.org)
Thread is called data payload for ajax calls, started by David Geary.
(some fighting in there, but I don't see a line that indicates a ticket on
their issue tracker)
+1 from me on the change...
-M
On Tue, Jan 12, 2010 at
Use Error instead of Exception in Ajax Js Impl
--
Key: MYFACES-2482
URL: https://issues.apache.org/jira/browse/MYFACES-2482
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
[
https://issues.apache.org/jira/browse/MYFACES-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Kurz updated MYFACES-2482:
--
Status: Patch Available (was: Open)
Use Error instead of Exception in Ajax Js Impl
Change type of the markup attribute from String[] to new class Markup
-
Key: TOBAGO-844
URL: https://issues.apache.org/jira/browse/TOBAGO-844
Project: MyFaces Tobago
Issue
[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799205#action_12799205
]
Carsten Pieper commented on TRINIDAD-37:
Hi, may I inquire about the status of
[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799211#action_12799211
]
Matthias Weßendorf commented on TRINIDAD-37:
can you check if the patch still
[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799224#action_12799224
]
Carsten Pieper commented on TRINIDAD-37:
Ups, I only tested this
[
https://issues.apache.org/jira/browse/MYFACES-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-2435:
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
Assignee: Leonardo Uribe
[
https://issues.apache.org/jira/browse/MYFACES-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-2481:
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
Assignee: Leonardo Uribe
[
https://issues.apache.org/jira/browse/MYFACES-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-2482:
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
Assignee: Leonardo Uribe
[
https://issues.apache.org/jira/browse/TRINIDAD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799282#action_12799282
]
Volker Malzahn commented on TRINIDAD-354:
-
I wonder why this issue is open since
Find a way to allow c:if work with partial state saving enabled
---
Key: MYFACES-2483
URL: https://issues.apache.org/jira/browse/MYFACES-2483
Project: MyFaces Core
Issue Type: Task
Hi,
Thanks for this patch.
I will have to look at the CSS spec to see if this syntax conforms to
other CSS syntaxes. This is what I usually do when I try to come up
with a new skinning api.
Like, is the comma standard, or should it be space-separated? Is the
camel-case standard, or should it
[
https://issues.apache.org/jira/browse/TRINIDAD-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Starets reopened TRINIDAD-1671:
---
Trinidad 2: ppr error when interacting with programatically added component
[
https://issues.apache.org/jira/browse/TRINIDAD-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Starets resolved TRINIDAD-1671.
---
Resolution: Fixed
Fix Version/s: 2.0.1-plugins
The offending code has been in
[
https://issues.apache.org/jira/browse/TRINIDAD-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Starets resolved TRINIDAD-1671.
---
Resolution: Fixed
Fix Version/s: (was: 2.0.1-plugins)
Hi,
Was wondering if it would be possible to package a skin in its own jar file,
so that we wouldn't need to package the skin witht the actual webapp that
uses it, so that we could start having separate modules for skins? it would
make sense for the new Casablanca skin IMHO. What do you think?
[
https://issues.apache.org/jira/browse/MYFACES-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799404#action_12799404
]
Jakob Korherr commented on MYFACES-2435:
OK. good solution.
f:facet can have
Another idea for the syntax comes from the rgb color syntax -
color: rgb(100%, 0%, 0%)
You could use this syntax, and not specify what each of the properties is for:
-tr-include-property:
property("af|foo", "color", "background-color")
or
property(af|foo, color, background-color)
I like this
[
https://issues.apache.org/jira/browse/MYFACES-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr updated MYFACES-2363:
---
Status: Patch Available (was: Open)
ExceptionHandler implementation requires deal with
Hi Jeanne,
Thank you for the answer! Like in the situation of -tr-rule-ref, the list of
properties is comma separated. I don't understand what you mean by
camel-case...The name of the new property can be whatever the user wishes
for. Afterwards, it will be treated like all the other properties in
25 matches
Mail list logo
