Hacker News new | past | comments | ask | show | jobs | submit login

This is why the webkit- prefix is nearly worthless. I've had a lot of problems where chrome and safari were rendering prefixed things differently and I couldn't target them individually, because they both use the same prefix. This is the whole point of having the prefixes!



"CSS parsing is the same, though. Slurping up your CSS and turning it into CSSOM’s pretty standard. Yeah, though Chrome accepts just the -webkit- prefix whereas Apple and other ports accept legacy prefixes like -khtml- and -apple-."

Using this information, can you target Chrome with the webkit- prefix and Safari with the apple- prefix? Specifying the apple- prefix after webkit- will ensure that Safari uses that one, right?


You can target them, write -webkit and then -apple, chrome will use webkit, safari will use apple due to the nature of css.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: