|
When examining the parsed console output for a build in Google Chrome the hyperlinks generated by the log-parser plugin don't work correctly. The exact same pages / links work fine in FireFox and Internet Explorer.
I did some digging and discovered that the source of the problem is how the latest version of Google Chrome parses the target HTML file. It seems at some point recently Chrome's HTML parser now requires all named HTML anchors to be enclosed in block tags, which is not currently the case with the latest version of this plugin.
For example, the generated HTML from one of my sample log files looks something like this:
<a name="ERROR1"></a><font color="red">Error Message Here</font><br/>
If I hack the HTML and wrap this block in, say, a paragraph tag, the named anchor works as expected, as in:
<p><a name="ERROR1"></a><font color="red">Error Message Here</font></p>
<br/>
Really this seems to be a bug with Google Chrome because so far as I can tell there is nothing in the HTML specification that requires anchor tags to be defined within a block tag, however given that the workaround to this bug - wrapping all console lines in block tags - should be easily implemented in your plugin I thought it may be quicker and easier (not to mention more compatible) if you were to fix your plugin as well.
NOTE: This bug may affect other areas of Jenkins as well, but this is the first place I've noticed it.
|
