Page MenuHomePhabricator

Bold lines in wikitables in Chrome
Closed, InvalidPublicBUG REPORT

Description

Hello. Probably I see a bug on Special:GlobalRenameQueue today, this problem is that a bold line appears in wikitable approximately every 4 lines. After, I looked the some pages on wikis. Usually the situation is the same with them.

Exemples on trwiki (https://tr.wikipedia.org/wiki/Sava%C5%9F%C3%A7%C4%B1_(dizi)#Oyuncu_kadrosu_ve_karakterler)
(https://tr.wikipedia.org/wiki/%C4%B0stanbul_S%C3%B6zle%C5%9Fmesi#%C4%B0mzalanmas%C4%B1_ve_y%C3%BCr%C3%BCrl%C3%BC%C4%9Fe_girmesi)

Exemples on enwiki (https://en.wikipedia.org/wiki/Istanbul_Convention)
(https://en.wikipedia.org/wiki/Help:Table)

Especially in the 1st and 2nd lines, bold lines appear from time to time. I only see this issue in Chrome on Windows 10 desktop. There is no problem with Microsoft Edge. The lines on the same pages are the normal size on my mobile phone. There is no problem with the desktop view on the mobile phone. Thanks.

Event Timeline

Aklapper changed the task status from Open to Stalled.May 26 2021, 3:51 PM

Hi, does this happen after making sure that the zoom level in your browser is set to 100%? Does this also happen when using safemode (see https://www.mediawiki.org/wiki/Help:Locating_broken_scripts )? Cannot reproduce.

The page resolution is %100 in Chrome. I use in the lastes version of Chrome. Probably, if the safemode is done as such (https://tr.wikipedia.org/wiki/Sava%C5%9F%C3%A7%C4%B1_(dizi)?safemode=1), I see a bold line in the 2nd and in every 4 lines after it.

Thanks! How HTML tables are actually rendered is up to your web browser's rendering engine and operating system (scaling factor, HiDPI, etc).
This is nothing that can be influenced by MediaWiki, except for if there was any custom CSS to change the border thickness, but this is not the case as you can see when looking at the HTML source code.

Aklapper renamed this task from Bold lines in wikitables to Bold lines in wikitables in Chrome.May 26 2021, 11:35 PM

Since this error happened after the last Chrome updated, I haven't been able to understand fully the reason. Thank you both for your interest.