[richfaces-issues] [JBoss JIRA] Updated: (RF-1641) ScrollableDataTableRenderer Emits Iframe Element with no src Attribute

ScrollableDataTableRenderer Emits Iframe Element with no src Attribute ---------------------------------------------------------------------- Key: RF-1641 URL: http://jira.jboss.com/jira/browse/RF-1641 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.2 Environment: All Reporter: atait Assigned To: Alexej Kushunin Fix For: 3.2.0, 3.1.4 The rich:scrollableDataTable is emitting a few HTML iframe elements that have no src attribute. This causes IE6, with default configuration, to post a warning to the user when running over SSL. The reason for this, per Microsoft, is that IE6 is not able to determine if the iframe is using secure or not. Although this issue does not appear to be present in IE7 and Firefox, many web application users are accessing sites (our sites) with IE6. There is a config change that can be made for IE6 to enable mixed content and avoid the warning. However, not an acceptable solution. You will see in the code below that the src attribute is included but later ingored when length is 0 The code from ScrollableDataTableRenderer: writer.startElement("iframe", component); getUtils().writeAttribute(writer, "class", "dr-sdt-substrate"); getUtils().writeAttribute(writer, "frameborder", "0"); getUtils().writeAttribute(writer, "id", convertToString(clientId) + ":hs"); getUtils().writeAttribute(writer, "scrolling", "no"); getUtils().writeAttribute(writer, "src", ""); writer.startElement("br", component); writer.endElement("br"); writer.endElement("iframe"); The code from ComponentUtils: public static void writeAttribute(ResponseWriter writer, String attribute, Object value ) throws IOException { if ( (value != null) && (value.toString().length()!=0) ) { writer.writeAttribute(attribute, value.toString(), attribute ); } } Note that there are two places where the iframe element is written in this class