[JBoss JIRA] (RF-12777) rich:picklist restriction
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12777?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12777:
-------------------------------
Priority: Major (was: Critical)
For _immediate_ response to an issue, consider either:
# fixing the issue yourself, and issuing a [pull request via github|https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubA...]
# purchasing a [WFK support subscription|http://www.redhat.com/products/jbossenterprisemiddleware/web...]
Assigning to RichFaces 5-Tracking to be addressed in a future release.
> rich:picklist restriction
> -------------------------
>
> Key: RF-12777
> URL: https://issues.jboss.org/browse/RF-12777
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.2.3.Final
> Environment: ie browser
> Reporter: Shireen O
> Labels: picklist
>
> Hello,
> I have 3 issues related to rich:picklist component, and I need solution immediately:-
> 1- I wanna add tooltip for selected item in both source and target lists,
> because not all item data is shown clear,and I am restricted with list width.
> 2- I wanna add horizontal scroll for source & target lists alone, Not for the whole rich:picklist component. Only the vertical scroll is appear.
> 3- When I changed style for selected item using selectItemClass property,
> the move controls (Add & Remove) are disabled, I need them to be enabled.
--
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, 4 months
[JBoss JIRA] (RF-12774) a4j:commandLink does not set the styleClass when disabled
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12774?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12774:
----------------------------------
Assignee: Pavol Pitonak
QE, please verify if this is indeed a regression.
> a4j:commandLink does not set the styleClass when disabled
> ---------------------------------------------------------
>
> Key: RF-12774
> URL: https://issues.jboss.org/browse/RF-12774
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.0.Final
> Reporter: Timothy Whitehead
> Assignee: Pavol Pitonak
> Labels: a4j:commandLink, regression, richfaces, styleClass
> Fix For: 4.3.1
>
>
> I upgraded to 4.3.0.Final and when I use a disabled a4j:commandLink it renders with class="class org.richfaces.component.UICommandLink" I believe it was working correctly in 4.2.3.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, 4 months
[JBoss JIRA] (RF-12775) Content jumps when resizing rich:popupPanel with custom header height
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12775?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12775:
-------------------------------
Fix Version/s: 5-Tracking
> Content jumps when resizing rich:popupPanel with custom header height
> ---------------------------------------------------------------------
>
> Key: RF-12775
> URL: https://issues.jboss.org/browse/RF-12775
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.Final
> Reporter: Andrey Zhemoytuk
> Priority: Minor
> Fix For: 5-Tracking
>
>
> Issue is reproducible when popupPanel's header is not of the standard height (22px). E.g. when custom styling applied or bigger font-size is set.
> For example it is reproducible on showcase 'Modal panel example' with the following style set:
> .rf-pp-hdr {
> height: 50px;
> }
> When resizing popup panel vertically - content (popup_content_scroller) 'jumps' extra 28px (50 minus 22).
--
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, 4 months
[JBoss JIRA] (RF-12774) a4j:commandLink does not set the styleClass when disabled
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12774?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12774:
-------------------------------
Labels: a4j:commandLink regression richfaces styleClass (was: a4j:commandLink richfaces styleClass)
> a4j:commandLink does not set the styleClass when disabled
> ---------------------------------------------------------
>
> Key: RF-12774
> URL: https://issues.jboss.org/browse/RF-12774
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.0.Final
> Reporter: Timothy Whitehead
> Labels: a4j:commandLink, regression, richfaces, styleClass
>
> I upgraded to 4.3.0.Final and when I use a disabled a4j:commandLink it renders with class="class org.richfaces.component.UICommandLink" I believe it was working correctly in 4.2.3.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, 4 months
[JBoss JIRA] (RF-12772) rich:fileUpload does not working properly (style, script)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12772?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12772:
-------------------------------
Fix Version/s: 5-Tracking
> 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)
> 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, 4 months
[JBoss JIRA] (RF-12772) rich:fileUpload does not working properly (style, script)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12772?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12772:
-------------------------------
Description:
_<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
was:rich:fileUpload does not working properly and require need to refresh browser when ...
> 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)
> 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
>
> _<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, 4 months
[JBoss JIRA] (RF-12771) Rich:tabPanel - Regression ? Behavior has been changed on getting ID via itemChangeListener
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12771?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12771.
--------------------------------
Resolution: Won't Fix
this change was required in order to implement support for tabs created dynamically with the a4j:repeat component. Your listener code can continue to function as before by using a substring function to parse the clientId for the tab name.
> Rich:tabPanel - Regression ? Behavior has been changed on getting ID via itemChangeListener
> -------------------------------------------------------------------------------------------
>
> Key: RF-12771
> URL: https://issues.jboss.org/browse/RF-12771
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.Final
> Environment: Tested on GlassFish - Mojarra 2.1.17 - Indigo on our ITHB (Integration Technologies Bug Hunter)
> Reporter: Jean ANDRE
>
> In version 4.2.3, under mojarra 2.1.17, we can get the active tab through the listener and the event ItemChangeEvent. This object contains the new and the old tab id without the fully qualified id of the tab, just the id we gave to the tab in our XHTML. ex: TAB_CLIENT-01-1.
> But in version 4.3.0.Final, same JSF implementation, we got a fully qualified ID: ex desktopForm:TAB_CLIENT-01-1.
> That breaks the application because, now, we have to take care about the fully qualified name instead having a simple one. This implementation is less transparent and is not compatible with the previous version.
> Is it a regression ?
--
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, 4 months
[JBoss JIRA] (RF-12770) rich:select not work properly after filtering list
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12770?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12770.
--------------------------------
Resolution: Duplicate Issue
> rich:select not work properly after filtering list
> --------------------------------------------------
>
> Key: RF-12770
> URL: https://issues.jboss.org/browse/RF-12770
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 4.3.0.M3, 4.3.0.Final
> Environment: Win7. Firefox 18, Chrome 24 and IE9. MyFaces 2.1.8. Tomcat 6.0.35
> Reporter: Cristiano Moraes
> Labels: rich:select
>
> With enableManualInput parameter as "true" if I typed some caracters in the field, and then I try to click at any option but the first in the filtered list, component always pick the first.
> How reproduce it:
> It is happing at showcase. Choose rich:select option at menu. At "Select with manual input" field, type 'al'. Alabama and Alaska will show up in the list. Try click in Alaska (second option), Alabama will be select.
> The same happens if you filter the list and select the option using arrows keys and press tab. Otherwise, it will work if you do that but press Enter in the end.
> Change selectFirst parameter value has no effect.
> It works in 4.3.0.M1 release.
> Sorry bad english mistakes. If I was not clear, ask me to clarify.
--
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, 4 months