Button trigger area is limited to top of button... in some cases

[FoundationDesign]

I have a really frustrating situation where ‘some’ buttons on my site can only be clicked at the very top of the button. I checked all my settings and everything is consistent (as far as I can see), but there are inconsistencies in the trigger area.

The development site is here https://staging3.startnow.co.nz/home-2020/

All the buttons in the Home section work perfectly.

In the next section down (Personal Programmes), the ‘contact us for a consultation’ button works, but the 4 buttons above (pathways, purpose, activation, & design) only work when the cursor is in the top 1.3 of the button.

Any help and/or suggestions would be greatly appreciated.

[nabeel]

Hi @fd_admin,

Thank you for reaching out to us. Please inspect the Row that contains “Contact us for a consultation” button. Under Setup set the Gap Width and Gap Height to 1 REM (see screenshot)

Let us know how this goes!

[FoundationDesign]

Thanks for your reply nabeel, but, unfortunately this has made no difference. What is weird, is that the settings are all the same but some button have a full active rollover area and others are confined to the top 3rd of the button.

[christopher]

Hi @fd_admin,

I checked the website and I see that the top and bottom rows interfere with the middle row which is the row containing 4 buttons.

I used the Chrome browser developer toolbar to check the top row. The toolbar highlights the containing tag. Please kindly check and see how it obscures the 4 button area:

I checked the lower row and it has the same problem:

Now, I am not sure if the problem is the top/bottom rows or the 4 button row itself. You can test that. Please kindly install this plugin and use it to duplicate the page that you have so that you can do some tests.

Then use the copied page and try to delete the rows and see the result. That way you can find the problem cause. After you find the culprit. Try to recreate the problematic row and then check on each step to see when the problem comes back. That way you will find the step that causes the problem.

Thank you.

[FoundationDesign]

SOLVED! There were too many Rows/Columns/Elements. I simplified it down to a single Row with a single Column containing multiple Elements. Working fine down.

[christopher]

Perfect! I’m happy that you managed to fix the issue.