Closed
Bug 303222
Opened 19 years ago
Closed 19 years ago
{quirks-mode}{inc} cell width incorrect when page Ctrl+reloaded and image size not declared
Categories
(Core :: Layout: Tables, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 275345
People
(Reporter: pentek.imre, Unassigned)
References
()
Details
(Keywords: testcase, Whiteboard: DUP of bug 148621 or bug 227699 or even bug 275345)
Attachments
(1 file)
|
2.12 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; hu; rv:1.7.3) Gecko/20050130 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; hu; rv:1.7.3) Gecko/20050130 Open this document: http://people.inf.elte.hu/pentek_i/doksik/Linux/bugs/Mozilla/03/teszt0001.html try hitting enter when url is written, then try reload and shift+reload too sometimes it happens that the cell containing the image is too big ane leaves a white garbage, but it shouldn't have Reproducible: Always Steps to Reproduce: 1. open the url 2. use shift+reload 3. Actual Results: thast white garbage is present Expected Results: shouldn't draw that white garbage. should have the cell the size 21x21
Comment 1•19 years ago
|
||
I can reproduce reliably, 100% of the time, the problem with Seamonkey 1.0a rv:1.8b4 build 2005080205 under XP Pro SP2 and also with a reduced testcase. The white "garbage" is the table's background color which is inherited from the body element. Imre, there are several workarounds, ways to solve your problem. Simple: If you declare width="21" height="21" for your sarok.png image, then the layout problem disappear. A bit more complex: If you declare table-layout: fixed for your table, then the problem disappear. You also need to quote the src attribute value: the W3C validator would have reported you this issue. I strongly believe this bug is a duplicate.
Component: General → Layout: Tables
OS: Linux → All
Product: Mozilla Application Suite → Core
Whiteboard: DUPEME
Version: unspecified → 1.0 Branch
Updated•19 years ago
|
Version: 1.0 Branch → Trunk
Comment 2•19 years ago
|
||
Load this self-explanatory testcase Instructions: Load (F5 or Ctrl+R) this page and then Reload without using cache (Ctrl+F5 or Ctrl+Shift+R or Shift+Reload) Actual results in Seamonkey 1.0a rv 1.8b4 build 2005080205 and Deer Park alpha 2 rv:1.8b3 build 20050712: The 2nd cell of the 2nd row displays a huge yellow gap on the right side of the rounded corner image Expected results: The 2nd cell of the 2nd row does not display a huge yellow gap on the right side of the rounded corner image and renders the table just as it would after a normal reload (F5 or Ctrl+R) Notes: 1- The yellow color is the background-color of the <body> element. 2- The more there is content in the 3rd cell of the 3rd row, the wider the gap is 3- Somehow, in the process of reloading without cache and rebuilding the layout without cache, the image is get, fetched without using the cache but the constraints on the table are not honored. 4- The layout bug only happens a) in Quirks rendering mode, b) when the image dimensions are unknown and c) when an absolute GET call (bypassing cache) is executed
Comment 3•19 years ago
|
||
Imre, I am/will be resolving this bug as a duplicate (bug 148621 or bug 227699 or even bug 275345). The testcase of attachment 191486 [details] will be hopefully useful over there. Besides the 2 workarounds already mentioned, there are many ways, even simple ones, to work around the layout bug you have: - use <col width="..."> for your table, - (best recommendable solution IMO) use a CSS based template which will trigger web standards compliant rendering mode in all modern browsers
Summary: malformed tables, too big cells → {quirks-mode}{inc} cell width incorrect when page Ctrl+reloaded and image size not declared
Whiteboard: DUPEME → DUP of bug 148621 or bug 227699 or even bug 275345
Comment 4•19 years ago
|
||
Ok. Attachment 169288 [details] is pretty much the same as attachment 191486 [details]. So I know I can not be wrong when resolving this bug as DUPLICATE of bug 275345 *** This bug has been marked as a duplicate of 275345 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•