Talk:Bianca Andreescu career statistics

Width limitations
and I am wondering why we have to add width limitations to the performance timeline table. Because other articles always done that? Because of the tennis guideline? Everything was okay without the extra  or , but once they are limited, the some columns are automactically wrapped, like: etc.
 * 3 / 57
 * 34– 13

Like I said, these additional markups add nothing but to create display issue. It is unreadable, isn't it? If it is the tennis guideline that forces us to do that, I would like to put WP:IAR here as it has prevented us from improving the readability. Unnamelessness (talk) 10:37, 8 September 2019 (UTC) 2003!!2004!!SR!!W–L
 * Actually, as I now look at this, the Tennis Project Guidelines are flexible on this. One chart there has: : Tournament!!1973!!1974!!1975!!1976!!1977!!1978!!1979!!1980!!1981!!1982!!1983!!1984!!1985!!1986!!1987!!1988!!1989!!1990!!1991!!1992!!1993!!1994!!1995–
 * Federer uses the widths, but Nadal does not, so the guideline is flexible on this issue. To be honest, I prefer no widths if feasible. The only trouble arises when the info in a column is wider than the year. Then if someone has say, a 227-123 record in one column and a 1-1 record in another, the column widths are all different sizes... and that looks bad! No font shrinkage if possible either... almost always 100%. Only for players that have a massive amount of years on the tour would we shrink the text size. Fyunck(click) (talk) 17:49, 8 September 2019 (UTC)
 * "Then if someone has say, a 227-123 record in one column and a 1-1 record in another, the column widths are all different sizes... and that looks bad! No font shrinkage if possible either... almost always 100%. Only for players that have a massive amount of years on the tour would we shrink the text size."
 * I don't think we should prior aesthetics over encyclopedia. If we do have to pursuit the perfection, then at least make these columns wider &mdash; wide enough to make sure there is no auto-wrapping that affects the readability. Unnamelessness (talk) 08:56, 9 September 2019 (UTC)
 * Well, aesthetics is quite important, but it shouldn't wrap if we can help it. When does it wrap for you? That 3/57 on her overall win loss doesn't wrap for me unless I crush the chart very tiny. And it does the same without width statements. Same with the 34–13 hardcourt win loss. On my firefox browser it looks perfect. Fyunck(click) (talk) 09:33, 9 September 2019 (UTC)
 * But on my Chrome browser, it just auto-wraps and looks pretty awful, even if I amplify the table unbelievably massive. Unnamelessness (talk) 10:12, 9 September 2019 (UTC)
 * Something might be set wrong in your Chrome browser because when I open it in Chrome (version 76.0.3809.132) it looks perfect! It also looks perfect in Microsoft Edge. We certainly want to make sure the widths are browser compatible, and those are the three browsers we do our best in to make it look good. But for me it looks great in all three. Maybe someone else can check their Chrome browser? If need be we can tweak the widths one or two pixels. Also perhaps your laptop screen settings are not natural size? Fyunck(click) (talk) 17:45, 9 September 2019 (UTC)

The resolution of my laptop is 1920*1080, and the settings of my Chrome brosewer are all initial. But if the widths are less than 42px, there are auto-wrappings. Strangly though, it seems that these width limitations have nothing to do with these columns in Microsoft Edge &mdash; Even if you put 1px there, there is still no wrappings. Unnamelessness (talk) 02:17, 10 September 2019 (UTC)
 * If I change my font setting in chrome to 18 I can get what you are talking about, but at standard 16 (or 17) it works fine. My screen is also 1920*1080. Strange. I asked for input at the help desk. Fyunck(click) (talk) 03:52, 10 September 2019 (UTC)
 * Strange... My font setting in chrome is exactly 16... Unnamelessness (talk) 04:41, 10 September 2019 (UTC)
 * Now I know what's going wrong. The region settings cause the issue. I've already fixed it. Thank you anyway. Unnamelessness (talk) 04:58, 10 September 2019 (UTC)
 * Actually, in case it ever happens to someone else... what region settings were askew? Fyunck(click) (talk) 07:04, 10 September 2019 (UTC)
 * I think I found it buried in Chrome settings. I'm glad all is well. Fyunck(click) (talk) 08:18, 10 September 2019 (UTC)
 * I come from China, so my Chrome broswer automatically pre-set the language region as Chinese, which causes the issue. To aovid that, I have to manually reset the language region as English. Accordingly, I think those who come from non-English speaking country might have the same issue as mine. Unnamelessness (talk) 09:08, 10 September 2019 (UTC)