Bug 11932 - New Javascript Parser error
Summary: New Javascript Parser error
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 312.x
Hardware: Mac OS X 10.3
: P2 Normal
Assignee: Nobody
URL: http://www.move.com
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-22 10:06 PST by dealscart
Modified: 2007-04-25 06:41 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dealscart 2006-12-22 10:06:58 PST 
App was working with Beta 1 of Atlas (Asp.net Ajax) toolkit. But with RC1 of Atlas toolkit it is getting a parser error here:
 // MicrosoftAjax.js
Function.__typeName="Function";Function.createCallback=function

So it fails on PowerMax running the latest Safari 1.3.2

App still works fine on Mac minis running Safari 2.0.4

It appears that the Javascript parser does not support the new class or prototype syntax. But it was working in Atals beta 1.0 and the issues could be resolved with better parser support for Safari 1.3.X
Comment 1 dealscart 2006-12-22 10:11:23 PST 
Failing with Parser error on PowerMAC (Safari 1.3.2) with this new Javascript syntax:
Function.__typeName="Function";Function.createCallback=function

But how come Safari 2.0.4 supports the syntax on sn Mac mini machine.
Comment 2 David Kilzer (:ddkilzer) 2006-12-22 11:25:26 PST 
Per the Safari User Agent Matrix, Safari 1.3.2 is available on Mac OS X 10.3.9 (Panther):

http://developer.apple.com/internet/safari/uamatrix.html

Safari 1.3.x was released with an updated WebKit framework that closely matched the version of WebKit that was released with Safari 2.0.x on Mac OS X 10.4 (Tiger), but they aren't exact.

My guess is that one of two things is happening:

1. The updated Atlas framework is mis-identifying Safari 1.3.2 and taking a different (incorrect) code path compared to Safari 2.0.x.

2. The slight differences in WebKit between Safari 1.3.2 and Safari 2.0.4 account for the parsing error.

Either way, Apple will be releasing Mac OS X 10.5 (Leopard) in 2007, and at that point Mac OS X 10.3.9 and Safari 1.3.2 will (most likely) no longer be supported.  

You could try filing a Radar bug on https://bugreport.apple.com/, but it's unlikely that Apple will fix this unless it's a critical bug.  Note that you must have an ADC account to file the bug.  You may create a free "online" ADC account on https://connect.apple.com/.
Comment 3 David Kilzer (:ddkilzer) 2006-12-22 11:27:13 PST 
Safari 1.3.2 uses WebKit 312.8.
Comment 4 Alexey Proskuryakov 2007-04-25 06:41:52 PDT 
According to the above comments, this is not a WebKit issue, closing as INVALID. 

The site seems to work fine with ToT at a first glance. Also, there is no MicrosoftAjax.js in Activity window, so the site may have been redesigned since this report was filed.