[JBoss JIRA] Created: (RF-8490) Editor can't be updated via ajax in Chrome
by Ilya Shaikovsky (JIRA)
Editor can't be updated via ajax in Chrome
------------------------------------------
Key: RF-8490
URL: https://jira.jboss.org/jira/browse/RF-8490
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: browser compatibility, component-input
Affects Versions: 3.3.3.CR1
Environment: Chrome 4.0.249.89 (38071)
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
livedemo sample not works for me in chrome. the same results for 3.3.1 and 3.3.3. So seems not a regression but just browser related.
in console I see
:8080/richfaces-demo/a4j/g/3_3_1.GAorg.ajax4jsf.javascript.AjaxScript.jsf:1394Uncaught Error: NO_MODIFICATION_ALLOWED_ERR: DOM Exception 7
this line is
oldnode.outerHTML = new XMLSerializer().serializeToString(newnode);
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-8464) a4j:included rich:dataTable prevents rich:panelMenu, a4j:commandButton and rich:tree from responding
by mark lewis (JIRA)
a4j:included rich:dataTable prevents rich:panelMenu, a4j:commandButton and rich:tree from responding
----------------------------------------------------------------------------------------------------
Key: RF-8464
URL: https://jira.jboss.org/jira/browse/RF-8464
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 3.3.2.SR1
Environment: Windows XP SP2, Tomcat 6.0, Application built with the following jars:
jsch-0.1.41
jhighlight-1.0
jsf-api
jsf-impl
jstl
myfaces-[api|impl]-1.2.7
richfaces-[api|impl|ui]-3.3.2-SR1
commons:
beanutils-1.7.0
codec-1.3
collections-3.2
digester-1.8
discovery-0.4
logging-1.1.1
Reporter: mark lewis
3 scenarios have occurred where reproducable malfunction can be replicated. In each case, the deployed web application appears to not respond. In each case, a jsp file is included using a4j:include and contains a rich:dataTable element.
In each case, minification has been conducted which isolates the dataTable as the element causing the issue.
1. Incompatibility with a4j:commandButton
index.jsp has a4j:commandButton. Clicking it reRenders area which has the a4j:include. Once the included file is in, clicking the a4j:commandButton causes the button to stay in pressed state.
Forum reference: http://stackoverflow.com/questions/2237863/a4jincluded-richdatatable-nega...
2. Incompatibility with rich:panelMenu
Same application. Here, the jsp file included (which contains a tabPanel one tab with the dataTable, and another with a rich:panelMenu) loads ok, appears to render all components fine, but when the panelMenu is expanded to reveal items (which it does ok), clicking on an item results in no response. RF demo panelMenu code was used with a right hand panel to receive information pertaining to which item was clicked. When the panelMenu is inserted in the index.jsp and the a4j:include removed or the dataTable taken out of the included jsp, the functionality is restored ok.
Forum reference: http://community.jboss.org/thread/148648?tstart=0
3. Incompatibility with rich:tree
Essentially the same as [2] except read rich:tree instead of rich:panelMenu. Tree opens ok, and has been applied using demo code. Custom icons for leaves etc. But selecting a leaf results in no response.
--
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
14 years, 9 months