[JBoss JIRA] (RF-12958) Popup panel opened from inside popup panel doesn't work
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-12958:
----------------------------------
Summary: Popup panel opened from inside popup panel doesn't work
Key: RF-12958
URL: https://issues.jboss.org/browse/RF-12958
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output, regression
Affects Versions: 4.3.2
Environment: RichFaces 4.3.2.CR1
Metamer 4.3.2-SNAPSHOT
Mojarra 2.1.7
JBoss AS 7.1.1.Final
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 26.0.1410.63 @ Linux x86_64, Firefox 20
Reporter: Pavol Pitonak
Priority: Critical
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml
# select "Rich Popup Panel" template from the select on top of the page and click "Load"
# click "Call the popup" button inside popup panel
result:
* a new popup panel should apper (i.e. two panels should be visible, both modal)
* this worked in RichFaces 4.3.1.Final
--
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
11 years, 7 months
[JBoss JIRA] (RF-12309) CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12309?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12309:
---------------------------------
This issue was almost covered, we need to make sure all the requirements in [Description] were reflected.
> CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub
> ----------------------------------------------------------------------------------------------------------------
>
> Key: RF-12309
> URL: https://issues.jboss.org/browse/RF-12309
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Affects Versions: 4.2.0.Final
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha1
>
>
> There are lot of bindings which needs to be manually hard-coded in order to make the component work:
> Look at sample of the calendar component:
> 1. [Renderer template|https://github.com/richfaces/components/blob/4.2.2.20120513-Fina...]
> 2. [Component interface|https://github.com/richfaces/components/blob/4.2.2.20120513-Fin...]
> ----
> What could follow naming conventions?
> 1. *Renderer template*
> * {{<class>}} - use the package where the template resides in: {{calendar.template.xml}} -> {{CalendarRenderer}}
> * {{<superclass}} - use the {{<class> + Base}}: {{CalendarRenderer}} -> {{CalendarRendererBase}}, if not exists, use {{org.richfaces.renderkit.RendererBase}}
> 2. *component* {{org.richfaces.component.AbstractCalendar}}
> * component-type: {{org.richfaces.Calendar}}
> * component-family: {{org.richfaces.Calendar}}
> * generated class: {{org.richfaces.component.UICalendar}}
> * renderer: {{org.richfaces.CalendarRenderer}}
> * tag: {{@Tag(name = "calendar", handler = "org.richfaces.view.facelets.CalendarHandler")}}
> Some definitions what need to be configured per component library: e.g. prefix for component type/family/renderer, etc.
> Only classes which violates conventions would be necessary to configure specifically.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12309) CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12309?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12309:
----------------------------
Fix Version/s: 5.0.0.Alpha1
(was: 5-Tracking)
> CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub
> ----------------------------------------------------------------------------------------------------------------
>
> Key: RF-12309
> URL: https://issues.jboss.org/browse/RF-12309
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Affects Versions: 4.2.0.Final
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha1
>
>
> There are lot of bindings which needs to be manually hard-coded in order to make the component work:
> Look at sample of the calendar component:
> 1. [Renderer template|https://github.com/richfaces/components/blob/4.2.2.20120513-Fina...]
> 2. [Component interface|https://github.com/richfaces/components/blob/4.2.2.20120513-Fin...]
> ----
> What could follow naming conventions?
> 1. *Renderer template*
> * {{<class>}} - use the package where the template resides in: {{calendar.template.xml}} -> {{CalendarRenderer}}
> * {{<superclass}} - use the {{<class> + Base}}: {{CalendarRenderer}} -> {{CalendarRendererBase}}, if not exists, use {{org.richfaces.renderkit.RendererBase}}
> 2. *component* {{org.richfaces.component.AbstractCalendar}}
> * component-type: {{org.richfaces.Calendar}}
> * component-family: {{org.richfaces.Calendar}}
> * generated class: {{org.richfaces.component.UICalendar}}
> * renderer: {{org.richfaces.CalendarRenderer}}
> * tag: {{@Tag(name = "calendar", handler = "org.richfaces.view.facelets.CalendarHandler")}}
> Some definitions what need to be configured per component library: e.g. prefix for component type/family/renderer, etc.
> Only classes which violates conventions would be necessary to configure specifically.
--
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
11 years, 7 months
[JBoss JIRA] (RF-10206) Add WAI-ARIA support to components
by ashutosh deora (JIRA)
[ https://issues.jboss.org/browse/RF-10206?page=com.atlassian.jira.plugin.s... ]
ashutosh deora commented on RF-10206:
-------------------------------------
Rafael Jeferson Pezzuto Damaceno , Please can you share our code for WAI-ARIA for 3.3.3 version .
> Add WAI-ARIA support to components
> ----------------------------------
>
> Key: RF-10206
> URL: https://issues.jboss.org/browse/RF-10206
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: accessibility
> Affects Versions: 3.3.3.Final
> Reporter: Brent Yarger
> Assignee: Nick Belaevski
> Labels: WAI-ARIA
> Fix For: 5-Future
>
>
> WAI-ARIA support would be a nice feature to have to improve accessibility of Richfaces. Both keyboard accessibility and screen reader accessibility could be significantly improved by adding WAI-ARIA support
--
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
11 years, 7 months