Bug 13480

Summary: window.Attr is undefined
Product: WebKit Reporter: Alexey Proskuryakov <ap>
Component: DOMAssignee: Alexey Proskuryakov <ap>
Status: RESOLVED FIXED    
Severity: Normal    
Priority: P2    
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   
URL: javascript:alert(window.Attr)
Bug Depends on:    
Bug Blocks: 4986    
Attachments:
Description Flags
proposed fix hyatt: review+

Alexey Proskuryakov
Reported 2007-04-25 04:06:40 PDT
This causes a problem with bindows.net, which attempts to manipulate Attr.prototype.
Attachments
proposed fix (23.61 KB, patch)
2007-04-25 13:31 PDT, Alexey Proskuryakov 		hyatt: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2007-04-25 13:31:14 PDT
Created attachment 14184 [details] proposed fix Added a bunch of new global constructors. Leaving it to the reviewer to decide whether this is appropriate during stabilization. It seems like we have a terminology problem somewhere. Invoking "new Element" results in a weird error message: "TypeError: Value [object ElementConstructor] (result of expression window.Element) is not a constructor. Cannot be used with new."
Dave Hyatt
Comment 2 2007-05-07 22:07:29 PDT
Comment on attachment 14184 [details] proposed fix r=me
Alexey Proskuryakov
Comment 3 2007-05-08 11:04:17 PDT
Committed revision 21308. Filed bug 13626 for the error message.
Note You need to log in before you can comment on or make changes to this bug.