Closed Bug 24118 Opened 25 years ago Closed 25 years ago

innerWidth property inconsistencies

Categories

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

x86
Windows 98
defect

Tracking

()

VERIFIED DUPLICATE of bug 9606

People

(Reporter: hrunting, Assigned: vidur)

References

()

Details

The innerWidth property is supposed to give the interior dimensions of the
window or frame object (as I understand it).  This shouldn't include
scrollbars, and indeed, Netscape 4.7's implementation ignores the scrollbars
when calculating this value (it might be irrelevant; Netscape renders the
scrollbar space no matter what, it seems).  In Mozilla M12, when accessing this
value, the return is the pixel width of the window including scrollbars, even
though page contents are never rendered under the scrollbar (ie. it is a non-
viewable area).  Since scrollbars aren't always included in the web page's
rendering, this can lead to inconsistencies across a site.  Of course, there's
no way to determine scrollbar width or even presence (it seems, although it can
be set in some instances), so this inconsistency can lead to problems.  I'd
recommend that the width of the scrollbar be removed from the innerWidth
property if the scrollbar is visible.

For reference, please visit http://studio.home.fastolfe.net/.  Without
scrollbars, the two lines in the div objects line up.  Other pages on the site
(try clicking on the 'd' link) which are longer and create scrollbars don't
line up as they should.

I apologize if this bug has already been reported.  The search script
repeatedly returned a server error when I tried to search for information on
this bug.

Please feel free to e-mail with any questions.
Assignee: mccabe → vidur
Component: Javascript Engine → DOM Level 0
QA Contact: rginda → desale
Reassigning to DOM component.
DUPing with existing danm bug. I wish Dan would fix it!

*** This bug has been marked as a duplicate of 9606 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified Dup.
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.