Closed
Bug 401080
Opened 17 years ago
Closed 17 years ago
-moz-inline-block expands to block on focus if applied on element in table cell
Categories
(Core :: Layout: Block and Inline, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 301072
People
(Reporter: me, Unassigned)
Details
Attachments
(1 file)
277 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.5) Gecko/20061023 SUSE/2.0.0.5-1.1 Firefox/2.0.0.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.5) Gecko/20061023 SUSE/2.0.0.5-1.1 Firefox/2.0.0.5 If you put an element (in my case an anchor) into a table cell and give this anchor the css display value "-moz-inline-block", it is first rendered as expected, but on focus expanded to the whole width of the outside container. There is no way to get the original size back (i.e. removing the focus has no impact). Test case follows. Reproducible: Always
Reporter | ||
Comment 1•17 years ago
|
||
Minimal test case showing a red anchor which expands to the whole yellow table on focus.
Comment 2•17 years ago
|
||
WFM, Firefox trunk on Linux. http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ -> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
-moz-inline-block doesn't even exist anymore on the trunk; only inline-block is supported. But this is probably a duplicate of another bug that was also fixed on the trunk.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Please reopen only if you see problems in trunk builds (nightlies for Firefox 3) or Firefox 3 alphas/betas; Firefox 2.0 is supported only for security fixes, not layout fixes. Probably a duplicate of this bug:
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → DUPLICATE
(In reply to comment #4) > Please reopen only if you see problems in trunk builds (nightlies for Firefox > 3) or Firefox 3 alphas/betas; Firefox 2.0 is supported only for security fixes, > not layout fixes. (or to fix layout bugs that were caused by security fixes)
You need to log in
before you can comment on or make changes to this bug.
Description
•