[JBoss JIRA] Created: (RF-7796) panelMenu: not properly initialized in server mode after submit
by Ilya Shaikovsky (JIRA)
panelMenu: not properly initialized in server mode after submit
---------------------------------------------------------------
Key: RF-7796
URL: https://jira.jboss.org/jira/browse/RF-7796
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.2.CR1
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
After some item selecetd - the things are ok. After submit from button (after selection) selected item reseted. bean in session scope.
<h:form id="form">
<rich:panelMenu expandMode="ajax"
id="panelMenu" mode="server"
selectedChild="#{userBean.name}" immediate="true">
<rich:panelMenuGroup label="group 1"
id="menugroup_useCases"
reRender="panelMenu">
<rich:panelMenuItem label="item 1 1"
id="menu_clientSearch" immediate="true">
</rich:panelMenuItem>
<rich:panelMenuItem label="item 1.2"
id="menu_changePassword" immediate="true">
</rich:panelMenuItem>
</rich:panelMenuGroup>
<rich:panelMenuGroup label="group 2"
id="menugroup_testCases"
reRender="panelMenu">
<rich:panelMenuItem label="item 2.1"
id="menu_styleguide2" immediate="true">
</rich:panelMenuItem>
<rich:panelMenuItem label="item 2.2"
id="menu_styleguide" immediate="true">
</rich:panelMenuItem>
</rich:panelMenuGroup>
</rich:panelMenu>
<a4j:commandButton value="submit" reRender="panelMenu"></a4j:commandButton>
</h:form>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (RF-7843) scoped tabindex
by Francisco Jose Peredo Noguez (JIRA)
scoped tabindex
---------------
Key: RF-7843
URL: https://jira.jboss.org/jira/browse/RF-7843
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.3.1
Environment: Firefox 3.5, Explorer 8.0
Reporter: Francisco Jose Peredo Noguez
HTML and XHTML do not support he notion of scoped tabindexes (they were not designed with component reutilization in mind), so it is impossible to keep tab order working properly if 2 ui:components with controls with the same tabindex numbers are used in a particular page.
I propose the creation of a component a:tabScope that changes the tabindex off all the elements inside it by prefixing the with the tabindex number indicated at the a:tabScope container component.
For an example of how it would work, take a look at the referenced forum post.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (RF-7801) Not mentioned that actionListener and action supported in client mode only
by Viacheslav Garmash (JIRA)
Not mentioned that actionListener and action supported in client mode only
--------------------------------------------------------------------------
Key: RF-7801
URL: https://jira.jboss.org/jira/browse/RF-7801
Project: RichFaces
Issue Type: Bug
Components: doc
Affects Versions: 3.3.2.CR1, 3.3.1, 3.3.0, 3.2.2, 3.2.1, 3.2.0.SR1, 3.2.0
Environment: http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/rich_toolTi...
Reporter: Viacheslav Garmash
In documentation here: http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/rich_toolTi... and at livedemo website here http://livedemo.exadel.com/richfaces-demo/richfaces/toolTip.jsf?tab=info&... actionListener and action attributes mentioned like following:
action MethodBinding pointing at the application action to be invoked, if this UIComponent is activated by you, during the Apply Request Values or Invoke Application phase of the request processing lifecycle, depending on the value of the immediate property
actionListener MethodBinding pointing at method accepting an ActionEvent with return type void
There is no any code examples or notes about those parameters later in the document.
In reality those attributes work in client mode only. Any attempt to use those attributes in ajax mode doesn't make any effect. As for now I see Feature Request about "Add support for an ActionListener in the toolTip component.": https://jira.jboss.org/jira/browse/RF-3166. So it is well known fact that those attributes doesn't work in ajax mode.
Please add note to online documentation and live demo website about this limitation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (RF-7040) Not possible to rerender rich:editor in Google Chrome
by Frank Bitzer (JIRA)
Not possible to rerender rich:editor in Google Chrome
-----------------------------------------------------
Key: RF-7040
URL: https://jira.jboss.org/jira/browse/RF-7040
Project: RichFaces
Issue Type: Bug
Components: component-input
Affects Versions: 3.3.0
Environment: RichFaces 3.3.0 or 3.3.1.CR2, Google Chrome 1.0.154.64
Reporter: Frank Bitzer
Priority: Blocker
When a rich:editor is rerendered using an a4j:commandLink in Google Chrome, it gets disabled and the content disappears, while in all other browsers (tested IE7, FF3, Opera 9.6) everything works fine.
Here is the code to reproduce the behaviour:
<h:form>
<a4j:commandLink action="#{bean.prepareMessage()}" reRender="editor">
Refresh editor
</a4j:commandLink>
<rich:editor id="editor" value="#{bean.message}" useSeamText="false" width="600" height="300"/>
</h:form>
Bean "bean":
//Setters and getters for property "message"
//...
public void prepareMessage(){
message = String.valueOf(new GregorianCalendar().getTimeInMillis());
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months