Bug 22372

Summary: Add a test for HTMLIFrameElement.document
Product: WebKit Reporter: Pam Greene (IRC:pamg) <pam>
Component: DOMAssignee: Pam Greene (IRC:pamg) <pam>
Status: RESOLVED INVALID    
Severity: Normal CC: ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
New test + result none

Pam Greene (IRC:pamg)
Reported 2008-11-19 18:04:52 PST
Test that if HTMLIFrameElement.document exists, it is an alias for HTMLIFrameElement.contentDocument.
Attachments
New test + result (1.65 KB, patch)
2008-11-19 18:10 PST, Pam Greene (IRC:pamg) 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Pam Greene (IRC:pamg)
Comment 1 2008-11-19 18:10:00 PST
Created attachment 25297 [details] New test + result
Sam Weinig
Comment 2 2008-11-19 20:56:43 PST
Are you sure this correct? HTMLIFrameElement.document and HTMLIFrameElement.contentDocument should not point to the same thing as far as I know. HTMLIFrameElement.document should be the document the iframe is in, and HTMLIFrameElement.contentDocument should be the document in iframe.
Darin Adler
Comment 3 2008-11-20 07:45:13 PST
Comment on attachment 25297 [details] New test + result r=me
Pam Greene (IRC:pamg)
Comment 4 2008-11-20 09:26:27 PST
(In reply to comment #2) > Are you sure this correct? No. Recent builds (3.2 and trunk) don't offer HTMLIFrameElement.document at all, and I can't find any additional documentation describing what it used to be. I'll ask the original author of the test why he thought this was the intended behavior. Removing Darin's r+ in the meantime.
Darin Adler
Comment 5 2008-11-20 09:36:14 PST
LOL, sorry I blindly said review+ on this. I remember well when we removed this "document" attribute, and the terrible problems it was causing on many real world websites!
Pam Greene (IRC:pamg)
Comment 6 2008-11-20 09:52:10 PST
Never mind, then. This test is no longer needed.
Note You need to log in before you can comment on or make changes to this bug.