I usually do my CSS (WordPress) webdev in FireFox, but check it in chrome sometimes. I just found that some CSS selectors work in FireFox but fail in Chrome, and the same for adding ":hover" attribute. Anyone else seen Chrome playing by different CSS rules than others?

@worldsendless
No, and hover has been around for so long. Why would they try and screw that up? I really don't like chrome.

Follow

@souldessin to be clear, it wasn't the :hover selector that broke. It was the webdev tool "make it hovered" that worked in FireFox but not the same in Chrome

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.