Posted by member 2112 on 2003-12-02 00:06:50 link
It's easy to see that the problem Firebird is having when rendering LS.net is not a fault with LS.net.
The repeated corner is simply because this table cell has a CSS class with a repeated background. If the class was changed from ...
.tablf { background-image: url(../images/tabs/tab_lightleft.gif); width: 5px;}
... to ...
.tablf { background-image: url(../images/tabs/tab_lightleft.gif) no-repeat; width: 5px;}
... you would only see one corner image but the table cell will still be as wide and push the content over to the right.
I believe the problem is that Firebird is making an assumption about the width of the column before it's recieved all table tags. Perhaps because it's recieving the information too slowly. Which is why when you reload the page it displays correctly, since it already has all the code, it just needs to draw it again.
I believe this problem can easily be corrected by using colgroup and col tags to define the structure of the columns in a table. The user agent will get this information before receiving all the data for the table and therefore won't have to guess the structure as it's rendering it.
The repeated corner is simply because this table cell has a CSS class with a repeated background. If the class was changed from ...
.tablf { background-image: url(../images/tabs/tab_lightleft.gif); width: 5px;}
... to ...
.tablf { background-image: url(../images/tabs/tab_lightleft.gif) no-repeat; width: 5px;}
... you would only see one corner image but the table cell will still be as wide and push the content over to the right.
I believe the problem is that Firebird is making an assumption about the width of the column before it's recieved all table tags. Perhaps because it's recieving the information too slowly. Which is why when you reload the page it displays correctly, since it already has all the code, it just needs to draw it again.
I believe this problem can easily be corrected by using colgroup and col tags to define the structure of the columns in a table. The user agent will get this information before receiving all the data for the table and therefore won't have to guess the structure as it's rendering it.