Open
Bug 224970
Opened 21 years ago
Updated 2 years ago
"onresize" inline HTML event doesn't function on FRAME
Categories
(Core :: DOM: Events, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: david_vozza, Unassigned)
Details
(Keywords: testcase)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Simply putting an "onresize" inline HTML event into a FRAME element doesn't
function. To test this behaviour I have put an alert inside event.
I know that onresize is not compliant with W3C spec, but on Gecko DOM Reference
it results as supported.
Reproducible: Always
Steps to Reproduce:
1. Put an "onresize" inline HTML event into a FRAME element
2. Raise event
Actual Results:
It doesn't function
Expected Results:
It should support an onresize event when a frame is resized.
|
Reporter | |
Comment 1•21 years ago
|
||
|
||
Comment 2•21 years ago
|
||
I believe we only support onresize events on the window object being resized...
(though we could propagate it up to the frame like we do onload events, I guess).
|
||
Comment 3•21 years ago
|
||
Actually, a frame can be set a resize eventListener in the frameset document. As
long as all document share the same domain name, this will work. So there is a
workaround working here.
I think this bug is more a question of loose or strict compliance with HTML 4.
onresize is not a valid HTML 4 event attribute for <frame>. OTOH, onresize is
not a valid HTML 4 event attribute for <body> either and Mozilla
supports/renders it anyway.
|
||
Comment 4•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
|
|
||
Comment 5•19 years ago
|
||
> a frame can be set a resize eventListener in the frameset document. As
> long as all document share the same domain name, this will work.
Demo:
http://www.gtalbot.org/BugzillaSection/FramesetMetaTestCase.html
Instructions: just resize the top frame.
|
||
Comment 7•18 years ago
|
||
|
|
||
Comment 8•18 years ago
|
||
|
||
Updated•15 years ago
|
Assignee: events → nobody
QA Contact: ian → events
Duplicate of bug 224970?
er, bug 227495
|
|
||
Comment 11•7 years ago
|
||
> > a frame can be set a resize eventListener in the frameset document. As
> > long as all document share the same domain name, this will work.
>
> Demo:
>
> http://www.gtalbot.org/BugzillaSection/FramesetMetaTestCase.html
>
> Instructions: just resize the top frame.
That demo stopped working a few years ago due to my negligence. I just updated it and it works as expected (the number of resize events fired in top frame are counted and are reported in the input text) in Firefox 55.0.2, in Firefox 57.0a1 buildID=20170831145413, in Chrome 60.0.3112.113 and in Chrome 62.0.3198.0.
Can anyone report if it works as expected in Edge 15 (or Edge 16) and in Safari 10.1.2 (or better)?
|
||
Comment 12•7 years ago
|
||
Yes, it works for me in Safari 10.1.2 (and tech preview 38), as well as Edge 15.
|
||
Updated•7 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•