[JBoss JIRA] (RF-12789) TabPanel error after partial update with new tab
by Lutz Ulrich (JIRA)
[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ]
Lutz Ulrich edited comment on RF-12789 at 2/18/13 9:53 AM:
-----------------------------------------------------------
Here you are:
dynamicTab.xhtml contains an initial static rich:tabPanel with an initial rich:tab.
Via the binding attribute, the tabPanel UIComponent is bound to my dynamicTabBean's 'staticTabPanel' property.
dynamicTabBean is an instance of my Java class test.DynamicTabBean.
The commandButton 'Add tab' invokes DynamicTabBean.addTab().
This adds a UITab to the staticTabPanel.
The staticTabPanel is re-rendered due to <f:ajax render="staticTabPanel">.
The new tab shows up.
But the <script> element at the end of <body>, which is supposed to contain RichFaces script code for all tabPanels and tabs is NOT re-rendered. Thus, one cannot switch from the initial static tab to the dynamically added new tab.
The commandButton 'Add tabPanel' invokes DynamicTabBean.addTabPanel().
A new tabPanel with 2 tabs is added.
The new tabPanel shows up. But one cannot switch its tabs due to similar problems as with the new single tab above.
was (Author: lutzulrich):
Here you are:
> TabPanel error after partial update with new tab
> ------------------------------------------------
>
> Key: RF-12789
> URL: https://issues.jboss.org/browse/RF-12789
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.0.CR2
> Environment: Mojarra 2.1.17, Tomcat 7.0.22, Java 1.7, Windows 7
> Reporter: Lutz Ulrich
> Assignee: Lukáš Fryč
> Labels: Tab, TabPanel, dynamical-add
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding tabs dynamically (programatically) in partial requests results in errors.
> The JavaScript code for all TabPanels and their child Tabs is added to HTML <body> using JavaScriptService.addScript(FacesContext, S), see DivPanelRenderer.writeJavaScript(), TabRenderer.doEncodeItemEnd() and TabRenderer.doEncodeEnd().
> The top-level <script> element in <body> won't be updated if a new Tab is added dynamically in a partial request. Thus, the script, new RichFaces.ui.Tab(...), for the new Tab is missing.
> Similar problems arise if a TabPanel is added in a partial request.
> All scripts, RichFaces.ui.Tab(...) and RichFaces.ui.TabPanel(...) should be rendered inline for partial update to work with new TabPanels and new Tabs.
--
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-12789) TabPanel error after partial update with new tab
by Lutz Ulrich (JIRA)
[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ]
Lutz Ulrich commented on RF-12789:
----------------------------------
Here you are:
> TabPanel error after partial update with new tab
> ------------------------------------------------
>
> Key: RF-12789
> URL: https://issues.jboss.org/browse/RF-12789
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.0.CR2
> Environment: Mojarra 2.1.17, Tomcat 7.0.22, Java 1.7, Windows 7
> Reporter: Lutz Ulrich
> Assignee: Lukáš Fryč
> Labels: Tab, TabPanel, dynamical-add
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding tabs dynamically (programatically) in partial requests results in errors.
> The JavaScript code for all TabPanels and their child Tabs is added to HTML <body> using JavaScriptService.addScript(FacesContext, S), see DivPanelRenderer.writeJavaScript(), TabRenderer.doEncodeItemEnd() and TabRenderer.doEncodeEnd().
> The top-level <script> element in <body> won't be updated if a new Tab is added dynamically in a partial request. Thus, the script, new RichFaces.ui.Tab(...), for the new Tab is missing.
> Similar problems arise if a TabPanel is added in a partial request.
> All scripts, RichFaces.ui.Tab(...) and RichFaces.ui.TabPanel(...) should be rendered inline for partial update to work with new TabPanels and new Tabs.
--
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-12794) Using the same name for id and name for this tag triggers an error with IE
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-12794?page=com.atlassian.jira.plugin.s... ]
Jan Papousek commented on RF-12794:
-----------------------------------
I've successfully reproduced the issue. The problem is location of h:form. When a4j:jsFunction is inside the h:form (see the code snippet above), everything works correctly. The following code doesn't work using IE 7, IE 8, but it works in Firefox and IE 9:
{code}
<a4j:jsFunction name="setText2" id="setText2" render="showText2">
<a4j:param name="text" assignTo="#{testBean.text}" />
</a4j:jsFunction>
<h:form>
Output: <h:outputText id="showText2" value="#{testBean.text}" />
<br />
<span onmouseover="setText2('TEXT')" onmouseout="setText2('')">ACTIVE TEXT</span>
</h:form>
{code}
> Using the same name for id and name for this tag triggers an error with IE
> --------------------------------------------------------------------------
>
> Key: RF-12794
> URL: https://issues.jboss.org/browse/RF-12794
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Jean ANDRE
> Assignee: Jan Papousek
>
> Using the same name for id and name for this tag triggers an error with IE.
> We need to:
> # Confirm that this is an issue
> # Determine if this is an RF issue, an upstream JSF issue, or purely a IE issue
> # Document this _somehwere_
--
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