PS: here's the correct rendering of the above, captured in Safari:
Workaround for a browser-dependent rendering bug in V3.
Sort:
Jan 3, 2017
0
#4
I had that problem when translating an arcticle with lots of games and text in it.
I just couldn't find the text box when clicking on the
button.
I thought that was maybe because of the text being too big, or having lots of games in it.
2 things.
*It may be zoomed in a lot so it is overflowing.
*Is the first picture taken on the most updated version of chrome?
Jan 3, 2017
0
#7
ChessMusicGirl wrote:
2 things.
*It may be zoomed in a lot so it is overflowing.
*Is the first picture taken on the most updated version of chrome?
No zooming; in any case, decent browsers scale everything (within reason).
The first one was taken with Opera. Chrome does this similarly.
The real problem is that the table, that was pasted into the post, wants to be 708 pixels wide, and there is only 600 pixels of space available. Safari and Firefox do a fairly intelligent scaling of the table cells' widths, while Opera and Chrome apparently do not.
Scrolling on overflow is one way to fix it; I am also quite certain that CSS/JavaScript could be used to do in Opera/Chrome what Safari/Firefox do in their own.
As far as I can tell, Chrome and Opera have problems rendering posts that include wide tables. They render them so that the text overflows to the right of the space assigned to the posts. Here is a snapshot from the bug submission I've sent in moments ago:
I did not do exhaustive testing, but this seems to be reproducible on all operating systems that support Chrome or Opera. On the other hand, Firefox, Safari, and IE all render the tables correctly, by squishing the whitespace so that everything fits nicely.
The workaround described in the above snapshot also seems to work everywhere I tried.