[JBoss JIRA] (RF-12577) rich:select - can't select different value after deleting the old one
by Alex Andreenko (JIRA)
[ https://issues.jboss.org/browse/RF-12577?page=com.atlassian.jira.plugin.s... ]
Alex Andreenko commented on RF-12577:
-------------------------------------
I can't believe that RF 4.3 with this bug.
The component is completely ruined...
> rich:select - can't select different value after deleting the old one
> ---------------------------------------------------------------------
>
> Key: RF-12577
> URL: https://issues.jboss.org/browse/RF-12577
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.0.M2
> Environment: RichFaces 4.3.0.20121024-M2
> Metamer 4.3.0.20121024-M2
> Weld Servlet (Uber Jar) 20120106-1159
> Apache Tomcat 7.0.32
> Java(TM) SE Runtime Environment 1.7.0_07-b10 @ Linux
> Firefox 16.0 @ Linux x86_64
> RichFaces 4.3.0.20121024-M2
> Metamer 4.3.0.20121024-M2
> JBoss Application Server: Weld Integration 7.1.1.Final
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.7.0_07-b10 @ Linux
> Firefox 16.0 @ Linux x86_64
> Reporter: Jan Papousek
> Fix For: 5-Tracking
>
>
--
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-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12768 at 2/19/13 5:54 AM:
-----------------------------------------------------------
Reopening because I can reproduce the issue on Metamer with {{4.3.0.Final}}, current SNAPSHOT and also with {{WFK 2.1.0.DR2}}.
It works with Chrome and other browsers. It is occurring only on Firefox.
There is slightly different behavior against description, and it is that *tabs are clickable but can not be removed*.
was (Author: jhuska):
Reopening because I can reproduce the issue on Metamer with {{4.3.0.Final}}, current SNAPSHOT and also with {{WFK 2.1.0.DR2}}.
It works with Chrome and other browsers. It is only on Firefox.
> Metamer: rich:tabPanel: Tabs are not clickable and can't be removed
> -------------------------------------------------------------------
>
> Key: RF-12768
> URL: https://issues.jboss.org/browse/RF-12768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final
> Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1
> Reporter: Petr Mensik
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed.
--
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-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ]
Juraj Húska reopened RF-12768:
------------------------------
Reopening because I can reproduce the issue on Metamer with {{4.3.0.Final}}, current SNAPSHOT and also with {{WFK 2.1.0.DR2}}.
It works with Chrome and other browsers. It is only on Firefox.
> Metamer: rich:tabPanel: Tabs are not clickable and can't be removed
> -------------------------------------------------------------------
>
> Key: RF-12768
> URL: https://issues.jboss.org/browse/RF-12768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final
> Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1
> Reporter: Petr Mensik
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed.
--
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 Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12789:
---------------------------------
Oh, I can see the problem now: you are using f:ajax, but tabPanel newly requires the a4j:ajax usage - just replace f:ajax with a4j:ajax (f:ajax us subset of equivalent a4j:ajax features).
The problem is reported already RF-12760
and discussed here https://community.jboss.org/thread/221406
We will further dig into it today during team meeting: https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2013-02-19
Please verify that the suggested workaround works for you.
> 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
>
> Attachments: dynamicTab.xhtml, DynamicTabBean.java
>
> 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 Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12789:
----------------------------
Attachment: (was: DynamicTabBean.java)
> 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
>
> Attachments: dynamicTab.xhtml, DynamicTabBean.java
>
> 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 Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12789:
----------------------------
Attachment: (was: dynamicTab.xhtml)
> 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
>
> Attachments: dynamicTab.xhtml, DynamicTabBean.java
>
> 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-12772) rich:fileUpload does not working properly (style, script)
by Byambaa MD (JIRA)
[ https://issues.jboss.org/browse/RF-12772?page=com.atlassian.jira.plugin.s... ]
Byambaa MD commented on RF-12772:
---------------------------------
This issue very urgent for me :(
> rich:fileUpload does not working properly (style, script)
> ---------------------------------------------------------
>
> Key: RF-12772
> URL: https://issues.jboss.org/browse/RF-12772
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final, 4.2.4, 4.3.0.Final
> Environment: when CONTEXT-PARAM (org.richfaces.SKIN=none and org.richfaces.CONTROL_SKINNING=disable and org.richfaces.CONTROL_SKINNING_CLASSES=disable and org.richfaces.enableControlSkinning=false and org.richfaces.LoadStyleStrategy=NONE and org.richfaces.LoadScriptStrategy=NONE)
> Reporter: Byambaa MD
> Fix For: 5-Tracking
>
>
> _<rich:fileUpload>_ does not working properly and require need to refresh browser when CONTEXT-PARAM:
> * org.richfaces.SKIN=none
> * org.richfaces.CONTROL_SKINNING=disable
> * org.richfaces.CONTROL_SKINNING_CLASSES=disable
> * org.richfaces.enableControlSkinning=false
> * org.richfaces.LoadStyleStrategy=NONE
> * org.richfaces.LoadScriptStrategy=NONE
--
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