[jira] [Created] (TRINIDAD-2329) remove acc datatable=0 from non data tables
Dave Robinson created TRINIDAD-2329: --- Summary: remove acc datatable=0 from non data tables Key: TRINIDAD-2329 URL: https://issues.apache.org/jira/browse/TRINIDAD-2329 Project: MyFaces Trinidad Issue Type: Bug Components: Components Reporter: Dave Robinson Priority: Minor we long ago added datatable=0 to non data tables as a JAWS hack so it could understand when table was not being used for data. This has long ago been fixed in JAWS, which now correctly looks for the 'standard' role=presentation for non data tables. This bug is to remove old datatable=0 cruft from our acc rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2329) remove acc datatable=0 from non data tables
[ https://issues.apache.org/jira/browse/TRINIDAD-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Robinson updated TRINIDAD-2329: Status: Patch Available (was: Open) remove acc datatable=0 from non data tables --- Key: TRINIDAD-2329 URL: https://issues.apache.org/jira/browse/TRINIDAD-2329 Project: MyFaces Trinidad Issue Type: Bug Components: Components Reporter: Dave Robinson Priority: Minor we long ago added datatable=0 to non data tables as a JAWS hack so it could understand when table was not being used for data. This has long ago been fixed in JAWS, which now correctly looks for the 'standard' role=presentation for non data tables. This bug is to remove old datatable=0 cruft from our acc rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2137) Improve Trinidad component and tagdoc generation plugin to handle deprecated classes
Improve Trinidad component and tagdoc generation plugin to handle deprecated classes Key: TRINIDAD-2137 URL: https://issues.apache.org/jira/browse/TRINIDAD-2137 Project: MyFaces Trinidad Issue Type: Improvement Components: Documentation Affects Versions: 2.0.4-plugins Reporter: Dave Robinson Priority: Minor When creating component metadata, a component may be marked as deprecated using fmd:deprecated. When a component is deprecated, we should include this information in the generated class javadoc, as well as in the generated tagdoc page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2090) Accessible Trinidad 2.0
[ https://issues.apache.org/jira/browse/TRINIDAD-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Robinson updated TRINIDAD-2090: Status: Patch Available (was: Open) Accessible Trinidad 2.0 Key: TRINIDAD-2090 URL: https://issues.apache.org/jira/browse/TRINIDAD-2090 Project: MyFaces Trinidad Issue Type: New Feature Components: Components Affects Versions: 2.0.0-alpha-2 Environment: Developed with Netbeans IDE 6.9, tested with JAWS and NVDA screen readers. works with IE8, IE7 and FF browser. Reporter: Karel Simek Priority: Minor Labels: ARIA, WAI-ARIA, accessibility Original Estimate: 8h Remaining Estimate: 8h As a result of my diploma thesis at Czech Technical University in Prague, I have implemented WAI-ARIA accessibility features (landmarks, roles, states, properties) into several Trinidad widgets. The implementation also includes new standardized keyboard navigation and shortcuts. All component were tested with visually impaired users. I am looking for somebody for code review and patch preparation. I will be happy to provide the source code, setup scripts, access to the project repository and documentation. Widget demo and project details available at http://amun.felk.cvut.cz/coe/?page=trinidad Ing. Karel Simek, project SUCCESS -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2082) hidden labels don't always render in screen reader mode
hidden labels don't always render in screen reader mode --- Key: TRINIDAD-2082 URL: https://issues.apache.org/jira/browse/TRINIDAD-2082 Project: MyFaces Trinidad Issue Type: Bug Components: Components Reporter: Dave Robinson When in screen reader mode, we always expect hidden labels to be rendered, as these hidden labels often contain information (like labels for input fields) necessary for 508 and WCAG 2.0 compliance. The HiddenLabelUtils has a method supportsHiddenLabels() that returns false if the current agent does not support hidden (off page) labels on the page. When in screen reader mode, this method should always return true, as we always want labels to be present in screen reader mode - regardless if they correctly appear hidden or not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2082) hidden labels don't always render in screen reader mode
[ https://issues.apache.org/jira/browse/TRINIDAD-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Robinson updated TRINIDAD-2082: Status: Patch Available (was: Open) hidden labels don't always render in screen reader mode --- Key: TRINIDAD-2082 URL: https://issues.apache.org/jira/browse/TRINIDAD-2082 Project: MyFaces Trinidad Issue Type: Bug Components: Components Reporter: Dave Robinson When in screen reader mode, we always expect hidden labels to be rendered, as these hidden labels often contain information (like labels for input fields) necessary for 508 and WCAG 2.0 compliance. The HiddenLabelUtils has a method supportsHiddenLabels() that returns false if the current agent does not support hidden (off page) labels on the page. When in screen reader mode, this method should always return true, as we always want labels to be present in screen reader mode - regardless if they correctly appear hidden or not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TRINIDAD-2082) hidden labels don't always render in screen reader mode
[ https://issues.apache.org/jira/browse/TRINIDAD-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13016567#comment-13016567 ] Dave Robinson edited comment on TRINIDAD-2082 at 4/6/11 9:56 PM: - Use the JIRA-TRINIDAD-2082v2.patch instead of the first one submitted. With further testing I saw that the webkit xml agent file did not list webkit as having the capability of supporting HTML fieldsets, so fixed that too. You can see that the Safari agent goldens are now getting the fieldsets when before they were not. was (Author: daverobinson): Use this one. With further testing I saw that the webkit xml agent file did not list webkit as having the capability of supporting HTML fieldsets, so fixed that too. You can see that the Safari agent goldens are now getting the fieldsets when before they were not. hidden labels don't always render in screen reader mode --- Key: TRINIDAD-2082 URL: https://issues.apache.org/jira/browse/TRINIDAD-2082 Project: MyFaces Trinidad Issue Type: Bug Components: Components Reporter: Dave Robinson Attachments: JIRA-TRINIDAD-2082.patch, JIRA-TRINIDAD-2082v2.patch When in screen reader mode, we always expect hidden labels to be rendered, as these hidden labels often contain information (like labels for input fields) necessary for 508 and WCAG 2.0 compliance. The HiddenLabelUtils has a method supportsHiddenLabels() that returns false if the current agent does not support hidden (off page) labels on the page. When in screen reader mode, this method should always return true, as we always want labels to be present in screen reader mode - regardless if they correctly appear hidden or not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TRINIDAD-1913) All tr:group component attributes to specify boundary and title preferences
All tr:group component attributes to specify boundary and title preferences --- Key: TRINIDAD-1913 URL: https://issues.apache.org/jira/browse/TRINIDAD-1913 Project: MyFaces Trinidad Issue Type: Improvement Environment: N/A Reporter: Dave Robinson When groups are rendered it is up to the container component on whether to include a graphical group boundaries or title values. This improvement would be to add attributes to tr:group so that a group could specify it's preference to the container to either show or hide boundaries and to use custom title values. Here are the new attributes: startBoundary indicates if a visual group start boundary is desired. The default value of 'dontCare' indicates no preference. A value of 'show' indicates a preference to show a start boundary. A value of 'hide' indicates a preference to not show a start boundary. Regardless of the start boundary value, whether a visual boundary will be displayed is up to the group's parent component. endBoundary indicates if a visual group end boundary is desired. The default value of 'dontCare' indicates no preference. A value of 'show' indicates a preference to show an end boundary. A value of 'hide' indicates a preference to not show an end boundary. Regardless of the end boundary value, whether a visual boundary will be displayed is up to the group's parent component. title a title value for the group. Whether anything is done with this title value is up to the group's parent component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1913) All tr:group component attributes to specify boundary and title preferences
[ https://issues.apache.org/jira/browse/TRINIDAD-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Robinson updated TRINIDAD-1913: Status: Patch Available (was: Open) All tr:group component attributes to specify boundary and title preferences --- Key: TRINIDAD-1913 URL: https://issues.apache.org/jira/browse/TRINIDAD-1913 Project: MyFaces Trinidad Issue Type: Improvement Environment: N/A Reporter: Dave Robinson Original Estimate: 24h Remaining Estimate: 24h When groups are rendered it is up to the container component on whether to include a graphical group boundaries or title values. This improvement would be to add attributes to tr:group so that a group could specify it's preference to the container to either show or hide boundaries and to use custom title values. Here are the new attributes: startBoundary indicates if a visual group start boundary is desired. The default value of 'dontCare' indicates no preference. A value of 'show' indicates a preference to show a start boundary. A value of 'hide' indicates a preference to not show a start boundary. Regardless of the start boundary value, whether a visual boundary will be displayed is up to the group's parent component. endBoundary indicates if a visual group end boundary is desired. The default value of 'dontCare' indicates no preference. A value of 'show' indicates a preference to show an end boundary. A value of 'hide' indicates a preference to not show an end boundary. Regardless of the end boundary value, whether a visual boundary will be displayed is up to the group's parent component. title a title value for the group. Whether anything is done with this title value is up to the group's parent component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1893) trh:tablelayout not a layout table in screen reader mode
trh:tablelayout not a layout table in screen reader mode Key: TRINIDAD-1893 URL: https://issues.apache.org/jira/browse/TRINIDAD-1893 Project: MyFaces Trinidad Issue Type: Bug Reporter: Dave Robinson trh:tableLayout should be identified as a layout table (having role=presentation) when it is rendered in screen reader mode. TableLayoutRenderer currently calls the OutputUtils.renderDataTableAttributes method to render its table, and does not get this role assignment. The TableLayoutRenderer should be updated to call the OutputUtils.renderLayoutTableAttributes method instead, so it will get the role assignment. I'll create and upload a patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1893) trh:tablelayout not a layout table in screen reader mode
[ https://issues.apache.org/jira/browse/TRINIDAD-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Robinson updated TRINIDAD-1893: Status: Patch Available (was: Open) trh:tablelayout not a layout table in screen reader mode Key: TRINIDAD-1893 URL: https://issues.apache.org/jira/browse/TRINIDAD-1893 Project: MyFaces Trinidad Issue Type: Bug Reporter: Dave Robinson Attachments: TRINIDAD-1893 trunk.patch trh:tableLayout should be identified as a layout table (having role=presentation) when it is rendered in screen reader mode. TableLayoutRenderer currently calls the OutputUtils.renderDataTableAttributes method to render its table, and does not get this role assignment. The TableLayoutRenderer should be updated to call the OutputUtils.renderLayoutTableAttributes method instead, so it will get the role assignment. I'll create and upload a patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TRINIDAD-1893) trh:tablelayout not a layout table in screen reader mode
[ https://issues.apache.org/jira/browse/TRINIDAD-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902656#action_12902656 ] Dave Robinson edited comment on TRINIDAD-1893 at 8/25/10 5:58 PM: -- patch uploaded was (Author: daverobinson): patch trh:tablelayout not a layout table in screen reader mode Key: TRINIDAD-1893 URL: https://issues.apache.org/jira/browse/TRINIDAD-1893 Project: MyFaces Trinidad Issue Type: Bug Reporter: Dave Robinson Attachments: TRINIDAD-1893 trunk.patch trh:tableLayout should be identified as a layout table (having role=presentation) when it is rendered in screen reader mode. TableLayoutRenderer currently calls the OutputUtils.renderDataTableAttributes method to render its table, and does not get this role assignment. The TableLayoutRenderer should be updated to call the OutputUtils.renderLayoutTableAttributes method instead, so it will get the role assignment. I'll create and upload a patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1839) Agent PLATFORM_IPHONE should detect iPad as well
Agent PLATFORM_IPHONE should detect iPad as well Key: TRINIDAD-1839 URL: https://issues.apache.org/jira/browse/TRINIDAD-1839 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.14-core , 1.0.13-core , 2.0.0.3-core Environment: iPad Reporter: Dave Robinson We currently use agent platform iphone to identify iPhone and iPod touch. It really means iOS. We should add iPad to this definition as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1696) acc (screen reader mode) layout tables should include role=presentation
acc (screen reader mode) layout tables should include role=presentation
-
Key: TRINIDAD-1696
URL: https://issues.apache.org/jira/browse/TRINIDAD-1696
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.12-core
Environment: all
Reporter: Dave Robinson
Priority: Minor
When using trh:tableLayout in our page to layout some UI components, it gives
warning during Accessibility testing:
WARNING - This layout Table could be confused for a data table by Screen
Readers
From the html perspective, this warning can be fixed by setting
role=presentation
on the html table element.
We can add
role=presentation to layout tables with the following addition to
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.OutputTextUtils.renderLayoutTableAttributes():
if (CoreRenderer.isScreenReaderMode(arc))
{
ResponseWriter writer = context.getResponseWriter();
writer.writeAttribute(datatable, 0, null);
-- writer.writeAttribute(role, presentation, null); --
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1587) maven-faces-plugin should allow java compatible variable names when converting list value of -1
[ https://issues.apache.org/jira/browse/TRINIDAD-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12768910#action_12768910 ] Dave Robinson commented on TRINIDAD-1587: - Here's some example xml to cause this: property property-namesize/property-name property-classint/property-class default-value-1/default-value property-extension fmd:property-metadata fmd:requiredfalse/fmd:required fmd:property-values-1 0 1 2 /fmd:property-values /fmd:property-metadata /property-extension /property maven-faces-plugin should allow java compatible variable names when converting list value of -1 -- Key: TRINIDAD-1587 URL: https://issues.apache.org/jira/browse/TRINIDAD-1587 Project: MyFaces Trinidad Issue Type: Bug Environment: Any Reporter: Dave Robinson Priority: Minor If you are using the component generator (MyFacesComponentGenerator.java) then you could end up with an invalid generated java file attribute name when converting a property that has as an allowed value of -1. For example, having property 'size' with allowed values of -1 0 1 results in 2 ok properties for 0 and 1: private String size0; private String size1; but an invalid definition of: private String size-1; A good solution would be to look for a leading nonA-Z, non0-9 character and replacing it with a valid character. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1587) maven-faces-plugin should allow java compatible variable names when converting list value of -1
maven-faces-plugin should allow java compatible variable names when converting list value of -1 -- Key: TRINIDAD-1587 URL: https://issues.apache.org/jira/browse/TRINIDAD-1587 Project: MyFaces Trinidad Issue Type: Bug Environment: Any Reporter: Dave Robinson Priority: Minor If you are using the component generator (MyFacesComponentGenerator.java) then you could end up with an invalid generated java file attribute name when converting a property that has as an allowed value of -1. For example, having property 'size' with allowed values of -1 0 1 results in 2 ok properties for 0 and 1: private String size0; private String size1; but an invalid definition of: private String size-1; A good solution would be to look for a leading nonA-Z, non0-9 character and replacing it with a valid character. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1583) Add tagdoc information for accessibility
Add tagdoc information for accessibility Key: TRINIDAD-1583 URL: https://issues.apache.org/jira/browse/TRINIDAD-1583 Project: MyFaces Trinidad Issue Type: Improvement Environment: Irrelevant Reporter: Dave Robinson Priority: Minor Improve Trinidad tagdoc generation plugin to include optional metadata to support accessibility information on the component level and the attribute level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1543) AccessibilityProfile is not Serializable
[ https://issues.apache.org/jira/browse/TRINIDAD-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12741596#action_12741596 ] Dave Robinson commented on TRINIDAD-1543: - Matthias - The change did not quite do it. In playing with this more, we still will receive an error during loading persisted sessions. This is because for subclass to be Serializable when superclass is not, the superclass must have an accessible no-arg constructor. In our case of a private static inner class as the subclass, the superclass no-arg constructor's must be at least package-level security (private will not work). I've created 2 more files and will upload here for your review an commit if all looks OK. Thanks! AccessibilityProfile is not Serializable Key: TRINIDAD-1543 URL: https://issues.apache.org/jira/browse/TRINIDAD-1543 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Reporter: Andy Schwartz Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1543 for 1.2.11.4 branch.patch, TRINIDAD-1543 for Trinidad Trunk.patch The AccessibilityProfile class is used to represent user-specific preferences, and is typically stored in the HttpSession. However, the fact that this class is not serializable prevents it from participating in session replication. Logging this issue to request that we make AccessibilityProfile serializable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1543) AccessibilityProfile is not Serializable
[ https://issues.apache.org/jira/browse/TRINIDAD-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12739728#action_12739728 ] Dave Robinson commented on TRINIDAD-1543: - Patch changes have been reviewed and approved by Andy Schwartz AccessibilityProfile is not Serializable Key: TRINIDAD-1543 URL: https://issues.apache.org/jira/browse/TRINIDAD-1543 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Reporter: Andy Schwartz Priority: Minor Attachments: TRINIDAD-1543 for Trinidad Trunk.patch The AccessibilityProfile class is used to represent user-specific preferences, and is typically stored in the HttpSession. However, the fact that this class is not serializable prevents it from participating in session replication. Logging this issue to request that we make AccessibilityProfile serializable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1543) AccessibilityProfile is not Serializable
[ https://issues.apache.org/jira/browse/TRINIDAD-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12739726#action_12739726 ] Dave Robinson commented on TRINIDAD-1543: - I've got patches for this, for trunk and branch 1.2.11.4 AccessibilityProfile is not Serializable Key: TRINIDAD-1543 URL: https://issues.apache.org/jira/browse/TRINIDAD-1543 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Reporter: Andy Schwartz Priority: Minor Attachments: TRINIDAD-1543 for Trinidad Trunk.patch The AccessibilityProfile class is used to represent user-specific preferences, and is typically stored in the HttpSession. However, the fact that this class is not serializable prevents it from participating in session replication. Logging this issue to request that we make AccessibilityProfile serializable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1371) JAWS: layout tables incorrectly identified as data tables
[ https://issues.apache.org/jira/browse/TRINIDAD-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668981#action_12668981 ] Dave Robinson commented on TRINIDAD-1371: - I have fix and will attach the patches. -Dave JAWS: layout tables incorrectly identified as data tables - Key: TRINIDAD-1371 URL: https://issues.apache.org/jira/browse/TRINIDAD-1371 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.10-core, 1.0.10-core Environment: Windows, JAWS8 Reporter: Andy Schwartz Priority: Minor Attachments: jira1371_for_Trinidad_trunk_1.0.x.patch, jira1371_for_Trinidad_trunk_1.2.x.patch JAWS distinguishes between two types of HTML tables: 1. Data tables 2. Layout tables Data tables should have markup that identify column/row headers (eg. th elements with scope=col|row) as well as non-empty summary attributes. JAWS provides special support for navigating to data tables as well as for navigating between cells within data tables. Layout tables should not contain any row/column header markup and should specify an empty summary attribute. These tables should be completely transparent to screen reader end users since they are only used for layout purposes. Unfortunately JAWS sometimes gets confused and treats some layout tables as if they are data tables. This is bad, since this adds noise to the screen read reader experience - ie. JAWS reports the presence of tables that are not interesting to blind users. To see this in action, access the following panelFormLayout demo via JAWS: http://www.irian.at/trinidad-demo/faces/components/panelFormLayout.jspx To see which tables JAWS considers to be data tables, do the following: - Hit Insert+F3 to bring up the JAWS Virtual HTML Featuers dialog - Arrow down to the Tables List item and hit Enter - JAWS brings up the Select a Table dialog, which lists the data tables. In the panelFormLayout demo, the only data table in the page is the Attributes table. However, JAWS incorrectly reports 4 other layout tables rendered by the panelFormLayout component as being data tables. A simple technique for forcing JAWS to recognize layout tables is to include the datatable=0 attribute on the HTML table element. This is non-standard attribute that JAWS checks to determine whether a particular HTML table is a data/layout table. This fix for this bug is to enhance OutputUtils.renderLayoutTableAttributes() to render the datatable=0 attribute when in screen reader mode (ie. when CoreRenderer.isScreenReaderMode() returns true). This will force JAWS to treat any Trinidad-rendered layout tables as layout tables and avoid confusion with data tables. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1072) Improvements to testing framework
Improvements to testing framework - Key: TRINIDAD-1072 URL: https://issues.apache.org/jira/browse/TRINIDAD-1072 Project: MyFaces Trinidad Issue Type: Improvement Components: Build Affects Versions: 1.2.7-core, 1.0.7-core Reporter: Dave Robinson The testing framework, which centers around org.apache.myfaces.trinidadinternal.renderkit.RenderKitTestCase, would benefit from some improvements: * Currently, a component is tested it exists with a static context, as defined in the populateDefaultComponentTree. While we do want a default component tree (with things like document/form) it would be nice if the test script could support context for the component, so instead of starting the test with a base-component, and then specifying components inside it, you would also have the option of specifying your base-component inside another component. Regardless of the implementation of this improvement, we would want to support multiple level of parent components. * Add the ability to create a test SuiteDefinition where you can specify to test printable (or rather navigable by XhtmlRenderer.supportsNavigation()) test suites * Ability to set/test various attribute types, like AWTKeyStroke. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
