mycontroller-org / mycontroller-v1-legacy

The Open Source Controller
http://www.MyController.org
Apache License 2.0
147 stars 90 forks source link

Bug: MyController time bad rendering on Chrome #326

Closed RURon closed 6 years ago

RURon commented 7 years ago

I just noticed (as I usually use Firefox), that in Chrome there is a padding/rendering issue in the default MyController time widget - see screenshot. In Firefox this looks flawless. If it makes a difference, I am now using the 0.0.3.Final-SNAPSHOT

grafik

jkandasa commented 7 years ago

@RURon We never faced this kind of issue. Can you clear cache on your browser? Clearing cache helped many people on GUi issues.

http://forum.mycontroller.org/topic/47/gui-caching-issue-problem

RURon commented 7 years ago

I tried with cleared cache (Shift+F5) - no change. I attached a element inspector screenshot - from what I can tell I would say the blue box showing the box model of the div.adf-myct-time.ng-binding shows a too small box for it and that creates the overlap. If I hover the date-element, that box looks better (even though it also not completely covers the element, missing a fex pixels on the bottom end). I wonder if this has to do with a changed monitor DPI (system settings in Windows 7) - I have a UHD screen and with default DPI i have far too small fonts...so I changed it to a higher value and most visual problems stem from that DPI change...When you look at what Chrome calculates as height for the time element, then that is only 16 pixels, whereas Firefox calculates a more real 50 pixels!

This is probably a Chrome bug that you cannot do much about I guess.

grafik

jkandasa commented 7 years ago

@RURon I tried in my computer, But I am unable to reproduce this issue. It may be chrome issue.

Here is the version I am using the following versions, on both browser, it is working perfectly!

OS: Fedora Linux 24 64 bit Chrome: Version 55.0.2883.87 (64-bit) Chromium: Version 51.0.2704.63 Russian Fedora (64-bit)

browser upgrade might help here.

jkandasa commented 6 years ago

@RURon kindly report back if you see this issue.