[JBoss JIRA] Created: (RF-5825) Editor: convertion failed in case past converted text in editor.
by Alexander Dubovsky (JIRA)
Editor: convertion failed in case past converted text in editor.
----------------------------------------------------------------
Key: RF-5825
URL: https://jira.jboss.org/jira/browse/RF-5825
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: IE7, Firefox 3.0, Safari 3.2
Reporter: Alexander Dubovsky
Assignee: Nick Belaevski
# Open richfaces-demo on Editor page
# Turn seamTextSupport on
# Copy any text from other external page or doc (e.g. from attached MS Word) and past it into editor
# submit value
Result: convertion error in server log (different for different browsers)
For IE7:
19.01.2009 16:11:22 com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=form:editor[severity=(INFO 0), summary=(An error occurred during conversion html to seam text), detail=(invalid value of attribute 'style' for element 'p')]
For Firefox 3.0:
19.01.2009 16:13:37 com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=form:editor[severity=(INFO 0), summary=(An error occurred during conversion html to seam text), detail=(invalid element 'meta')]
For Safari 3.2:
19.01.2009 16:16:16 com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=form:editor[severity=(INFO 0), summary=(An error occurred during conversion html to seam text), detail=(invalid element 'o')]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (RF-3513) toolTip: "disable" JS API doesn't work for this component.
by Mikhail Vitenkov (JIRA)
toolTip: "disable" JS API doesn't work for this component.
----------------------------------------------------------
Key: RF-3513
URL: http://jira.jboss.com/jira/browse/RF-3513
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: IE6.IE7,Firefox,Opera,Safari(3.2.1.CR5)
Reporter: Mikhail Vitenkov
Assigned To: Nick Belaevski
Step 1. Add toolTip inside any rich component:
<rich:panel style="width:50px; height:50px; background-color: gray">
<rich:toolTip id="tooltipID" value="#{tooltip.value}" ...>
<h:outputLink value="http://www.jboss.com/"><f:verbatim>Link</f:verbatim></h:outputLink>
</rich:toolTip>
</rich:panel>
Step 2. Add "show", "hide", "enable" & "disable" JS API functionality:
<a4j:commandLink onclick="$('formID:tooltipSubviewID:toolTipID').component.show(event)" value="show"></a4j:commandLink>
<a4j:commandLink onclick="$('formID:tooltipSubviewID:toolTipID').component.hide(event)" value="hide"></a4j:commandLink>
<a4j:commandLink onclick="$('formID:tooltipSubviewID:toolTipID').component.enable" value="enable"></a4j:commandLink>
<a4j:commandLink onclick="$('formID:tooltipSubviewID:toolTipID').component.disable" value="disable"></a4j:commandLink>
Step 3. Click on "show" ajax link - toolTip appears.
Step 4. Click on "disable" ajax link - toolTip disappear just after delay, defined in hideDelay attribute.
Step 5. Click on "show" link again.
Actual behavior:
toolTip appears any way - "disable" JS API doesn't work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (RF-5512) Scrollable DataTable cannot be used when adding @charset statement to css files.
by Rong Tao (JIRA)
Scrollable DataTable cannot be used when adding @charset statement to css files.
--------------------------------------------------------------------------------
Key: RF-5512
URL: https://jira.jboss.org/jira/browse/RF-5512
Project: RichFaces
Issue Type: Bug
Components: portal
Affects Versions: 3.2.2
Environment: windows xp + glassfish v2u2 + jdk 1.6
Reporter: Rong Tao
This is a very strange bug, when I add a statement '@charset "utf-8"' to a css file or the css section of the xhtml file, the Scrollable DataTable becomes very strange and cannot be used, the problems are:
1. the table header is not displayed.
2. scroll bar is not displayed.
3. cannot select any rows.
4. the 1st and 2nd columns are overlap.
Very easy to reproduce: download and deploy the demo scrollableDataTable.xhtml and DataTableScrollerBean.java; then add '@charset "utf-8"' to scrollableDataTable.xhtml, the <style> section of the page should be like this:
<style>
@charset "utf-8";
.scrolls{
width:300px;
height:200px;
overflow:auto;
}
</style>
Refresh the page and you will see the problems.
Not only "utf-8", other charset such as "iso-8859-1" can also cause the issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months