[JBoss JIRA] Created: (RF-11067) rich:autocomplete popups with suggestions does not reflect the value in input
by Juraj Huska (JIRA)
rich:autocomplete popups with suggestions does not reflect the value in input
-----------------------------------------------------------------------------
Key: RF-11067
URL: https://issues.jboss.org/browse/RF-11067
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: examples
Affects Versions: 4.1.0.Milestone1
Environment: richfaces-showcase
commit 4a534c358ff5903429609ff065fc27bae6fec2c0
Reporter: Juraj Huska
In richfaces-showcase, demo for rich:autocomplete, sample Custom Popup Layouts, popup with suggestions does not reflect what is typed in the input, it always shows the first row of suggestion.
For example when I type v, it should render popup with suggestion Vermont, but instead of it suggest Alabama.
This is corrected when something is chosen, for example Alabama, then suggestions work properly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-10876) rich:toolBar links are barely visible
by Juraj Huska (JIRA)
rich:toolBar links are barely visible
-------------------------------------
Key: RF-10876
URL: https://issues.jboss.org/browse/RF-10876
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: mobile
Affects Versions: 4.0.0.Final
Environment: Demo application - richfaces-showcase-4.0.0.Final-jee6.war
demo - sample - poppupPanel
container - Jboss AS 6.0.0.Final
mobile devices - iPhone 4 - OS version iOS 4.2.1 - browser Safari
iPad1 - OS version iOS 4.2.1 - browser Safari
Nexus S - OS Android 2.3.2
Reporter: Juraj Huska
The link which is on the toolbar in the demo for poppupPanel, in the sample of login panel positioning, is almost invisible with some skins, but it is problem not only on mobile devices but the problem of skinnability in general.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-10880) rich:inplaceSelect no highlighting for options in this select
by Juraj Huska (JIRA)
rich:inplaceSelect no highlighting for options in this select
-------------------------------------------------------------
Key: RF-10880
URL: https://issues.jboss.org/browse/RF-10880
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: mobile
Affects Versions: 4.0.0.Final
Environment: Demo application - richfaces-showcase-4.0.0.Final-jee6.war
container - Jboss AS 6.0.0.Final
mobile devices - iPhone 4 - OS version iOS 4.2.1 - browser Safari
iPad1 - OS version iOS 4.2.1 - browser Safari
Nexus S - OS Android 2.3.2
Reporter: Juraj Huska
There is no highlighting when I touch the option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-10891) rich:dragSource it is not possible to drag an object
by Juraj Huska (JIRA)
rich:dragSource it is not possible to drag an object
----------------------------------------------------
Key: RF-10891
URL: https://issues.jboss.org/browse/RF-10891
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: mobile
Affects Versions: 4.0.0.Final
Environment: Demo-application - richfaces-showcase-4.0.0.Final-jee6.war
container - JBoss AS 6.0.0.Final
mobile devices -
iPhone 4 - OS version iOS 4.2.1 - browser Safari
iPad1 - OS version iOS 4.2.1 - browser Safari
Nexus S - OS Android 2.3.2
Reporter: Juraj Huska
Does not work at all, it is not possible to drag the item.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-10783) showcase wrong description of components
by Juraj Huska (JIRA)
showcase wrong description of components
----------------------------------------
Key: RF-10783
URL: https://issues.jboss.org/browse/RF-10783
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.0.0.Final
Environment: showcase version v.4.0.0-SNAPSHOT SVN r.22194
Reporter: Juraj Huska
There are wrong descriptions of these components:
a4j:region, The button inside the first panel should not work according to the description, but actually it works.
Client Side Validation, JSR 303 Validators, There is written that there should be ajax fallback when user click on the check box, and there is no ajax fallback. But the checkbox has rich:validator tag also, so the behavior is correct, only the text says something different, so either correct the text or the source code of that page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-9306) ComponentControl can't control DataScroller nested in iteration component
by Lukas Fryc (JIRA)
ComponentControl can't control DataScroller nested in iteration component
-------------------------------------------------------------------------
Key: RF-9306
URL: https://jira.jboss.org/browse/RF-9306
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Milestone3
Environment: * RichFaces Core Implementation by JBoss, a division of Red Hat, Inc., version v.4.0.0-SNAPSHOT SVN r.19085
* Metamer: RichFaces Testing Application by JBoss, a division of Red Hat, Inc., version 4.0.0-SNAPSHOT SVN r. 19087
* Java(TM) SE Runtime Environment 1.6.0_20-b02
* Linux 2.6.31-22-generic
* Mojarra 2.0.2-FCS
* Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/9.10 (karmic) Firefox/3.6.8
Reporter: Lukas Fryc
Works great for h:dataTable and ui:repeat,
but not for a4j:repeat or rich:dataTable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-11112) PartialViewContext#getRenderIds() implementation returns empty set
by Bauke Scholtz (JIRA)
PartialViewContext#getRenderIds() implementation returns empty set
------------------------------------------------------------------
Key: RF-11112
URL: https://issues.jboss.org/browse/RF-11112
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Final
Environment: Win7 x64, Eclipse Helios SR2, JBoss AS 6.0.0 Final, RF 4.0.0 Final.
Reporter: Bauke Scholtz
During invoke action phase we would like to retrieve a list of partial render IDs for some specific preprocessing (resetting submitted values for the case they're embedded in another form). Those IDs are normally available by {{PartialViewContext#getRenderIds()}}.
{code}
PartialViewContext partialViewContext = FacesContext.getCurrentInstance().getPartialViewContext();
Collection<String> renderIds = partialViewContext.getRenderIds();
{code}
This works fine in combination with standard JSF components, such as {{<h:commandLink><f:ajax render="foo"/></h:commandLink>}} However, when a RichFaces/A4J command component is been used, such as {{<a4j:commandLink render="foo" />}}, an empty collection is been returned instead. Debugging learns that the {{ExtendedPartialViewContextImpl}} implementation stores them in {{componentRenderIds}} instead of {{renderIds}} and never returns it on {{getRenderIds()}} method. The {{ExtendedPartialViewContextImpl}} also doesn't seem to use {{renderIds}} in a sensible manner anywhere else.
I believe that {{componentRenderIds}} really has to be {{renderIds}} instead.
As far now, we workarounded this by accessing the {{componentRenderIds}} field using reflection.
{code}
Collection<String> renderIds = partialViewContext.getRenderIds();
if (renderIds.isEmpty() && partialViewContext instanceof ExtendedPartialViewContextImpl) {
try {
Field componentRenderIds = ExtendedPartialViewContextImpl.class.getDeclaredField("componentRenderIds");
componentRenderIds.setAccessible(true);
renderIds = (Collection<String>) componentRenderIds.get(partialViewContext);
} catch (Exception e) {
// Handle.
}
}
{code}
However, this introduced a nasty dependency in our code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (RF-10978) Richfaces 4.0 Final fileUpload incomptible with Tomahawk 2.0 1.1.10
by Matt Choate (JIRA)
Richfaces 4.0 Final fileUpload incomptible with Tomahawk 2.0 1.1.10
-------------------------------------------------------------------
Key: RF-10978
URL: https://issues.jboss.org/browse/RF-10978
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Final
Reporter: Matt Choate
Including the Tomahawk 2.0 v1.1.10 library along with Richfaces 4.0 Final causes the Richfaces fileUpload component to break. In the JBoss logs this message appears when rendering the page with the component:
"JSF1091: No mime type could be found for file fileUploadProgress. To resolve this, add a mime-type mapping to the applications web.xml"
Also when monitoring the HTTP traffic in Fiddler I see this entry over and over. Appears to be stuck in some loop
/lsweb/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.712090154203886
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month