well,seems like there is some bug (?) or some case with Chrome….
just tested with Firefox (both browsers latest versions – no other changes made no where…)
please,take a look at the screenshots…..
Looks fine in Firefox,still meesy in Chrome…..
gonna try your suggestion John,and i’ll update….