Open
Bug 397393
Opened 18 years ago
Updated 3 years ago
offsetLeft, offsetTop, offsetWidth and offsetHeight are different in <a> tag and the only child tag (like <i>)
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
UNCONFIRMED
People
(Reporter: marcinkadluczka, Unassigned)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.3
Even though both tags covers exactly the same content, they return different offsetHeight.
The offsetHeight for child covers only one line instead of two lines. The offsetHeight for <a> tag is correct in terms of Height (not correct in other values but separate bug submitted on this).
Reproducible: Always
Example for third link in selected papers:
OffParent is the OffsetParent (so both have same one)
BoxAbs is the tuple of GetOffset[Left,Top,Width,Height] but in absolute document position (and converted to pixels from nscoord)
BoxFrameN (N=1,2,3...) are the Frames associated with the DOM element (in case of one frame is the same as BoxAbs) - same absolute tuple as for BoxAbs
<a OffParent="0xfb4ade8" BoxAbs="532, 566, 406, 50" BoxFrame1="532, 566, 113, 25" BoxFrame2="258, 591, 406, 25" onclick="javascript:urchinTracker('papers-FP/Recommending_PohlJCDL')" class="cleanlink" href="paper.php?p=Recommending_PohlJCDL.pdf">
<i OffParent="0xfb4ade8" BoxAbs="532, 566, 406, 25" BoxFrame1="532, 566, 113, 25" BoxFrame2="532, 566, 406, 25">
Recommending Related Papers Based on Digital Library Access Records
</i></a>
Clearly visible problme is with second Frame (continuation frame)
for <a> tag:
BoxFrame2="258, 591, 406, 25" which is correct
and for <i> tag:
BoxFrame2="532, 566, 406, 25" which is wrong in Left, Top
| Reporter | ||
Updated•18 years ago
|
Component: General → Layout
Product: Firefox → Core
Updated•18 years ago
|
QA Contact: general → layout
Comment 1•18 years ago
|
||
How does one actually reproduce the bug? Please attach a testcase that actually shows the problem. Make sure to include the steps to reproduce when you do that, as well as the expected and actual behavior.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•