Closed
Bug 142034
Opened 22 years ago
Closed 21 years ago
[ABS POS] CSS: bottom property breaks nested element within a block
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: joelgrimes, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
918 bytes,
text/html
|
Details |
See url - FLASH OBJECT inside DIV positioned from the BOTTOM of the page will
not display.
Also appears to be broken on linux builds.
Is the testcase valid? MSIE also shows the last testcase as a big white square,
but there it in addition contains the "missing image" icon.
|
||
Comment 3•22 years ago
|
||
-> Plugins (?)
Assignee: Matti → beppe
Status: UNCONFIRMED → NEW
Component: Browser-General → Plug-ins
Ever confirmed: true
QA Contact: imajes-qa → shrir
|
||
Comment 4•22 years ago
|
||
Tested this using iframe as well, and the iframe test also failed. I am
attaching a test case with the iframe (commented out is the embed tag example)
What I did notice is if the bottom property is attached to the div, it does not
work. If the property is attached to the ifrmae or the embed (and object if you
want to try that) it does work.
This sounds like it may be a block issue, reassigning to Kevin for help on this one
Assignee: beppe → attinasi
Component: Plug-ins → Layout
QA Contact: shrir → petersen
Summary: bottom style breaks flash → CSS: bottom property breaks nested element within a block
|
|
||
Comment 6•22 years ago
|
||
|
||
Updated•22 years ago
|
Priority: -- → P3
|
||
Updated•22 years ago
|
Keywords: testcase
OS: Windows 2000 → All
Summary: CSS: bottom property breaks nested element within a block → [ABS POS] CSS: bottom property breaks nested element within a block
|
||
Comment 8•22 years ago
|
||
mass reassign to default owner
Assignee: karnaze → table
Component: Layout → Layout: Tables
QA Contact: petersen → madhur
Target Milestone: Future → ---
|
||
Updated•22 years ago
|
Target Milestone: --- → Future
|
||
Comment 9•21 years ago
|
||
This testcase worskforme in a current build. Is this still a problem?
|
Reporter | |
Comment 10•21 years ago
|
||
Confirming. It's now working properly in the 2/16 nightly.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
|
|
||
Comment 11•21 years ago
|
||
Fixed means we know what fixed it....
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
|
||
Updated•21 years ago
|
Status: REOPENED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•