[Webkit-unassigned] [Bug 19359] New: KJS behaves differently from FF2/3 and IE when handling context in catch statement

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jun 2 09:31:25 PDT 2008


http://bugs.webkit.org/show_bug.cgi?id=19359

           Summary: KJS behaves differently from FF2/3 and IE when handling
                    context in catch statement
           Product: WebKit
           Version: 526+ (Nightly build)
          Platform: PC
               URL: http://wiki.ecmascript.org/doku.php?id=es3.1:catch_claus
                    e_context_specification
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ian.eng.webkit at gmail.com


The link describes the behaviors of FF and IE, and here is the example code:
function foo() {
  this.x = 11;
}

x = "global.x";

try {
  throw foo;
} catch(e) {
  print(x) // Should print "global.x"
  e();
  print(x) // Should add x to e
           // (Both IE and Firefox modify the global x)
}

print(x);  // Should print "global.x". IE and Firefox both print 11

Although the spec says the last print statement should print 'global.x', but
FF (>1.5) and IE print out '11'. According to Brendan Eich, ES4 will follow IE
behavior.

Should KJS change its implementation? I don't know any broken websites due to
this.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list