384473 - table overlaying table on Nascar.com

Status: RESOLVED FIXED

(Core :: Layout, defect)

Description

[u88484]

For a good while now all the head2head columns on Nascar.com are all screwed up and the right portion of the screen is unreadable due to a table overlaying a table (I guess that is how you would describe it). 

Link: http://www.nascar.com/2007/news/features/06/13/dearnhardtjr.head2head.jpate.maumann/index.html

This maybe related also (the special notice on the left hand side which has been like this for months on this site):

https://www.usaa.com/inet/ent_logon/Logon

Comment 1

[Martijn Wargers (dead)]

A regression range might be useful... (Ria?)

Comment 2

[Martijn Wargers (dead)]

Ah, ok, regression from the reflow branch landing.

Comment 3

[Ryan VanderMeulen [:RyanVM]]

WFM. Kurt, can you try visiting the page with a Textframe-enabled build and see if the problem persists? I do my own trunk builds and I can't reproduce it, and my only thought is that I also have the new textframe enabled.

Comment 4

[Martijn Wargers (dead)]

Yeah, this seems to indeed be fixed in the new-textrame builds.

Comment 5

[u88484]

Yeah the nascar.com page is fixed in the new textframe builds but not the USAA page.  If you click the [+] for the special message on the left hand side, it expands over the "benefits of membership" it used to push that column down or a long long time ago.

Comment 6

[Martijn Wargers (dead)]

Minimized testcase would be nice ;)

Comment 7

[u88484]

Attachment: reduced testcase

I reduced it to pretty much as possible so someone can still be able to tell what the bug is.

Comment 8

[Ria Klaassen (not reading all bugmail)]

The drop down seems to be transparent now :).
This has a quite different regression range: 2006-01-25 17 - 2006-01-26 09.

Comment 9

[Martijn Wargers (dead)]

Attachment: testcase2

Ah, yeah, this is something that changed with the frame display lists bug (bug 317375)
But the older builds and branch are actually doing it wrong.
The attached testcase shows the difference.
Compare with branch and current trunk.
The yellow block should overlap over the green block, because it has a higher stack level.
See http://www.w3.org/TR/CSS21/visuren.html#z-index for what the rules are for that.
There was a bug in older builds that when you specified overflow:hidden/auto/scroll on the div, it suddenly got a higher stack level. Bug 317375 fixed that.

Comment 10

[Martijn Wargers (dead)]

This is fixed now that the new textframe has landed.
I hope you find my explanation in comment 9 for the other issue you saw understandable enough.

Comment 11

[u88484]

What does the in-testsuit flag mean? Sorry to ask but there isn't a list of flags with explanations anywhere like there used to be

Comment 12

[Martijn Wargers (dead)]

There isn't? That's not good, I think there really should be something documented somewhere about it.
But if you hover over the "in‑testsuite" word, you should get this explanation:
"
Whether the bug has a testcase in the test suite or not. Set it to "testcase?" if the bug needs a testcase (only set this if the bug actually <em>needs</em> a testcase — not all bugs do, even layout bugs!), set it to "testcase+" if the bug has an appropriate testcase, and set it to "testcase-" if the bug doesn't need an explicit testcase (e.g. for code cleanup bugs). Only QA actively working on test cases in the component should use this keyword.
"

Comment 13

[u88484]

Ahh thanks I never even noticed that...must have been why I couldn't doubleclick to select "in-testsuite" to paste it in my comment.  "Flags" used to be a link to a whole list.