[JBoss JIRA] Created: (RF-10758) Input fields in popupPanel loose focus
by Marc-Christian Schroeer (JIRA)
Input fields in popupPanel loose focus
--------------------------------------
Key: RF-10758
URL: https://issues.jboss.org/browse/RF-10758
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-panels-layout-themes
Affects Versions: 4.0.0.CR1
Environment: Tomcat 7.0.8, MyFaces 2.0.4, RichFaces 4.0.0-SNAPSHOT, Firefox 3.6.15, InternetExplorer 8
Reporter: Marc-Christian Schroeer
When opening a popupPanel with inputText-components, pressing the tab key to switch between input fields results in the address input field getting the focus. tabindex-attributes do not help this issue. This issue does not exist with Google Chrome browsers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (RF-11427) rich:tab - actionListener
by Jan Papousek (JIRA)
rich:tab - actionListener
-------------------------
Key: RF-11427
URL: https://issues.jboss.org/browse/RF-11427
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Affects Versions: 4.1.0.Milestone2
Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d
Metamer 4.1.0-SNAPSHOT r.22728
Mojarra 2.1.2-FCS
Apache Tomcat 7.0.16
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
Reporter: Jan Papousek
It seems that the actionListener attribute doesn't work.
This can be reproduced in Metamer on page faces/components/richTab/simple.xhtml: after clicking on the tab, the info area in the top right corner should contain text "action listener invoked".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (RF-10277) XML Parsing Error in response due to invalid character in attribute
by Michael Heinen (JIRA)
XML Parsing Error in response due to invalid character in attribute
--------------------------------------------------------------------
Key: RF-10277
URL: https://issues.jboss.org/browse/RF-10277
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.3.3.Final
Environment: richfaces 3.3.3
myfaces 1.2.9
facelets
neko parser 1.9.12
Reporter: Michael Heinen
An ajax response is not updated on clientside if it contains ISO control characters like 'START OF HEADING' (in windows Alt + 01 or U+0001) in attributes of tags.
(see http://www.fileformat.info/info/unicode/char/1/index.htm)
The ajax console shows during rendering:
error[14:57:16,523]: Error parsing XML
error[14:57:16,523]: Parse Error: XML Parsing Error: Invalid unicode character.
The parser error occurs in combination with neko filter if such a special character is used as an attribute value, e.g. as value of an inputText field.
This is caused by a wrong transformation in class org.ajax4jsf.xml.serializer.ToXHTMLStream.
Method ToXHTMLStream.writeAttrString contains following check:
String outputStringForChar = m_charInfo.getOutputStringForChar(ch);
if (null != outputStringForChar)
{
writer.write(outputStringForChar);
}
else if (escapingNotNeeded(ch))
{
writer.write(ch); // no escaping in this case
}
else
{
writer.write("&#");
writer.write(Integer.toString(ch)); //THIS IS CALLED!
writer.write(';');
}
The 'START OF HEADING' control char is transformed to the entity  which results in an parsing error on client side.
The char is correctly processed and displayed in NON-Ajax requests.
The char is correctly processed and displayed in Ajax requests in outputfields (as \u0001).
The char is correctly processed but not displayed in the response if tidy filter is used for ajax requests.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months