Comment #7 on issue 22864 by [email protected]: May failure parsing a
valid PAC script if it doesn't end with a newline
http://code.google.com/p/chromium/issues/detail?id=22864
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=27171
------------------------------------------------------------------------
r27171 | [email protected] | 2009-09-24 21:52:39 -0700 (Thu, 24 Sep 2009)
| 6 lines
Changed paths:
A
http://src.chromium.org/viewvc/chrome/trunk/src/net/data/proxy_resolver_v8_unittest/ends_with_statement_no_semicolon.js
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/proxy/proxy_resolver_v8_unittest.cc?r1=27171&r2=27170
Add an additional unit-test for when PAC script is missing newline.
This variation uses a statement without semi-colon, rather than a comment,
as the last line.
BUG=http://crbug.com/22864
Review URL: http://codereview.chromium.org/238004
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
