[jira] Updated: (TRINIDAD-1060) update tagdoc for RowDisclosureEvent
[ https://issues.apache.org/jira/browse/TRINIDAD-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-1060: -- Status: Patch Available (was: Open) > update tagdoc for RowDisclosureEvent > > > Key: TRINIDAD-1060 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1060 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Documentation >Affects Versions: 1.2.7-core >Reporter: Sandy Schaffner >Priority: Minor > Attachments: RowDisclosure.xml > > > In the Events section, for > org.apache.myfaces.trinidad.event.RowDisclosureEvent it says "The Expansion > event is generated when tree nodes are expanded or collapsed." > change to: "The Expansion event is generated when detail facet for the rows > are expanded or collapsed." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1075) default attribute on subform tagdoc needs clarification
default attribute on subform tagdoc needs clarification --- Key: TRINIDAD-1075 URL: https://issues.apache.org/jira/browse/TRINIDAD-1075 Project: MyFaces Trinidad Issue Type: Bug Components: Documentation Affects Versions: 1.2.7-core Reporter: Sandy Schaffner Priority: Minor 1. Update tag doc on default from: "whether the subform should assume it has been submitted. When set to "default", "submitted" will be considered true if no other subform has been submitted." to: "whether the subform should assume it has been submitted. When set to "true", "submitted" will be considered true if no other subform has been submitted. 2. Update top level description from: "The contents of a subform will only be validated (or otherwise processed) if a component inside of the subform is responsible for submitting the page." to: "The contents of a subform will only be validated (or otherwise processed) if a component inside of the subform is responsible for submitting the page or if the default attribute is set to true." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1060) update tagdoc for RowDisclosureEvent
update tagdoc for RowDisclosureEvent Key: TRINIDAD-1060 URL: https://issues.apache.org/jira/browse/TRINIDAD-1060 Project: MyFaces Trinidad Issue Type: Bug Components: Documentation Affects Versions: 1.2.7-core Reporter: Sandy Schaffner In the Events section, for org.apache.myfaces.trinidad.event.RowDisclosureEvent it says "The Expansion event is generated when tree nodes are expanded or collapsed." change to: "The Expansion event is generated when detail facet for the rows are expanded or collapsed." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1060) update tagdoc for RowDisclosureEvent
[ https://issues.apache.org/jira/browse/TRINIDAD-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-1060: -- Status: Patch Available (was: Open) > update tagdoc for RowDisclosureEvent > > > Key: TRINIDAD-1060 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1060 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Documentation >Affects Versions: 1.2.7-core >Reporter: Sandy Schaffner > > In the Events section, for > org.apache.myfaces.trinidad.event.RowDisclosureEvent it says "The Expansion > event is generated when tree nodes are expanded or collapsed." > change to: "The Expansion event is generated when detail facet for the rows > are expanded or collapsed." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1005) improve tag doc for rendered property
[ https://issues.apache.org/jira/browse/TRINIDAD-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-1005: -- Status: Patch Available (was: Open) > improve tag doc for rendered property > - > > Key: TRINIDAD-1005 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1005 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Documentation >Reporter: Sandy Schaffner >Priority: Minor > > The tag doc for the visible attribute says: When "rendered" is false, the > component will not in any way be rendered, and cannot be made visible on the > client. > We need to add this information to the description for the rendered property. > Currently the description for the rendered property says: "whether the > component is rendered. When set to false, no output will be delivered for > this component." > Please change to: "whether the component is rendered. When set to false, no > output will be delivered for this component (the component will not in any > way be rendered, and cannot be made visible on the client). In most cases, > use the "rendered" property instead of the "visible" property." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1005) improve tag doc for rendered property
improve tag doc for rendered property - Key: TRINIDAD-1005 URL: https://issues.apache.org/jira/browse/TRINIDAD-1005 Project: MyFaces Trinidad Issue Type: Improvement Components: Documentation Reporter: Sandy Schaffner Priority: Minor The tag doc for the visible attribute says: When "rendered" is false, the component will not in any way be rendered, and cannot be made visible on the client. We need to add this information to the description for the rendered property. Currently the description for the rendered property says: "whether the component is rendered. When set to false, no output will be delivered for this component." Please change to: "whether the component is rendered. When set to false, no output will be delivered for this component (the component will not in any way be rendered, and cannot be made visible on the client). In most cases, use the "rendered" property instead of the "visible" property." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-964) add links to tag doc and skinning doc to demos
[ https://issues.apache.org/jira/browse/TRINIDAD-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-964: - Status: Patch Available (was: Open) > add links to tag doc and skinning doc to demos > -- > > Key: TRINIDAD-964 > URL: https://issues.apache.org/jira/browse/TRINIDAD-964 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Components >Reporter: Sandy Schaffner >Priority: Minor > > add a link to tag doc and skinning doc to each demo. > remove obsolete skinning keys > alphabetize skinning selector doc -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-964) add links to tag doc and skinning doc to demos
add links to tag doc and skinning doc to demos -- Key: TRINIDAD-964 URL: https://issues.apache.org/jira/browse/TRINIDAD-964 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Reporter: Sandy Schaffner Priority: Minor add a link to tag doc and skinning doc to each demo. remove obsolete skinning keys alphabetize skinning selector doc -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-938) panelBox is inside of panelHorizontalLayout with valign="top" halign="end" does not render correctly.
panelBox is inside of panelHorizontalLayout with valign="top" halign="end" does not render correctly. - Key: TRINIDAD-938 URL: https://issues.apache.org/jira/browse/TRINIDAD-938 Project: MyFaces Trinidad Issue Type: Bug Components: Skinning Affects Versions: 1.2.5-core Reporter: Sandy Schaffner Priority: Minor When panelBox is inside of panelHorizontalLayout with valign="top" halign="end", the panelBox does not render correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-918) Create an oracle skin in Trinidad that looks like 10.1.3, for migrating customers
[ https://issues.apache.org/jira/browse/TRINIDAD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-918: - Status: Patch Available (was: Open) > Create an oracle skin in Trinidad that looks like 10.1.3, for migrating > customers > - > > Key: TRINIDAD-918 > URL: https://issues.apache.org/jira/browse/TRINIDAD-918 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Skinning >Reporter: Sandy Schaffner >Priority: Minor > Attachments: suede080130.patch > > > Customers who currently have 10.1.3 want to upgrade to Trinidad, but want > their applications to have the appearance of 10.1.3, not Trinidad. Create a > skin for Trinidad that is similar to 10.1.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-918) Create an oracle skin in Trinidad that looks like 10.1.3, for migrating customers
[ https://issues.apache.org/jira/browse/TRINIDAD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-918: - Status: Open (was: Patch Available) > Create an oracle skin in Trinidad that looks like 10.1.3, for migrating > customers > - > > Key: TRINIDAD-918 > URL: https://issues.apache.org/jira/browse/TRINIDAD-918 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Skinning >Reporter: Sandy Schaffner >Priority: Minor > > Customers who currently have 10.1.3 want to upgrade to Trinidad, but want > their applications to have the appearance of 10.1.3, not Trinidad. Create a > skin for Trinidad that is similar to 10.1.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-918) Create an oracle skin in Trinidad that looks like 10.1.3, for migrating customers
[ https://issues.apache.org/jira/browse/TRINIDAD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Schaffner updated TRINIDAD-918: - Status: Patch Available (was: Open) > Create an oracle skin in Trinidad that looks like 10.1.3, for migrating > customers > - > > Key: TRINIDAD-918 > URL: https://issues.apache.org/jira/browse/TRINIDAD-918 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Skinning >Reporter: Sandy Schaffner >Priority: Minor > > Customers who currently have 10.1.3 want to upgrade to Trinidad, but want > their applications to have the appearance of 10.1.3, not Trinidad. Create a > skin for Trinidad that is similar to 10.1.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-925) Skin selectors doc lists af:menuTabs as a Trinidad component.
Skin selectors doc lists af:menuTabs as a Trinidad component. - Key: TRINIDAD-925 URL: https://issues.apache.org/jira/browse/TRINIDAD-925 Project: MyFaces Trinidad Issue Type: Bug Components: Documentation Reporter: Sandy Schaffner Priority: Minor On this document: http://myfaces.apache.org/trinidad/skin-selectors.html#ComponentLevelSelectors af:menuTabs is listed as a component. It was replaced with navigationPane hint="tabs" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-918) Create an oracle skin in Trinidad that looks like 10.1.3, for migrating customers
Create an oracle skin in Trinidad that looks like 10.1.3, for migrating customers - Key: TRINIDAD-918 URL: https://issues.apache.org/jira/browse/TRINIDAD-918 Project: MyFaces Trinidad Issue Type: Improvement Components: Skinning Reporter: Sandy Schaffner Priority: Minor Customers who currently have 10.1.3 want to upgrade to Trinidad, but want their applications to have the appearance of 10.1.3, not Trinidad. Create a skin for Trinidad that is similar to 10.1.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-903) demos for showDetail* components missing from demo index
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 Components: Components Affects Versions: 1.2.5-core Reporter: Sandy Schaffner Priority: Minor http://www.irian.at/trinidad-demo/faces/componentDemos.jspx demos for tr:showDetailHeader and tr:showDetailItem exist but are not on index. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-902) skin selector af|selectBooleanRadio:disabled does not work
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 Components: Skinning Affects Versions: 1.2.5-core Reporter: Sandy Schaffner Priority: Minor skin selector af|selectBooleanRadio:disabled does not work -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-901) Trinidad demos use deprecated styleClass="AFDataText"
Trinidad demos use deprecated styleClass="AFDataText" - Key: TRINIDAD-901 URL: https://issues.apache.org/jira/browse/TRINIDAD-901 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.5-core Reporter: Sandy Schaffner Priority: Minor Manyy Trinidad demos use styleClass="AFDataText". This should be styleClass="AFFieldTextMarker" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-900) typo in skin-selectors on af|panelAccordion::title-disabledlink
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: Bug Components: Documentation Affects Versions: 1.2.5-core Reporter: Sandy Schaffner Priority: Minor Typo in Trinidad skinning doc. Selector listed as: af|panelAccordion::title-disabledlink. Should be: af|panelAccordion::title-disabled-link Doc here: http://myfaces.apache.org/trinidad/skin-selectors.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-899) skinning keys for tr:navigationPane not documented (hint=buttons, choice, list)
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 Trinidad Issue Type: Bug Components: Documentation Affects Versions: 1.2.5-core Environment: skinning keys for several components are not documented Reporter: Sandy Schaffner Priority: Minor Documention for the skinning keys is here: http://myfaces.apache.org/trinidad/skin-selectors.html The following components do not have their skinning keys documented: tr:navigationPane hint='buttons' tr:navigationPane hint='choice' tr:navigationPane hint='list' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-898) skinning keys af|input*:readOnly:disabled:content do not work
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 Components: Skinning Affects Versions: 1.2.5-core Reporter: Sandy Schaffner Priority: Minor The following skinning keys do not work: af|inputColor:readOnly:disabled::content af|inputDate:readOnly:disabled::content af|inputListOfValues:readOnly:disabled::content af|inputNumberSpinbox:readOnly:disabled::content af|inputText:readOnly:disabled::content -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
