Last Comment Bug 717819 - position:absolute element inside a table reports wrong offsetParent
: position:absolute element inside a table reports wrong offsetParent
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: DOM: Core & HTML (show other bugs)
: 10 Branch
: x86_64 Windows 7
: -- normal (vote)
: mozilla12
Assigned To: :Ehsan Akhgari (busy, don't ask for review please)
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-12 17:41 PST by T. Brains
Modified: 2012-01-16 04:55 PST (History)
5 users (show)
ehsan: in‑testsuite+
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
Patch (v1) (3.16 KB, patch)
2012-01-13 10:44 PST, :Ehsan Akhgari (busy, don't ask for review please)
bzbarsky: review+
Details | Diff | Review
Patch (v2) (4.60 KB, patch)
2012-01-13 16:05 PST, :Ehsan Akhgari (busy, don't ask for review please)
bzbarsky: review+
Details | Diff | Review

Description T. Brains 2012-01-12 17:41:29 PST
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)

Steps to reproduce:

Per bug 10209, these elements now use the right parent for positioning, but offsetParent still reports the outer block element.
Comment 1 :Ehsan Akhgari (busy, don't ask for review please) 2012-01-13 10:44:45 PST
Created attachment 588456 [details] [diff] [review]
Patch (v1)
Comment 2 Boris Zbarsky [:bz] 2012-01-13 10:59:40 PST
Comment on attachment 588456 [details] [diff] [review]
Patch (v1)

Oh, ok, then!  r=me
Comment 3 :Ehsan Akhgari (busy, don't ask for review please) 2012-01-13 16:05:07 PST
Created attachment 588557 [details] [diff] [review]
Patch (v2)

Oops, we actually do need that code if we're dealing with table frames.
Comment 4 Boris Zbarsky [:bz] 2012-01-13 20:21:58 PST
Comment on attachment 588557 [details] [diff] [review]
Patch (v2)

I assume one of those tests (or some other test) failed when the block was removed completely?  r=me if so
Comment 5 Mozilla RelEng Bot 2012-01-13 20:32:10 PST
Try run for d701fd1f8bbe is complete.
Detailed breakdown of the results available here:
    https://tbpl.mozilla.org/?tree=Try&rev=d701fd1f8bbe
Results (out of 234 total builds):
    success: 173
    warnings: 41
    failure: 20
Builds (or logs if builds failed) available at:
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/eakhgari@mozilla.com-d701fd1f8bbe
Comment 6 :Ehsan Akhgari (busy, don't ask for review please) 2012-01-14 10:10:43 PST
(In reply to Boris Zbarsky (:bz) from comment #4)
> Comment on attachment 588557 [details] [diff] [review]
> Patch (v2)
> 
> I assume one of those tests (or some other test) failed when the block was
> removed completely?  r=me if so

Yes, they did.
Comment 7 :Ehsan Akhgari (busy, don't ask for review please) 2012-01-14 10:18:56 PST
https://hg.mozilla.org/integration/mozilla-inbound/rev/944eb2cc77d8
Comment 8 Jonathan Kew (:jfkthame) 2012-01-16 04:55:05 PST
https://hg.mozilla.org/mozilla-central/rev/944eb2cc77d8

Note You need to log in before you can comment on or make changes to this bug.