Closed Bug 6946 Opened 25 years ago Closed 25 years ago

(re)flow problem with an aligned/not-aligned table setup

Categories

(Core :: Layout: Tables, defect, P3)

Product:
Core
Component:
Layout: Tables
Platform:
x86
Windows 98
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: hyp-x, Assigned: mjudge)

References

Details

(Whiteboard: [TESTCASE])

Attachments

(1 file)

Testcase (same as in the description)
189 bytes, text/html
Details 
The 1st table in the following example is rendered using its minimal width
the first time the page is loaded (or reloaded).
It takes it's expected size only when I resize the window.

Builds tested are: M5 and 1999052208
---
<html>
<body>
  <table border=3 align=left>
    <tr><td>blablablabla blablablabla</td>
  </table>

  <table border=3>
    <tr><td>foo</td>
  </table>
</body>
</html>
Status: NEW → ASSIGNED
Target Milestone: M9
Whiteboard: [TESTCASE]
I cannot simplify the testcase any more.
I'm duplicating it as an attachment for easier viewing from the browser.

    
  
Target Milestone: M9 → M10

    
    

    
  
Moving to M11

    
    

    
  
*** Bug 10299 has been marked as a duplicate of this bug. ***

    
    

    
  
In a more recent build (Linux 1999-08-16-08-M9) I'm seeing just a quick flash of
the incorrect state before it corrects itself.

    
    

    
  
Re: dbaron's comment
I saw the same behaviour some time ago in a Solaris build too.
I think it may be a (completly different) bug on unix (or on gtk), that it does
a superflous reflow on loading which causes the content to turn right.
On windows it happens only after I resize the window.

    
    

    
  
I'm testing this with 1999-08-30-10 on WinNT 4sp3

I came to test this when I encountered 12783 (yet another bug with left aligned
tables.), and I found I can no longer see this behaviour.

Something has clearly changed (recently) because:
1. The two tables has a few pixel space between them now.
2. If you click below the tables, the left-aligned table gets a blue one-pixel
border.

Is any of those are intentional?
Should I open another bug for case 2?

I'm not marking this worksforme yet.

    
  
Assignee: karnaze → mjudge
Status: ASSIGNED → NEW

    
    

    
  
The only remaining problem I see is the table selection issue. Michael, is this
the intended behavior.

    
  
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED

    
    

    
  
yes this is intentional. if this is a "bad" thing let me know. since a "dead"
space was clicked it looks for the nearest frame to give the "click" to. the
table grabs it and it must be selecting itself. i am resolving this fixed
so someone will opens a new bug on table selection if they want

    
  
Status: RESOLVED → VERIFIED

    
    

    
  
Using 9/16 Apprunner on Win 95, Win NT, Win 98, Mac8.5 and Linux Red Hat 6.0
(Linux 2.2), verified bug fixed.

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: