org.apache.myfaces.trinidadinternal.config.upload.FileUploadConfiguratorImpl
beginRequest ; java.io.EOFException: Per-request disk space limits
exceeded.
CSS Class for sheet header and cell filler
---
Key: TOBAGO-808
URL: https://issues.apache.org/jira/browse/TOBAGO-808
Project: MyFaces Tobago
Issue Type: Improvement
Components: Themes
[
https://issues.apache.org/jira/browse/TOBAGO-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-796.
-
Resolution: Fixed
Fix Version/s: 1.0.24
tobago blocks on error in onComplete javascript
[
https://issues.apache.org/jira/browse/TOBAGO-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-792.
--
Resolution: Fixed
SimpleSheet should store scroll position
[
https://issues.apache.org/jira/browse/TOBAGO-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-808.
--
Resolution: Fixed
CSS Class for sheet header and cell filler
[
https://issues.apache.org/jira/browse/TOBAGO-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770088#action_12770088
]
Sven Bunge commented on TOBAGO-802:
---
The code
new SelectItem( , null);
doesn't throw
Just curious, what does everyone think about including ARIA
(http://www.w3.org/TR/wai-aria/) accessibility support in 2.0?
Thanks,
Curtiss Howard
Actually, I just thought of why we wouldn't be able to include ARIA
support in the MyFaces implementation of the standard HTML taglib...
because it's not a requirement in the JSF 2.0 spec. So obviously
that's out.
Given that... let me pose this question another way... what about
including the
[
https://issues.apache.org/jira/browse/MYFACES-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770120#action_12770120
]
Leonardo Uribe commented on MYFACES-2216:
-
It seems to be a misunderstanding
[
https://issues.apache.org/jira/browse/MYFACES-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2216.
-
Resolution: Fixed
Fix Version/s: 1.2.8-SNAPSHOT
MyFaces suppresses runtime
Well, we might be able to do some stuff within the boundaries of the
JSF specification, but I'm afraid the possibilities are limited... (am
I saying without in-depth ARIA knowledge)
On my current project, we had to be very strict with accessibility,
but AFAICS, the end user is happy with every
Hi
While implementing the new attributes of f:selectItems (var, itemValue,
itemLabel, ...) I got stuck at the last one.
The problem is that the mojarra javadoc lists itemLabelEscaped twice, but
with two totally different descriptions. Looking at the example in the
description of value, I found
unmappable character for encoding UTF8 warning causes maven build to fail
-
Key: TRINIDAD-1609
URL: https://issues.apache.org/jira/browse/TRINIDAD-1609
Project: MyFaces Trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Starets updated TRINIDAD-1609:
--
Status: Patch Available (was: Open)
unmappable character for encoding UTF8 warning causes
[
https://issues.apache.org/jira/browse/TRINIDAD-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1609:
-
Resolution: Fixed
Fix Version/s: 2.0.0-core
Assignee: Matthias
Hi,
in order to avoid dependency to h:head/body/form BUT be able to
support the Relocatable Resources feature, we should change our
renderers for head, body and form to check
for any component resource(s) that has been targeted to one of these guys.
This would mean that something like this just
oh, yeah... of course this can only work when we change our
UIXComponentBase's setParent() to trigger the new PostAddToViewEvent
event.
A simple implementation of the setParent() is available here:
[
https://issues.apache.org/jira/browse/TRINIDAD-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1608.
--
Resolution: Invalid
this is the exact expected behavior...
Take a look
clean up the UIComponentBase.setParent()
Key: MYFACES-2389
URL: https://issues.apache.org/jira/browse/MYFACES-2389
Project: MyFaces Core
Issue Type: Improvement
Affects Versions: 2.0.0-alpha
Hi,
some of the hidden secrets of the new spec have been forgotten to be
spec'd out :-(
While checking on MyFaces's setParent() implementation, I decided to
do a little clean up.
Please see the patch here:
https://issues.apache.org/jira/browse/MYFACES-2389
Generally I am wondering about the
Hi Matthias,
that has not been discussed on the EG, so I can't confirm your version
of the code. However, it seems reasonable to me. As I see from the
issue tracker, Ed already responded (he's been faster there than with
other MyFaces team issues recently ;), so I guess there is no need for
Hi Jan-Kees,
for now, our last ressort ist code duplication. For the future, you
should file an issue against the spec, I would say.
regards,
Martin
On 10/25/09, Jan-Kees van Andel jankeesvanan...@gmail.com wrote:
Hey (CC MyFaces Dev),
For MyFaces, I have implemented the first version of
[
https://issues.apache.org/jira/browse/TRINIDAD-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770388#action_12770388
]
Agam Dass commented on TRINIDAD-1550:
-
I think this change was done to preserve the
23 matches
Mail list logo
