Closed
Bug 169512
Opened 23 years ago
Closed 22 years ago
object tag doesn't return width or height when displaying image
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
mozilla1.5alpha
People
(Reporter: neil, Assigned: bzbarsky)
References
Details
(Keywords: qawanted, testcase)
Attachments
(1 file)
989 bytes,
text/html
|
Details |
If I use an <object> tag to display an image and I try to read the width and
height, I just get an empty string. When I do the exact same thing with an
<img> tag I get the actual width and height of the image, even if it wasn't
specified.
Reporter | ||
Comment 1•23 years ago
|
||
![]() |
Assignee | |
Comment 2•23 years ago
|
||
I suspect the only reason that .height/.width on image reflects the "actual"
size instead of the attr is for DOM0 reasons....
In any case, making <object> and <img> use the same code here would not be too
hard if we decided we want it.
Comment 3•23 years ago
|
||
http://mozilla.org/quality/ngdriver/suites/dom-html/hobj017.html is a testcase
which sets the height and tries to read the value, It is working fine.
Boris,
you added the qawanted keyword, what are you expecting from QA.
Keywords: testcase
![]() |
Assignee | |
Comment 4•23 years ago
|
||
The point is, for images you can read the "displayed height" without setting the
value manually.
I'm expecting an evaluation of what the spec says on this issue and what our
behavior should be....
Comment 5•23 years ago
|
||
Object is a generic element and can be used for specific elements like "img,
applet, iframe". So i think "object" should have the same behaviour as an
img|applet|iframe.
![]() |
Assignee | |
Comment 6•23 years ago
|
||
Well, those three are inconsistent in how they treat the width/height
properties, as far as I can tell.
Comment 7•23 years ago
|
||
Well, object element being generic of those three elements, it should be
consistant across all these elements.
![]() |
Assignee | |
Comment 9•22 years ago
|
||
Taking this so I can keep track of this. I have sent mail to www-dom@w3.org
requesting clarification (which is what I was requesting QA do, as it
happens.... see comment 4)
Assignee: dom_bugs → bzbarsky
![]() |
Assignee | |
Updated•22 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.5alpha
![]() |
Assignee | |
Comment 10•22 years ago
|
||
This could use a testcase that compares with IE behavior (the testcase at
http://mozilla.org/quality/ngdriver/suites/dom-html/hobj017.html makes IE barf).
Comment 11•22 years ago
|
||
actually... that url works in my ie (tested using 6.0sp1), it gives the expected
result
what does make ie barf for me is the attachment to this bug
![]() |
Assignee | |
Comment 12•22 years ago
|
||
> it gives the expected result
Oh, right. That one actually sets the values... so it's not very useful for
this bug.
![]() |
Assignee | |
Comment 13•22 years ago
|
||
OK, I see no reason to change our behavior, since it follows the DOM spec and IE
apparently has the same behavior we do. So....
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
You need to log in
before you can comment on or make changes to this bug.
Description
•