[JBoss JIRA] (RF-13524) the tooltip freezes when changing page.
by Carlos Mauro Cárdenas Fernández (JIRA)
Carlos Mauro Cárdenas Fernández created RF-13524:
----------------------------------------------------
Summary: the tooltip freezes when changing page.
Key: RF-13524
URL: https://issues.jboss.org/browse/RF-13524
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: accessibility, component, component-a4j-core, component-tables
Affects Versions: 4.2.2.Final, 4.0.0.CR1
Environment: Windows Vista, Web Sphere 8.5, Java jdk 1.5, maven
Reporter: Carlos Mauro Cárdenas Fernández
Priority: Critical
I have a tooltip implemented on a main page, but when you click the link tooltip box gets stuck on next page
<h:outputText value="#{it.get(newItem.strCampoNombre)}" rendered="#{newItem.strCampoTipo == '1' or newItem.strCampoTipo == '5' or newItem.strCampoTipo == '4' or newItem.strCampoTipo == '9' or newItem.strCampoTipo == '10' or newItem.strCampoTipo == '11'}" />
<h:outputText value="#{it.get((newItem.strCampoToolTip))}" rendered="#{newItem.strCampoTipo == '8'}" />
<rich:tooltip styleClass="tooltip" layout="block" rendered="#{newItem.strCampoTipo == '8'}" showDelay="500" onhide="false" hideEvent="mouseleave">
<span class="wrap"> <h:outputText value="#{it.get(newItem.strCampoNombre)}" /> </span>
</rich:tooltip>
problem.png
I tried to change the tooltip parameter but didnt find the solution.
--
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
10 years, 10 months
[JBoss JIRA] (RF-13481) Upgrade to Warp 1.0.0.Alpha6
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13481?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak closed RF-13481.
------------------------------
> Upgrade to Warp 1.0.0.Alpha6
> ----------------------------
>
> Key: RF-13481
> URL: https://issues.jboss.org/browse/RF-13481
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha3
>
>
> It seems Warp Alpha6 doesn't suffer from intermittent test issues as much as Alpha5 did (or it can recover).
> My impression comes from running whole test suite without getting stuck on EAP 6.1 and WildFly CR1.
> I will bump to snapshot and we will release as necessary.
--
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
10 years, 10 months
[JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13420:
----------------------------
Issue Type: Bug (was: Enhancement)
> Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged
> ------------------------------------------------------------------------------------------
>
> Key: RF-13420
> URL: https://issues.jboss.org/browse/RF-13420
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 5.0.0.Alpha2
> Environment: Firefox, Chrome
> JBoss AS 7.1.1.Final
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: 5.0.0.Alpha3
>
>
> Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded.
> {code:none}
> 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml.
> {code}
> Steps to reproduce:
> # deploy showcase
> # clean the browser cache
> # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickLi...
> # look for the WARNING in the JBoss AS console
> Notes:
> * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK.
> * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged
--
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
10 years, 10 months