google-code-prettify - Project Hosting on Google Code

Last 30 days Dec 30, 2009 issue 104 (IE renders PRE in a single line if "white-space:nowrap") commented on by mikegleasonjr - Yes exactly. The problem occurs on IE7 (only IE version tested). Works on FF3, Chrome, Opera 10 Thanks Yes exactly. The problem occurs on IE7 (only IE version tested). Works on FF3, Chrome, Opera 10 Thanks Dec 30, 2009 issue 104 (IE renders PRE in a single line if "white-space:nowrap") commented on by mikesamuel - Ah. I think we agree then that <pre style="white-space: nowrap">foo bar</pre> should render on one line, but the problem you're seeing is that <pre style="white-space: nowrap">foo<br>bar</pre> also renders on one line when it obviously shouldn't? And this happens on IE7 and possibly other browsers? Ah. I think we agree then that <pre style="white-space: nowrap">foo bar</pre> should render on one line, but the problem you're seeing is that <pre style="white-space: nowrap">foo<br>bar</pre> also renders on one line when it obviously shouldn't? And this happens on IE7 and possibly other browsers? Dec 30, 2009 issue 104 (IE renders PRE in a single line if "white-space:nowrap") commented on by mikegleasonjr - prettify transforms the actual content with <spans> and <brs />, but on IE the brak lines has no effects... I think it's due to a innerHTML bug: http://stackoverflow.com/questions/195363/inserting-a-newline-into-a-pre-tag-ie- javascript prettify transforms the actual content with <spans> and <brs />, but on IE the brak lines has no effects... I think it's due to a innerHTML bug: http://stackoverflow.com/questions/195363/inserting-a-newline-into-a-pre-tag-ie- javascript Dec 30, 2009 issue 104 (IE renders PRE in a single line if "white-space:nowrap") commented on by mikegleasonjr - I forgot to mention that <br /> has no effect, hence no line breaks in IE. I forgot to mention that <br /> has no effect, hence no line breaks in IE. Dec 30, 2009 issue 104 (IE renders PRE in a single line if "white-space:nowrap") commented on by mikesamuel - Isn't that correct? Newlines in white-space:pre tags should be treated as spaces according to my reading of the CSS2.1 spec. From http://www.w3.org/TR/CSS21/text.html#white-space-prop : nowrap This value collapses white space as for 'normal', but suppresses line breaks within text. Isn't that correct? Newlines in white-space:pre tags should be treated as spaces according to my reading of the CSS2.1 spec. From http://www.w3.org/TR/CSS21/text.html#white-space-prop : nowrap This value collapses white space as for 'normal', but suppresses line breaks within text. Dec 30, 2009 issue 105 (The link to the Haskell extension in README.html is incorrec...) changed by mikesamuel - Thanks much for pointing that out. Fixed at revision 97. Status: Fixed Owner: mikesamuel Thanks much for pointing that out. Fixed at revision 97. Status: Fixed Owner: mikesamuel Dec 30, 2009 r97 (fixed issue 105: typos in README.html) committed by mikesamuel - fixed issue 105 : typos in README.html fixed issue 105 : typos in README.html Dec 29, 2009 issue 105 (The link to the Haskell extension in README.html is incorrec...) reported by wei.hoo - The link is in the following sentence: And similarly for CSS, Haskell, Lua, OCAML, SML, F#, Visual Basic, SQL, Protocol Buffers, and WikiText.. The URL should be http://code.google.com/p/google-code- prettify/source/browse/trunk/src/lang-hs.js Similarly, the CSS URL should be http://code.google.com/p/google-code- prettify/source/browse/trunk/src/lang-css.js The link is in the following sentence: And similarly for CSS, Haskell, Lua, OCAML, SML, F#, Visual Basic, SQL, Protocol Buffers, and WikiText.. The URL should be http://code.google.com/p/google-code- prettify/source/browse/trunk/src/lang-hs.js Similarly, the CSS URL should be http://code.google.com/p/google-code- prettify/source/browse/trunk/src/lang-css.js Dec 28, 2009 issue 104 (IE renders PRE in a single line if "white-space:nowrap") reported by mikegleasonjr - What steps will reproduce the problem? 1. Use a PRE and put some code in it 2. set style "white-space:nowrap" to the PRE 3. IE is rendering all the code in the PRE in a single line (Please include HTML, not just your source code) see link below What is the expected output? What do you see instead? There should be newlines as in the original HTML What version are you using? On what browser? IE7 Please provide any additional information below. see http://blog.mikecouturier.com/2009/12/google-street-view-with-google- maps_27.html for an exmaple What steps will reproduce the problem? 1. Use a PRE and put some code in it 2. set style "white-space:nowrap" to the PRE 3. IE is rendering all the code in the PRE in a single line (Please include HTML, not just your source code) see link below What is the expected output? What do you see instead? There should be newlines as in the original HTML What version are you using? On what browser? IE7 Please provide any additional information below. see http://blog.mikecouturier.com/2009/12/google-street-view-with-google- maps_27.html for an exmaple Dec 14, 2009 issue 103 (Support for VHDL language) changed by mikesamuel - Thanks much. Added at r96 : http://code.google.com/p/google-code-prettify/source/detail?r=96 with one change to make sure that a \ delimited identifier can follow punctuation without intervening space. Status: Fixed Owner: mikesamuel Thanks much. Added at r96 : http://code.google.com/p/google-code-prettify/source/detail?r=96 with one change to make sure that a \ delimited identifier can follow punctuation without intervening space. Status: Fixed Owner: mikesamuel Dec 14, 2009 r96 (added Le Poussin's VHDL mode) committed by mikesamuel - added Le Poussin's VHDL mode added Le Poussin's VHDL mode Dec 13, 2009 issue 103 (Support for VHDL language) reported by lepoussin - I've wrote a language file to add support for VHDL syntax. A sample VHDL source code is attached too, if needed for tests. Thanks! I've wrote a language file to add support for VHDL syntax. A sample VHDL source code is attached too, if needed for tests. Thanks! Dec 10, 2009 issue 102 (Performance bug with newline replacement on IE 6-7 (patch in...) changed by mikesamuel - Patched in at revision 95. Thanks much. Status: Fixed Owner: mikesamuel Patched in at revision 95. Thanks much. Status: Fixed Owner: mikesamuel Dec 10, 2009 r95 (patched in jacobly's IE performance improvements from issue ...) committed by mikesamuel - patched in jacobly's IE performance improvements from issue 102 patched in jacobly's IE performance improvements from issue 102 Dec 10, 2009 issue 102 (Performance bug with newline replacement on IE 6-7 (patch in...) commented on by jacobly@google.com - I just found out that IE 8 has an actual profiler, a pretty good one. I actually didn't realize earlier that this issue affected IE 8 as well, but it does. With the patch to prettify.js, the time spent is actually fairly well-distributed (without it, there's an extra 24 seconds inside replaceWithPrettyPrintedHtml). Out of a total of 1400ms, the largest contributor was emitTextUpTo at 750ms (including its callees in the time spent). This function was called 25000 times, so that's not too bad. I was actually very impressed with how fast IE 8 is on this page. In all of these cases, the total time spent in a function exceeded the time spent in its callees and in its own body, meaning that a large body of time is spent in IE itself, doing rendering. I've attached a csv file exported from the profiler. I just found out that IE 8 has an actual profiler, a pretty good one. I actually didn't realize earlier that this issue affected IE 8 as well, but it does. With the patch to prettify.js, the time spent is actually fairly well-distributed (without it, there's an extra 24 seconds inside replaceWithPrettyPrintedHtml). Out of a total of 1400ms, the largest contributor was emitTextUpTo at 750ms (including its callees in the time spent). This function was called 25000 times, so that's not too bad. I was actually very impressed with how fast IE 8 is on this page. In all of these cases, the total time spent in a function exceeded the time spent in its callees and in its own body, meaning that a large body of time is spent in IE itself, doing rendering. I've attached a csv file exported from the profiler. Dec 10, 2009 issue 102 (Performance bug with newline replacement on IE 6-7 (patch in...) commented on by mikesamuel - Thanks so much for profiling. It's really hard for me to run one since I can only run IE under VMWare which is a royal PITA. I'll try incorporating this when I get a chance. Do you know where time under IE8 is spent? Thanks so much for profiling. It's really hard for me to run one since I can only run IE under VMWare which is a royal PITA. I'll try incorporating this when I get a chance. Do you know where time under IE8 is spent? Dec 10, 2009 issue 102 (Performance bug with newline replacement on IE 6-7 (patch in...) reported by jacobly@google.com - I noticed that on extremely large files - say, 3000 lines of code inside a single <code> tag - IE 6 and 7 spend the vast majority of rendering time replacing <br>s with \r\n after the rest of the markup has occurred. By choosing the appropriate newline style inside recombineTagsAndDecoration, we can eliminate the replacement step at the end. I've attached a patch that implements this. On the aforementioned 3kloc test file, it reduces IE7 rendering time on my computer from 40s to 10s, with similar results for IE6. I noticed that on extremely large files - say, 3000 lines of code inside a single <code> tag - IE 6 and 7 spend the vast majority of rendering time replacing <br>s with \r\n after the rest of the markup has occurred. By choosing the appropriate newline style inside recombineTagsAndDecoration, we can eliminate the replacement step at the end. I've attached a patch that implements this. On the aforementioned 3kloc test file, it reduces IE7 rendering time on my computer from 40s to 10s, with similar results for IE6. Dec 10, 2009 issue 101 (HTML highlighter bugs on multiple <script> tags) Status changed by mikesamuel - I tried your example and it seems to work at revision 92. Please reopen this issue if upgrading doesn't solve your problem. Status: Fixed I tried your example and it seems to work at revision 92. Please reopen this issue if upgrading doesn't solve your problem. Status: Fixed Dec 08, 2009 issue 101 (HTML highlighter bugs on multiple <script> tags) commented on by mikesamuel - Thanks. http://code.google.com/p/google-code-prettify/source/detail?r=92 may have already fixed the issue. I'll check when I have a spare minute. Thanks. http://code.google.com/p/google-code-prettify/source/detail?r=92 may have already fixed the issue. I'll check when I have a spare minute. Dec 08, 2009 issue 101 (HTML highlighter bugs on multiple <script> tags) commented on by balusc - You can find a live example here: http://meta.stackoverflow.com/questions/32029/syntax-highlighter-bugs-on-multiple-script-tags You can find a live example here: http://meta.stackoverflow.com/questions/32029/syntax-highlighter-bugs-on-multiple-script-tags Dec 08, 2009 issue 101 (HTML highlighter bugs on multiple <script> tags) commented on by mikesamuel - What is the problem you're seeing? What is the problem you're seeing? Dec 08, 2009 issue 101 (HTML highlighter bugs on multiple <script> tags) reported by balusc - To illustrate, multiple non-`script` tags works fine: <element name="value"></element> <element name="value"></element> But multiple `script` tags bugs the highlighter, see the pattern: <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> <script name="value"></script> here's a real world example: <!doctype html> <html lang="en"> <head> <script type="text/javascript" src="http://example.com/one.js"></script> <script type="text/javascript" src="http://example.com/two.js"></script> <script type="text/javascript"> $(document).ready(function() { alert('waa'); }); </script> </head> <body></body> </html> Look like a bug in some sort of XSS filter, if any. To illustrate, multiple non-`script` tags works fine: <element name="value"></element> <element name="value"></element> But multiple `script` tags bugs the highlighter, see the pattern: <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> <script name="value"></script> here's a real world example: <!doctype html> <html lang="en"> <head> <script type="text/javascript" src="http://example.com/one.js"></script> <script type="text/javascript" src="http://example.com/two.js"></script> <script type="text/javascript"> $(document).ready(function() { alert('waa'); }); </script> </head> <body></body> </html> Look like a bug in some sort of XSS filter, if any. Older Dec 04, 2009 issue 100 (Support for "<code>" tag) Status changed by mikesamuel - The code in the third bullet point: 3. Add onload="prettyPrint()" to your document's body tag. at http://google-code-prettify.googlecode.com/svn/trunk/README.html is in a <code> element. You never need to use a lang-* class, you only need to use the prettyprint class. If it doesn't work for you after following those steps, please reopen this bug and tell me what browser you're using. A link to sample code that shows the bug would be great too. Status: Invalid The code in the third bullet point: 3. Add onload="prettyPrint()" to your document's body tag. at http://google-code-prettify.googlecode.com/svn/trunk/README.html is in a <code> element. You never need to use a lang-* class, you only need to use the prettyprint class. If it doesn't work for you after following those steps, please reopen this bug and tell me what browser you're using. A link to sample code that shows the bug would be great too. Status: Invalid Dec 04, 2009 issue 100 (Support for "<code>" tag) reported by eitan.ad...@gmail.com - If you wrap code in a "<code>" and include the requisite class it should also highlight the text. Perhaps <code> should include an implicit "prettyprint" class so you /just/ need to use the lang-* part. If you wrap code in a "<code>" and include the requisite class it should also highlight the text. Perhaps <code> should include an implicit "prettyprint" class so you /just/ need to use the lang-* part. Dec 03, 2009 issue 98 (It's Lua, not LUA) commented on by h.anjos - This time I'll let it slide :) The noun/acronym confusion crops up in the Lua mailing list often enough to prompt the authors to add <a href="http://www.lua.org/about.html#name">a section to Lua's about page</a>. This time I'll let it slide :) The noun/acronym confusion crops up in the Lua mailing list often enough to prompt the authors to add <a href="http://www.lua.org/about.html#name">a section to Lua's about page</a>. Dec 03, 2009 issue 95 (Most worthless POS on the Internet today) Status changed by mikesamuel - Closing for lack of information on how to repeat the issue. Status: Incoherent Closing for lack of information on how to repeat the issue. Status: Incoherent Dec 03, 2009 prettify-3-Dec-2009.zip (Zip of source, tests, and documentation) file uploaded by mikesamuel - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Dec 03, 2009 prettify-small-3-Dec-2009.zip (Minimized source files) file uploaded by mikesamuel - Labels: Type-Archive OpSys-All Labels: Type-Archive OpSys-All Dec 03, 2009 r94 (fix comment) committed by mikesamuel - fix comment fix comment Dec 03, 2009 issue 99 (XML element name does not support periods) changed by mikesamuel - Thanks for the fix. Something this small doesn't really rate a patch :) Applied at revision 93. Please see http://google-code- prettify.googlecode.com/svn/trunk/tests/prettify_test.html#xml Status: Fixed Owner: mikesamuel Thanks for the fix. Something this small doesn't really rate a patch :) Applied at revision 93. Please see http://google-code- prettify.googlecode.com/svn/trunk/tests/prettify_test.html#xml Status: Fixed Owner: mikesamuel Dec 03, 2009 r93 (applied smain's fix for isue 99) committed by mikesamuel - applied smain's fix for isue 99 applied smain's fix for isue 99 Dec 03, 2009 issue 96 (HTML highlightning defect) changed by mikesamuel - Fixed at issue 92 . Please see http://google-code- prettify.googlecode.com/svn/trunk/tests/prettify_test.html#html Status: Fixed Owner: mikesamuel Fixed at issue 92 . Please see http://google-code- prettify.googlecode.com/svn/trunk/tests/prettify_test.html#html Status: Fixed Owner: mikesamuel Dec 03, 2009 r92 (issue 96: fix highlighting of style and script elements that...) committed by mikesamuel - issue 96 : fix highlighting of style and script elements that have no content. issue 96 : fix highlighting of style and script elements that have no content. Dec 03, 2009 issue 95 (Most worthless POS on the Internet today) commented on by sm...@google.com - Copying prettified code from FF 3.5.5 works perfectly fine for me. Maybe try and be more constructive and help resolve the issue you're having instead of make sweeping generalizations about how "impossible" it is (because it isn't). Copying prettified code from FF 3.5.5 works perfectly fine for me. Maybe try and be more constructive and help resolve the issue you're having instead of make sweeping generalizations about how "impossible" it is (because it isn't). Dec 03, 2009 issue 98 (It's Lua, not LUA) changed by mikesamuel - My apologies. I've updated 4 files that used the uppercase form at revision 91 in comments and in documentation. Maybe it could be an acronym for Lua ou astro? Status: Fixed Owner: mikesamuel My apologies. I've updated 4 files that used the uppercase form at revision 91 in comments and in documentation. Maybe it could be an acronym for Lua ou astro? Status: Fixed Owner: mikesamuel Dec 03, 2009 r91 (issue 98: replace uses of "LUA" with "Lua") committed by mikesamuel - issue 98 : replace uses of "LUA" with "Lua" issue 98 : replace uses of "LUA" with "Lua" Dec 03, 2009 issue 99 (XML element name does not support periods) reported by sm...@google.com - What steps will reproduce the problem? 1. Prettify an XML sample that has an element name using a period. For example: <com.example.FooBar> The element coloring ends at the period and the rest is considered an attribute string. I've fixed this for myself with this: [PR_TAG, /^^<\/?[a-z](?:[\w.:-]\w)?\|\/?>$/i], Notice the added period in [\w.:-] Sorry, I'm too lazy to submit a patch. :) What steps will reproduce the problem? 1. Prettify an XML sample that has an element name using a period. For example: <com.example.FooBar> The element coloring ends at the period and the rest is considered an attribute string. I've fixed this for myself with this: [PR_TAG, /^^<\/?[a-z](?:[\w.:-]\w)?\|\/?>$/i], Notice the added period in [\w.:-] Sorry, I'm too lazy to submit a patch. :) Dec 03, 2009 issue 98 (It's Lua, not LUA) reported by h.anjos - Minor quibble, but nonetheless: the name of the language is Lua (as in Moon, in Portuguese), not LUA (as if it was an acronym). Otherwise, great job! Minor quibble, but nonetheless: the name of the language is Lua (as in Moon, in Portuguese), not LUA (as if it was an acronym). Otherwise, great job! Nov 28, 2009 issue 97 (Single quotes breaks Lua syntax highlight) changed by mikesamuel - Thanks for the patch. Applied at revision 90. http://code.google.com/p/google-code-prettify/source/detail?r=90 Status: Fixed Owner: mikesamuel Thanks for the patch. Applied at revision 90. http://code.google.com/p/google-code-prettify/source/detail?r=90 Status: Fixed Owner: mikesamuel Nov 28, 2009 r90 (applied thezbyg's patch to fix a LUA highlighting bug and fi...) committed by mikesamuel - applied thezbyg's patch to fix a LUA highlighting bug and fixed a similar issue in the SQL highlighter applied thezbyg's patch to fix a LUA highlighting bug and fixed a similar issue in the SQL highlighter Nov 28, 2009 issue 97 (Single quotes breaks Lua syntax highlight) reported by thez...@gmail.com - What steps will reproduce the problem? 1. See source code at http://code.google.com/p/gpick/source/browse/trunk/share/gpick/init.lua 2. Syntax highlight breaks at line 7 3. (Please include HTML, not just your source code) What is the expected output? What do you see instead? Expected correct display. Instead, only first single quoted string is displayed correctly, and overall syntax highlight breaks at that point too. What version are you using? On what browser? Tested with current trunk revision r89. Using Google Chrome 4.0.249.11 Please provide any additional information below. Attached a patch to fix this issue What steps will reproduce the problem? 1. See source code at http://code.google.com/p/gpick/source/browse/trunk/share/gpick/init.lua 2. Syntax highlight breaks at line 7 3. (Please include HTML, not just your source code) What is the expected output? What do you see instead? Expected correct display. Instead, only first single quoted string is displayed correctly, and overall syntax highlight breaks at that point too. What version are you using? On what browser? Tested with current trunk revision r89. Using Google Chrome 4.0.249.11 Please provide any additional information below. Attached a patch to fix this issue Nov 23, 2009 issue 96 (HTML highlightning defect) reported by burgestrand - What steps will reproduce the problem? HTML: <pre class="prettyprint lang-html"> <script src="http://static.tumblr.com/4cradrm/oYmknlgzf/jquery.min.js" type="text/javascript"></script> <script src="http://static.tumblr.com/4cradrm/pb1knqm9c/jq-basic.js" type="text/javascript"></script> </pre> What is the expected output? What do you see instead? Expected: Consistent coloring Instead: Inconsistent coloring (from first </script> tag and forward) What version are you using? On what browser? Firefox 3.5.5, Mac OS using “prettify-small-21-May-2009.zip” What steps will reproduce the problem? HTML: <pre class="prettyprint lang-html"> <script src="http://static.tumblr.com/4cradrm/oYmknlgzf/jquery.min.js" type="text/javascript"></script> <script src="http://static.tumblr.com/4cradrm/pb1knqm9c/jq-basic.js" type="text/javascript"></script> </pre> What is the expected output? What do you see instead? Expected: Consistent coloring Instead: Inconsistent coloring (from first </script> tag and forward) What version are you using? On what browser? Firefox 3.5.5, Mac OS using “prettify-small-21-May-2009.zip” Nov 22, 2009 issue 71 (copy paste broken in IE7 (newlines are not preserved)) Status changed by mikesamuel - Fixed at revision 89. Please see http://code.google.com/p/google-code-prettify/source/diff?spec=svn89&r=89&format=side&path=/trunk/src/prettify.js#sc_svn88_1322 for the code that chooses the appropriate linebreak. Status: Fixed Fixed at revision 89. Please see http://code.google.com/p/google-code-prettify/source/diff?spec=svn89&r=89&format=side&path=/trunk/src/prettify.js#sc_svn88_1322 for the code that chooses the appropriate linebreak. Status: Fixed Nov 22, 2009 r89 (issue 71: copy and paste in IE 6, 7, and 8) committed by mikesamuel - issue 71 : copy and paste in IE 6, 7, and 8 issue 71 : copy and paste in IE 6, 7, and 8 Nov 22, 2009 issue 71 (copy paste broken in IE7 (newlines are not preserved)) commented on by justingrantjg - Hi Mike - Take a look at http://stackoverflow.com/questions/136443/why-doesnt-ie7- copy-precode-blocks-to-the-clipboard-correctly/159582#159582 which contains more background info about this fix. The approach detailed in that StackOverflow post is the same as Mel's: /r is the mapping for IE7/IE8, while /r/n is the mapping for IE6. BTW, I've tested this fix on IE8 and it works great. Hi Mike - Take a look at http://stackoverflow.com/questions/136443/why-doesnt-ie7- copy-precode-blocks-to-the-clipboard-correctly/159582#159582 which contains more background info about this fix. The approach detailed in that StackOverflow post is the same as Mel's: /r is the mapping for IE7/IE8, while /r/n is the mapping for IE6. BTW, I've tested this fix on IE8 and it works great. Nov 21, 2009 issue 95 (Most worthless POS on the Internet today) commented on by mikesamuel - Example please. Example please. Nov 21, 2009 issue 95 (Most worthless POS on the Internet today) reported by mara.alexander - What steps will reproduce the problem? 1. Try copying code from a page that uses this crap. 2. 3. (Please include HTML, not just your source code) What is the expected output? What do you see instead? What version are you using? On what browser? Firefox 3.5. Please provide any additional information below. It sucks, I hate it, and it royally pisses me off when code is displayed that is MEANT to be copied from the page, only it can't be, because when I select text then copy it, I end up copying the ENTIRE PAGE OF TEXT because of the damn "prettify" BS. It's impossible to just select that area of code/text. What steps will reproduce the problem? 1. Try copying code from a page that uses this crap. 2. 3. (Please include HTML, not just your source code) What is the expected output? What do you see instead? What version are you using? On what browser? Firefox 3.5. Please provide any additional information below. It sucks, I hate it, and it royally pisses me off when code is displayed that is MEANT to be copied from the page, only it can't be, because when I select text then copy it, I end up copying the ENTIRE PAGE OF TEXT because of the damn "prettify" BS. It's impossible to just select that area of code/text. Nov 11, 2009 r88 (comment fixup and made sure that typeof is recognized as a j...) committed by mikesamuel - comment fixup and made sure that typeof is recognized as a javascript keyword. Added some annotations to make it work with js compilers/minifiers. comment fixup and made sure that typeof is recognized as a javascript keyword. Added some annotations to make it work with js compilers/minifiers. Nov 04, 2009 issue 71 (copy paste broken in IE7 (newlines are not preserved)) commented on by mikesamuel - Mel, can you confirm which line break should be used on which version of IE? Mel, can you confirm which line break should be used on which version of IE? Oct 16, 2009 r87 (added abstract as a java and C# keyword. This was a regress...) committed by mikesamuel - added abstract as a java and C# keyword. This was a regression. added abstract as a java and C# keyword. This was a regression.

issue 101 (HTML highlighter bugs on multiple <script> tags) reported by balusc - To illustrate, multiple non-`script` tags works fine: <element name="value"></element> <element name="value"></element> But multiple `script` tags bugs the highlighter, see the pattern: <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> <script name="value"></script> here's a real world example: <!doctype html> <html lang="en"> <head> <script type="text/javascript" src="http://example.com/one.js"></script> <script type="text/javascript" src="http://example.com/two.js"></script> <script type="text/javascript"> $(document).ready(function() { alert('waa'); }); </script> </head> <body></body> </html> Look like a bug in some sort of XSS filter, if any.

To illustrate, multiple non-`script` tags works fine: <element name="value"></element> <element name="value"></element> But multiple `script` tags bugs the highlighter, see the pattern: <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> and <script name="value"></script> <script name="value"></script> <script name="value"></script> <script name="value"></script> here's a real world example: <!doctype html> <html lang="en"> <head> <script type="text/javascript" src="http://example.com/one.js"></script> <script type="text/javascript" src="http://example.com/two.js"></script> <script type="text/javascript"> $(document).ready(function() { alert('waa'); }); </script> </head> <body></body> </html> Look like a bug in some sort of XSS filter, if any.

Last 30 days

Older