The Button That Promised to Register But Scrolled the Page: The Invisible Bug in Activation Days

I was reviewing the code for the Activation Days 2026 homepage, the ticketing platform for the outdoor event in Riva del Garda, when I noticed something strange. In the hero section of the page there were two buttons: one said 'View the program' and one said 'Register for the event'. I clicked both of them. Then I clicked them again. Both did exactly the same thing: they scrolled the page down to the program section below.

The first button was correct: a smart link that scrolled to the program. The second button was a copy of the same behavior. Nobody noticed because visually it was perfect: same style, same size, same position, same text. A designer would never have caught it, and a tester who only looks at visual rendering wouldn't either. The bug lived inside the onClick code, where a scroll function had been mistakenly reused instead of a direct link to the /register page.

It happens often when components are copied and adapted quickly. Someone duplicated the program button, changed the text, forgot to change the click function. Nobody tested the actual behavior because everyone was checking Figma or the visual preview. The code was invisible until I opened it.

A user who clicks 'Register for the event' expects to end up on the registration page. If the page scrolls instead, they're confused. They might think the button doesn't work. They might look elsewhere for the registration link, or worse, leave. It's a small bug that costs real conversions and doesn't show up in crash reports.

I fixed it in a minute: I turned the button into a direct link to /register, keeping the style and text identical. Zero visual impact, behavior finally correct. Next time you see a button that promises an action, click it and follow where it takes you. It's just as important as checking how it looks.