Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

Hover Effect Bug on Buttons in Firefox After Using the Back Button

  • Problem Description:
    I have created a button using Global Styles in GenerateBlocks, which is designed to have a hover effect: the button is normally white, and upon hovering, the text turns white and the background fills with color, similar to a progress bar effect. This effect works correctly in all browsers except Firefox.

    Expected Behavior:
    Upon returning to the page, the button should retain the defined hover properties, and the text should revert to its original color.

    Actual Behavior:
    Both the button and the text remain white, leading to readability issues (the hover effect persists).

    I would appreciate it if you could look into this issue. Should you need any further information, please let me know.

  • Hi there,

    I can’t seem to replicate the issue from my end from Firefox.

    I may be doing something wrong.

    Can you share a screenshot of the issue from your end?

  • Hi Fernando,

    thank you for your fast reply!

    I can sure share a screenshot.

    Best regards

  • Here’s an article regarding Uploading Screenshots:

    Once you’ve uploaded it, share the link to the uploaded screenshot here(in the Private Information field if you want).

  • src=”” alt=”before and after clicking” />

  • I see. Can you reshare the link to the page in question? I’ll recheck the issue.

    > section “Our products” > Dynamic seating > Learn more
    (The other links are not activated yet)

  • Hi there.

    could you try adding this CSS to your site:
        position: relative;

    It may seem random but it was a previous method to fix this FF bug.

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.