search

nightingale-media-player / nightingale-website

development of web templates, php for other stuff
http://www.getnightingale.com
GNU General Public License v2.0
9 stars 4 forks source link

Nav Bar Highlight Issue on Chrome v17.0.963 #6

Closed ilikenwf closed 12 years ago

ilikenwf commented 12 years ago

Screenshot:

error

I've seen this on Windows, I haven't had a chance to try under Linux yet...but FYI. It happens when any of the pages are loaded/selected.

phoerious commented 12 years ago

Strange issue, doesn't occur in Firefox, but at least happens reliably. Also reproducible in Chromium 18 on Sabayon Linux.

phoerious commented 12 years ago

border-radius is the cause for this. Chrome is unable to apply border-radius without affecting the background color as it seems.

I'd say we have to new IE6 for sure. Not the first time this browser makes it all different.

ilikenwf commented 12 years ago

Try using the webkit specific border radius?

http://www.the-art-of-web.com/css/border-radius/ http://muddledramblings.com/table-of-css3-border-radius-compliance/

hnzlmnn commented 12 years ago

I only get this error on windows. On Ubuntu 12.04 Beta with firefox not!

Am 15. Mrz 2012 19:33 schrieb Matt Parnell < reply@reply.github.com

:

Screenshot:

error

I've seen this on Windows, I haven't had a chance to try under Linux yet...but FYI.

Reply to this email directly or view it on GitHub: https://github.com/nightingale-media-player/nightingale-website/issues/6

Mit freundlichen Gren, Malte Heinzelmann

E-Mail: malte.heinzelmann@fechten-in-heidelberg.de Website: www.fechten-in-heidelberg.de

freaktechnik commented 12 years ago

Well, chrome is a bastard. the whole world thinks it's good. But to be honest, the Chrome devs just rush the implementation, while gecko people take some time and test the features out. there is also an issue with inset shadows and border radiusses etc. I don't care about this one :P

Using a webkit specific border radius, since this would break the design. Since the implementation should technically be exactly the same (else the chrome devs are like reeeealy stupid). I habe a workaround in my mind tought, but hey: 1. We develop a gecko app and 2. This is a bug of the rendering engine and so not the web devs problem. Thats why I also don't fix IE stuff.

freaktechnik commented 12 years ago

Fixed by c0e6f02