I have a series of buttons. I created buttons, then created another that went near top of page and then positioned it with absolute.
Then reset all the class styles for all states. Clicking on the top button, I edited the Type style so that there is a color on a hover, and giving all such buttons the same starting font, color, padding..... Its not working in Firefox, but other browsers do. When I edit the hover states for a class, it will work.
Is this some sort of bug with Firebox. I did not searching, but I am finding things from 4 years ago. I am using the latest Firefox. Is there a way to fix this? I know I can just assign classes. But I would like to do it the right way - and have a Type class defined.
*I just noticed - it's half working in Chrome. The series of buttons I created BEFORE the button I placed at the top give the correct hover state - but the button I created last, and used to define the style for the Type, does not have a hover.
Firefox hover state not working on...
OK - its back working in Chrome. I deleted the "#" from the top button in the Href. Putting it back gets it to work as normal. But I do not have any hover state still in Firefox when I style the button-link Type for the hover-state.
OK. I believe I see what the problem is. My browsers are showing a hoverstate whenever I change the link. Not all my links are fleshed out, so many use the same link. So only when I was changing the link because I thought the problem might have had something to do with linking to a font-link, it seemed to fix the issue.
However, it seems that the link state css was placed into the stylesheet out of order. I don't know if it was RSD, or the convoluted way in which I started to style the button-links that might confused RSD up too much.
This is my CSS output:
a.link-button:hover { } THEN a.link-button:visited {}
Isn't the convention to be visited, then hover, so hover can always override visited? LVHA? Wouldn't that also apply to button-link elements? I can change the order of those styles, and it fixes the issues (in an editor or the browser developer tools stye editor)
However, it seems that the link state css was placed into the stylesheet out of order. I don't know if it was RSD, or the convoluted way in which I started to style the button-links that might confused RSD up too much.
This is my CSS output:
a.link-button:hover { } THEN a.link-button:visited {}
Isn't the convention to be visited, then hover, so hover can always override visited? LVHA? Wouldn't that also apply to button-link elements? I can change the order of those styles, and it fixes the issues (in an editor or the browser developer tools stye editor)
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.