Bug 50862
| Summary: | REGRESSION: Parse errors on pages using processing.js | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ethan Sherbondy <sherbondye> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Major | CC: | ap, barraclough, ggaren, mdelaney7, msaboff, oliver |
| Priority: | P1 | Keywords: | Regression |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac (Intel) | ||
| OS: | OS X 10.6 | ||
| URL: | http://mariuswatz.com/works/abstract01js/index_auto.html | ||
Ethan Sherbondy
In the past few nightly releases, sites using processing.js have returned "SyntaxError: Parse error" in the WebKit inspector and fail to load.
I've found this to be true across the board, even with the header graphic on the Processing.js homepage: http://processingjs.org/
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Confirmed with r73491.
Oliver Hunt
I suspect it's a regexp parse failure, as there have been no js parser changes now in more than a month..
Alexey Proskuryakov
I'm wondering if this is related to <script type="application/processing"> and then maybe bug 50320.
Gavin Barraclough
This may be a dupe of https://bugs.webkit.org/show_bug.cgi?id=50483, please retest post r73594.
Alexey Proskuryakov
I can no longer reproduce with r76045.