Closed Bug 185557 Opened 22 years ago Closed 21 years ago

iframe has no properties accessible through javascript.

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jodie, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5 print() and other methods not accessible from an iframe element through javascript. May be in relation to: Bugzilla bug #159900 Reproducible: Always Steps to Reproduce: 1. Define an iframe element within the document 2. Try to access it via id, or through document.frames[0] Actual Results: All properties seem to be undefined. Expected Results: Given access to the frame methods such as print()
Reporter, could you please provide a testcase and see if this also occurs in Mozilla's latest nightly?
not a phoenix bug I'm sure.
Assignee: blaker → saari
Component: General → DOM Events
Product: Phoenix → Browser
QA Contact: asa → vladimire
Version: unspecified → Trunk
Attached file testcase
Not sure if my testcase is valid 100%, but if it is this is definately a bug. Frame.location should return the location of the frame.
Assignee: saari → jst
Status: UNCONFIRMED → NEW
Component: DOM Events → DOM Level 0
Ever confirmed: true
QA Contact: vladimire → desale
The testcase works fine if I use iframe.src instead of iframe.location. Is iframe.location supposed to be defined?
Mass-reassigning bugs to dom_bugs@netscape.com
Assignee: jst → dom_bugs
The testcase is bogus (the location is on the iframe.contentWindow, not the iframe itself). The original bug report with print() worksforme, so marking so.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: