Skip to main content
Some CSS issues with latest Google Chrome 39 Started by Adrek · · Read 4686 times 0 Members and 2 Guests are viewing this topic. previous topic - next topic

Some CSS issues with latest Google Chrome 39

This texts used to be in one line (and still are in Firefox), latest Google Chrome update (39.0.2171.65 m (64-bit)) broke them



Re: Some CSS issues with latest Google Chrome 39

Reply #1

I noticed something... ehm... crappy in chrome a couple of days ago, but I blamed linux, instead it looks like someone broke the internet... again. :-\

ETA: I can't test it very well because now here it looks good, not sure why... :-\
What resolution are you using?
Are you overriding any font-size by chance?
Bugs creator.
Features destroyer.
Template killer.

Re: Some CSS issues with latest Google Chrome 39

Reply #2

I'm not overriding anything here, adblock (and other plugins) disabled
Screen resolution: 1680x1050

Re: Some CSS issues with latest Google Chrome 39

Reply #3

same for me, I just updated chrome to the latest version (39.0.2171.65 m)


Re: Some CSS issues with latest Google Chrome 39

Reply #4

I tried adding a white-space: nowrap; no the linkbutton class, let me know if the situation improves.
Bugs creator.
Features destroyer.
Template killer.

Re: Some CSS issues with latest Google Chrome 39

Reply #5

Buttons are looking fine now :)

Re: Some CSS issues with latest Google Chrome 39

Reply #6

 emanuele hopes this doesn't break anything else. :P
Bugs creator.
Features destroyer.
Template killer.

Re: Some CSS issues with latest Google Chrome 39

Reply #7

emanuele is wrong  :D

I see the button "Click here to try all unread..." correctly now, but no changes in what phantom posted in the first two screenshots.
sorry for my bad english

Re: Some CSS issues with latest Google Chrome 39

Reply #8

I just tried this on the site so it should be live ...

in index.css remove: text-rendering: optimizeLegibility; (its in the body tag) ... see what that does for those lines.

Re: Some CSS issues with latest Google Chrome 39

Reply #9

Everything went back to normal :)