[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212453#comment-13212453
]
Stephen Friedrich commented on TRINIDAD-875:
Sorry, I have left first
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774912#action_12774912
]
Stephen Friedrich commented on TRINIDAD-875:
Happens to me with latest FF2
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774920#action_12774920
]
Stephen Friedrich commented on TRINIDAD-875:
Same problem occurs using Opera
[
https://issues.apache.org/jira/browse/TRINIDAD-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771614#action_12771614
]
Stephen Friedrich commented on TRINIDAD-1071:
-
I am back to Trinidad after
My 2 cents: Don't load classes to use java.lang.reflect on it:
- What if a class does something bad (or just about anything) in a static
initializer?
For example try to run the code below. It will EXIT THE VM
- Can you be sure that those classes are unloaded again?
- Performance: It is
The JSF spec is actually quite readable and explicitly highlights differences
to the 1.1 version.
Out of my head:
A single major change: Unified EL
Lots of small changes.
Naik, Bhushan wrote:
Hi All,
We are planning to upgrade the JSF version to 1.2. Do we have
some document for
Normally objects in the JSF component tree (ie the current view) are
never stored in the http session. Instead, the JSF implementation takes
Hm, since this is the myfaces mailing list, I'd like to point out that
Trinidad has a configuration parameter
[
https://issues.apache.org/jira/browse/TRINIDAD-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628445#action_12628445
]
Stephen Friedrich commented on TRINIDAD-1215:
-
Now that you mentioned it, I
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626468#action_12626468
]
Stephen Friedrich commented on TRINIDAD-1195:
-
Thanks Matthias for caring
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626480#action_12626480
]
Stephen Friedrich commented on TRINIDAD-1195:
-
entered 1 and got an error
Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.2.9-core
Reporter: Stephen Friedrich
Title says it all:
When a disabled text field contains some text, then some PPR action sets
disabled=false on that field, then the field losses its value.
All
Components: Components
Affects Versions: 1.2.9-core
Reporter: Stephen Friedrich
When a tr:inputText is switched from required=true to required=false using
PPR, then the required icon is correctly removed, but validation still fails if
the inputText is empty.
See TRINIDAD-1130
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626484#action_12626484
]
Stephen Friedrich commented on TRINIDAD-1195:
-
Thanks Matthias, I created
[
https://issues.apache.org/jira/browse/TRINIDAD-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626490#action_12626490
]
Stephen Friedrich commented on TRINIDAD-1198:
-
So?
The valueChangeListener
[
https://issues.apache.org/jira/browse/TRINIDAD-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626495#action_12626495
]
Stephen Friedrich commented on TRINIDAD-1198:
-
Ah, sorry, JSF is in fact
[
https://issues.apache.org/jira/browse/TRINIDAD-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626724#action_12626724
]
Stephen Friedrich commented on TRINIDAD-1198:
-
Yes, like I said this isn't
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626100#action_12626100
]
Stephen Friedrich commented on TRINIDAD-1195:
-
No, this is not a seam issue
[
https://issues.apache.org/jira/browse/TRINIDAD-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625854#action_12625854
]
Stephen Friedrich commented on TRINIDAD-755:
Just in case somebody needs
Reporter: Stephen Friedrich
When a tr:selectBooleanCheckbox is placed into a panelFormLayout the label and
checkbox are not vertically aligned (the checkbox's message cell is always
visible, so that the checkbox is about 10px too high).
See TRINIDAD-1130 for an example application
[
https://issues.apache.org/jira/browse/TRINIDAD-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12624828#action_12624828
]
Stephen Friedrich commented on TRINIDAD-1091:
-
Knock. Knock. The patch adds
[
https://issues.apache.org/jira/browse/TRINIDAD-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12621449#action_12621449
]
Stephen Friedrich commented on TRINIDAD-65:
---
Not fixed in 1.2.9
Using
[
https://issues.apache.org/jira/browse/TRINIDAD-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12621467#action_12621467
]
Stephen Friedrich commented on TRINIDAD-65:
---
Thanks Matthias for the quick
I agree that this is useful, but should _not_ be in core.
It's nothing new, however, the Seam framework has a nice, robust
implementation of a very similar feature:
http://docs.jboss.com/seam/2.1.0.A1/reference/en/html/events.html#d0e4418
If you choose to copy that effort, please make sure that
Reporter: Stephen Friedrich
An action set on an ItemNode is evaluated as a value expression.
Workround is to have a getter instead of an action-method-signature in the
backing bean:
public String getDoIt()
for an itemNode like this:
itemNode id=companies action=#{_companyList.doIt}
label
/browse/TRINIDAD-1131
Project: MyFaces Trinidad
Issue Type: Improvement
Reporter: Stephen Friedrich
Priority: Minor
With this setting in trinidad-config.xml
!-- Improve a4j compatibility --
accessibility-modeinaccessible/accessibility-mode
[
https://issues.apache.org/jira/browse/TRINIDAD-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607183#action_12607183
]
Stephen Friedrich commented on TRINIDAD-695:
Matthias, really sorry
Versions: 1.2.8-core
Reporter: Stephen Friedrich
Attachments: escape.png
selectOneRadio always escapes every option. However SelectItem has an escape
attribute that should be honored.
(Have to check the other tags based on SelectItems, too.)
If a committer is willing to review
[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607072#action_12607072
]
Stephen Friedrich commented on TRINIDAD-1129:
-
I don't know what exactly you
[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607073#action_12607073
]
Stephen Friedrich commented on TRINIDAD-1129:
-
Regarding
[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607035#action_12607035
]
Stephen Friedrich commented on TRINIDAD-1129:
-
Nope. Does not work for me
PPR on inputText required and disabled
--
Key: TRINIDAD-1130
URL: https://issues.apache.org/jira/browse/TRINIDAD-1130
Project: MyFaces Trinidad
Issue Type: Bug
Reporter: Stephen Friedrich
Issue Type: Bug
Affects Versions: 1.2.8-core
Reporter: Stephen Friedrich
tr:validateLength (and very probably other Trinidad validator also) do not
validate anything on the server side at all.
Trinidad's org.apache.myfaces.trinidad.validator.LengthValidator is a subclass
[
https://issues.apache.org/jira/browse/TRINIDAD-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606352#action_12606352
]
Stephen Friedrich commented on TRINIDAD-917:
What's even worse: Client-side
[
https://issues.apache.org/jira/browse/TRINIDAD-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606371#action_12606371
]
Stephen Friedrich commented on TRINIDAD-695:
Arg%§$°
I keep hitting bug
Type: Bug
Affects Versions: 1.2.7-core
Reporter: Stephen Friedrich
This skinning selector used to work for tr:selectManyShuttle
.AFShuttleMoveIcon:alias {
content: url(/images/icons_right.gif);
width: 15px;
height: 15px;
}
In Trinidad 1.2.7 I don't get any icon at all
[
https://issues.apache.org/jira/browse/TRINIDAD-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598345#action_12598345
]
Stephen Friedrich commented on TRINIDAD-462:
Any update on this?
My skin file
Jeanne Waldman wrote:
What's the JIRA number?
What exactly are your requirements? I wouldn't over-design it by putting
in too many hooks.
- Jeanne
Here's the Jira issue:
https://issues.apache.org/jira/browse/TRINIDAD-755
Any yes, it is more complicated than it feels it should be.
We
Blake Sullivan wrote:
Stephen Friedrich said the following On 4/13/2008 11:26 PM PT:
Blake, in general you point of view is a very theoretical one from a high
ebony tower. Do you say so in english? ;-)
In English, it is usually ivory tower, but, if you think that I'm
evil, ebony tower might
Blake, in general you point of view is a very theoretical one from a high
ebony tower. Do you say so in english? ;-)
In real life those private methods do make using Trinidad more cumbersome
that it needs to be.
For example it is currently not possible to make a simple change like moving
*
simply have to add to their skin something like:
.AFLabelPosition:alias { -tr-before-label: false }
And then the renderers of labels would check this skin property when
they are rendering the label,
and render it either in front or behind.
- Jeanne
Stephen Friedrich wrote, On 4/13/2008 11:26
[
https://issues.apache.org/jira/browse/TRINIDAD-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569566#action_12569566
]
Stephen Friedrich commented on TRINIDAD-885:
Also a problem for me. I have
[
https://issues.apache.org/jira/browse/TRINIDAD-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569567#action_12569567
]
Stephen Friedrich commented on TRINIDAD-944:
Also: Sort icon position
[
https://issues.apache.org/jira/browse/TRINIDAD-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568214#action_12568214
]
Stephen Friedrich commented on TRINIDAD-656:
Any updates on this? Seems like
where did you got the Trinidad ?
-M
On Feb 10, 2008 1:21 AM, Stephen Friedrich [EMAIL PROTECTED] wrote:
Completely removing my maven repository did not help, even after mvn clean
install.
Strangely what worked is this:
In trinidad-impl sub-folder do mvn clean install, then in root folder try
?
Stephen Friedrich wrote:
My naive approach was to checkout trunk, then do mvn install.
However the build process fails when compiling the tests for impl:
[INFO] Compiling 45 source files to
C:\java\trinidad-svn\trinidad-impl\target\test-classes
[INFO
My naive approach was to checkout trunk, then do mvn install.
However the build process fails when compiling the tests for impl:
[INFO] Compiling 45 source files to
C:\java\trinidad-svn\trinidad-impl\target\test-classes
[INFO]
: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.0.4-core
Reporter: Stephen Friedrich
Priority: Minor
If I specify the unselectedLabel attribute of tr:selectOneChoice, then that
label always displays in the list, even if a selection has been made
[
https://issues.apache.org/jira/browse/TRINIDAD-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550971
]
Stephen Friedrich commented on TRINIDAD-865:
There was a lively discussion on the mailing list
I just checked out trunk, and tried mvn install
That results in a lot of compile errors on Trinidad Impl.
First one is this:
C:\java\trinidad-svn\trinidad\trinidad-impl\src\test\java\org\apache\myfaces\trinidadinternal\renderkit\ComponentDefinition.java:[31,54]
package
[
https://issues.apache.org/jira/browse/TRINIDAD-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543671
]
Stephen Friedrich commented on TRINIDAD-359:
Bug in very basic feature, priority Major, open for more
: Stephen Friedrich
My client's styleguide mandates 15px gap between buttons.
When I did not find anything in the skin selectors doc at first I thought the
doc was just missing.
When I inspected my page with Firebug I saw that a spacer image was hardcoded
with 10px width and thought
Thanks for your answer, Adam.
I'll try to be more careful in keeping formatting and not changing unrelated
code. I am just so used to act on Idea's inspection warning's to keep the code
status green.
I'll provide some separate patches to clean up the code a little:
Unused imports, missorted
[
https://issues.apache.org/jira/browse/TRINIDAD-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534235
]
Stephen Friedrich commented on TRINIDAD-755:
When I started I hoped for just a few tweaks in the code
[
https://issues.apache.org/jira/browse/MYFACES-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533477
]
Stephen Friedrich commented on MYFACES-1733:
Hm, I don't know JSF internals as well as you, but I just
Trinidad
Issue Type: Bug
Affects Versions: 1.0.3-core
Reporter: Stephen Friedrich
Currently __getIndex() throws an exception if the submittedValue is not in the
list of select items, or is not a number.
That code is annotated with // TODO Don't throw exception: message
Feature
Components: Skinning
Affects Versions: 1.0.3-core
Reporter: Stephen Friedrich
Currently Trinidad always shows icon and text of a label in this order:
message-icon required-.icon text
It should be able to specify a different order in the skin.
--
This message
[
https://issues.apache.org/jira/browse/TRINIDAD-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Friedrich updated TRINIDAD-755:
---
Status: Patch Available (was: Open)
Positions of required and message label
, not per component. There's no
strict rule though. About the name, maybe -tr-required-icon-position?
~ Simon
On 10/1/07, *Stephen Friedrich* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I have just changed the OutputLabelRenderer to optionally render
the required icon _after_
I just did an update and tried to build:
Also getting a compile error in ChildPropertyTreeModel.
If I locally rollback that file to the previous revision, then
mvn clean install
works fine, though. No test failures.
Simon Lessard wrote:
Hi all,
I cannot build the current Trinidad trunk. The
PPR does not R: Table rows are not refreshed
Key: TRINIDAD-750
URL: https://issues.apache.org/jira/browse/TRINIDAD-750
Project: MyFaces Trinidad
Issue Type: Bug
Reporter: Stephen
[
https://issues.apache.org/jira/browse/TRINIDAD-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531642
]
Stephen Friedrich commented on TRINIDAD-750:
No Jira macors enabled?!
PPR does not R: Table rows
[
https://issues.apache.org/jira/browse/TRINIDAD-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531654
]
Stephen Friedrich commented on TRINIDAD-750:
After further research: It is not caused by PPR
I have just changed the OutputLabelRenderer to optionally render
the required icon _after_ the label.
How should I implement skinning for that?
(Currently I check a system property, that I set in my test code.)
What is the practical difference between defining a new skinning
property vs. a
: 1.0.3-core
Reporter: Stephen Friedrich
My app has some fields where it isn't useful to have the browser remember and
try to auto complete values.
In HTML you can switch that off with the non-standard autocomplete attribute.
JSF 1.2 also added the same attribute, but Trinidad
[
https://issues.apache.org/jira/browse/MYFACES-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530948
]
Stephen Friedrich commented on MYFACES-1733:
It may well be that it is only Seam that triggers the bug
Reporter: Stephen Friedrich
Sometimes when using server-side state-saving some state is fixed and won't
ever update.
I don't know how exactly this is caused, but it occurs a lot when using JBoss
Seam.
It is consensus in the Seam community not to ever use myfaces with server-side
state
66 matches
Mail list logo