My guess is there is some other more specific rule applying to the element,
please see this for more details:
http://www.w3.org/TR/REC-CSS2/cascade.html#specificity
In other words, I suspect that a selector definition like the
following would be more specific and would win:
.anchorlinks.OraLink
According to http://myfaces.apache.org/trinidad/download.html Apache MyFaces
Trinidad 2.0.0 is released.
The Javadoc is still showing version 1.2.x:
http://myfaces.apache.org/trinidad/trinidad-api/apidocs/index.html
In the past version 1.0.x was under a URL like:
I believe that if you are seeing a different browser mode for localhost
vs. machinename then this is either coming from the IE compatibility view
preferences where the user has chosen to run pages from a given domain in
compatibility view or the domain is listed in one of Microsoft's xml files
That generator meta tag is redundant with the comment that can appear at the
bottom of the page and is also listed as one of the types that is not
recommended at http://www.webmarketingnow.com/tips/meta-tags-uncovered.html
I would suggest that it should never be drawn.
However, you would still
This might be the same thing but there is an open issue filed to support the
equivalent of the old 10g ADF Faces skin property af|table{
-ora-repeat-control-bar: true; } for the tr:table tag:
https://issues.apache.org/jira/browse/TRINIDAD-885
If anyone can submit a patch, it would be appreciated.
If you need to support users that use assistive technology (e.g. screen
readers) then be sure to specify summary= on the table element if the
purpose of the table is solely for layout. If it is for a data table then
the summary should describe the nature of the table in 1-3 sentences.
Regards,
in the code, then please feel free to point it
out.
-Anuj
On Tue, Jul 7, 2009 at 9:57 AM, Matt Cooper mcoo...@apache.org wrote:
The behavior described sounds like there might be some invalid HTML on the
page. If you have any other component libraries or any custom HTML in this
page, I would
at all?
-Anuj
On Mon, Jul 13, 2009 at 3:47 PM, Matt Cooper mcoo...@apache.org wrote:
Hi Anuj,
Your test page seems to be okay. In your first email, there is this
style:
display:none
Perhaps either the faces message didn't get assigned to the inputFile
component or maybe the inputFile
The behavior described sounds like there might be some invalid HTML on the
page. If you have any other component libraries or any custom HTML in this
page, I would recommend trying to remove them temporarily to isolate the
problem. If certain pieces of the page are not showing up but their
Hi Jan,
In CSS, the selectors are ranked such that the most specific style will take
precidence over a lesser-specific style. It isn't just the order in which
the selectors appear in the CSS file (that only counts if the selectors have
equal specificity). There are many different factors that
Hi Marco,
Actually I think RowLayoutRenderer just needs to perform the
UIXComponent.processFlattenedChildren() just like is done in
PanelFormLayoutRenderer to supports component flattening. This would give
you that effect that you desire but also will flatten a tr:iterator
wrappers.
Regards,
On Fri, Mar 6, 2009 at 8:34 AM, Matt Cooper mcoo...@apache.org wrote:
Hi Marco,
Actually I think RowLayoutRenderer just needs to perform the
UIXComponent.processFlattenedChildren() just like is done in
PanelFormLayoutRenderer to supports component flattening. This would give
you that effect
Hi Lars,
If you view the page source, you can see what the active skin is.
For example if you go to:
http://www.irian.at/trinidad-demo/faces/index.jspx
it shows the following at the bottom of the page's source:
!--Created by Apache Trinidad (Apache MyFaces Trinidad API -
1.0.8-SNAPSHOT/Apache
/skin/Skin.htmlobject:
RenderingContext.getCurrentInstance().getSkin();
From that you can get the skin family or skin ID.
Regards,
Matt
On Tue, Feb 24, 2009 at 9:22 AM, Matt Cooper mcoo...@apache.org wrote:
Hi Lars,
If you view the page source, you can see what the active skin is.
For example
I imagine that your Java code will look something like this (do this
for each showDetailItem in the panelTabbed):
FacesBean facesBean = showDetailItem.getFacesBean();
FacesBean.Type type = facesBean.getType();
PropertyKey disclosedKey = type.findKey(disclosed);
if
Hi,
The panelFormLayout arranges children top-to-bottom one column at a
time--this is also how the browser will handle tab ordering between
the fields.
If you still wanted the effective visual positioning to match what you
desired, you could have your component tags like this:
panelFormLayout
This is because the tr:panelHorizontalLayout is getting in the way.
The labelAlignment will only apply to inputs that are direct children
of the panelFormLayout. If you want to force 2 columns of inputs, you
can also set rows=1 maxColumns=2 on the panelFormLayout.
Regards,
Matt
On Thu, Oct 2,
I think using a custom skin would be more robust. I wonder if
defining a skin extension with the following definition would be
sufficient:
af|inputText:error::content {
background-color: red;
}
This definition means that the the background-color applies to the
internal psuedo-element named
Probably the simplest component would be panelGroupLayout
layout=default. Though, perhaps the trh taglib should have a tr:div
component added to it?
Regards,
Matt
On Mon, Jul 21, 2008 at 6:33 AM, Daniel Niklas [EMAIL PROTECTED] wrote:
Hi Mathias,
Mathias Walter wrote:
could you find a
Hi Bill,
I could be wrong but I don't believe the tr:selectOneRadio accepts
children that produce DOM. Also, the trh:rowLayout must be inside of
a trh:tableLayout.
Instead of using tr:selectOneRadio, you may want to use multiple
tr:selectBooleanRadio components. The selectBooleanRadio is more
!
On 6/6/08, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Dear MyFaces community,
please welcome our new MyFaces PMC member Matt Cooper.
Matt is working on the Apache MyFaces and Trinidad stuff.
Therefore last week there was a vote to invite him to the MyFaces
Project Management
For this to work, the tr:selectOneChoice renderer would need to be
enhanced to support processing of flattened children. The iterator
actually shows up as a child component during rendering and the
selectOneChoice component doesn't know what to do with an iterator
child.
An alternative to using
tag. I am
wondering if trinicad dropped tr:forEach? But, it is still in the
document.
thanks
Bill
On Tue, Jun 3, 2008 at 4:32 PM, Matt Cooper [EMAIL PROTECTED] wrote:
For this to work, the tr:selectOneChoice renderer would need to be
enhanced to support processing of flattened children
Off the top of my head, the only ones I've seen used browser plug-ins
to perform the upload rather than input type=file. I don't recall
ever seeing any using open standards-based mechanisms. In any case, I
think this type of functionality would be quite useful if added.
Regards,
Matt
On Fri,
This is the intended implementation, inlineStyle and styleClass should
be applied to the root element of the component. If it becomes common
additional style or class attributes can be added. For example, there
is a contentStyle attribute that would apply to the inner input
element.
For your
Hi Martin,
I'm not sure if this is exactly the problem you are running into but
one thought might be to wrap the input component that you want to PPR
inside of a panelLabelAndMessage (and setting simple=true on the
input component). This way the input becomes stand-alone and PPR-able
whereas
Hi Shawn,
I think I have run into this same problem. When the disclosure changes, the
locally-stored property for disclosed changes from a value expression to a
boolean--the expression disappears once the system has overwritten it with a
boolean value as a result of a manual disclosure change.
. Are you also using XmlMenuModel with Trinidad or do
you have the menus configured in managed beans in faces-config.xml.
-Richard
On 1/2/08, Matt Cooper [EMAIL PROTECTED] wrote:
Hi Richard,
I believe the answer is that startDepth and level are almost the same.
There is one subtle
I am confused, how does your email pertain to Apache MyFaces? I would
recommend that you post your question to the A4J board instead.
Regards,
Matt
On 10/16/07, bansi [EMAIL PROTECTED] wrote:
I have a situation where reRender attribute reRenders the whole form. Here
is
the snippet
Hi Nate,
If you are trying to PPR the panelButtonBar components directly, it will not
work when rendered was set to false. In order to PPR something, it must be
already rendered. Instead, either PPR the parent of the panelButtonBar
components, the panelHeader, or wrap the two panelButtonBar
copies of the original message*.
--
*From:* Matt Cooper [mailto:[EMAIL PROTECTED]
*Sent:* Monday, October 08, 2007 2:26 PM
*To:* MyFaces Discussion
*Subject:* Re: [Trinidad] PPR problem
Hi Nate,
If you are trying to PPR the panelButtonBar components directly
of the original message*.
--
*From:* Matt Cooper [mailto:[EMAIL PROTECTED]
*Sent:* Monday, October 08, 2007 2:49 PM
*To:* MyFaces Discussion
*Subject:* Re: [Trinidad] PPR problem
The subform is a NamingContainer so the problem could be issues with the
expressions
Oh, and one other tip is to try reproducing the problem using a very simple
test case. This will sometimes help to narrow down and identify the
problem.
On 10/8/07, Matt Cooper [EMAIL PROTECTED] wrote:
Hmm... that looks correct to me too. I don't know what else might be
causing the problem
The easiest thing might be to see if it reproduces in a very simple hello
world page. If the problem reproduces then it might be work verifying that
the .js files listed in the page source do load script as expected (put
those URLs in your browser's address bar). If the problem doesn't reproduce
The other thing you can look into is using Firebug Lite which you can use
with IE but requires a change to your JSP to insert its script... more
details here:
http://www.getfirebug.com/lite.html
On 9/13/07, Matt Cooper [EMAIL PROTECTED] wrote:
The easiest thing might be to see if it reproduces
there who
will have used this parameter already. Have fun answering their mails
;))
regards,
Martin
On 9/5/07, Matt Cooper [EMAIL PROTECTED] wrote:
I agree with Adam.
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
The old parameter was trinidadinternal
If possible, I would suggest swapping the order of the tr:panelFormLayout
and tr:subform tags. That should correct the invalid HTML problems since I
suspect the inputText components are expecting to be direct children of the
panelFormLayout.
Thank you,
Matt
On 9/6/07, Vadim Dmitriev [EMAIL
I agree with Adam.
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
The old parameter was trinidadinternal, and therefore was
never officially supported. If we were changing from one
supported name to another, I'd agree that we should keep the
old name around, but supporting backwards
I like that name too. Should the text for it be text like on other
components or caption?
Regarding this example mentioned earlier:
tr:panelFormLayout
tr:panelCaptionGroup caption=Personal Details
tr:inputText.../
/tr:panelCaptionGroup
/tr:panelFormLayout
this could potentially be
I haven't tested this but I believe this should be valid:
tr:inputText styleClass=inputStyle1 label=I a bold label value=test/
tr:inputText styleClass=inputStyle2 label=I a non-bold label
value=test/
af|inputText.inputStyle1 af|inputText::label {
font-weight: bold;
}
As long as the styleClass
Hi Jeanne,
This looks great!
Do you think we need to call out that *-tr-inhibit* will only perform
server-side inhibiting; it will not inhibit styles that resolve in the
browser bases on things like selector specificity.
Thank you,
Matt
On 8/22/07, Jeanne Waldman [EMAIL PROTECTED] wrote:
Hi
in the browser will not be inhibited.
However, if examples are easier to understand (as seen above), then let's
put them in.
Thanks,
Matt
On 8/22/07, Jeanne Waldman [EMAIL PROTECTED] wrote:
Hi Matt,
Can you elaborate so I'm sure what you are saying?
Thanks,
Jeanne
Matt Cooper wrote:
Hi
Hi Andrew,
A few things you might try... specify quotes around the path in your URL and
perhaps specify width/height dimensions, e.g.:
.AFFindIcon {
content: url(/skins/standard/images/icon_find_sml.png);
width: 16px;
height: 16px;
}
If this still doesn't work, there might be a syntax
Hi Andrew,
Since styleClass applies to the root element of a component, your
definitions could be something like this:
.CustomStyleClass.af|myComponent {
/* styles for the root element */
}
.CustomStyleClass.af|myComponent af|myComponent::sub-element {
/* styles for the sub element */
}
Hi Kevin,
I believe the breadCrumb component displays current path down the hierarchy
of the MenuModel. It does not replicate the browser history from your back
button's menu.
Regards,
Matt
On 7/25/07, Kevin R. Gutch [EMAIL PROTECTED] wrote:
Ok Thanks for the information!
Simon Lessard
Hi Carsten,
To help debug the issue, you can assign background-color values in the
tr:panelGroupLayout to ensure that it is stretched vertically as you
desire. I don't believe you can stretch a tr:panelGroupLayout
layout=horizontal reliably across web browsers because the horizontal
layout for
for one
example.
Is there really NO documentation at all for this? ADF at least had
adf-skins-doc.xml that I used. I will file a JIRA, as you say, if that's
the way it is.
Thanks
Dan
--
*From:* Matt Cooper [mailto:[EMAIL PROTECTED]
*Sent:* Monday, June 11, 2007
Hi Chris,
Not sure if this is exactly what you want but but for each cell, you could
have 2 lines of data, e.g.:
tr:panelGroupLayout layout=vertical
tr:outputText value=#{row.columnALine1}/
tr:outputText value=#{row.columnALine2}/
/tr:panelGroupLayout
Regards,
Matt
On 6/12/07, Chris Hane
record summary.. |
I put the hard breaks between rows for visual effect only. In the
application, they are not there - highlighting is used instead.
Thanks,
Chris
Matt Cooper wrote:
Hi Chris,
Not sure if this is exactly what you want but but for each cell, you
could have 2 lines of data, e.g
Hi Dan,
I'm not sure what the selectors for that component are off-hand but one
handy procedure I can share with you (what I frequently use to make sure I
am skinning things correctly) is to *temporarily* add the following
(unsupported) entry in my web.xml file:
context-param
50 matches
Mail list logo
