Clicking Terms and Privacy links accept them instead of opening them in child account setup.

To reproduce, visit https://account.churchofjesuschrist.org ... enAccounts and attempt to click the terms and conditions or privacy links. Neither open. Instead, the click is intercepted to accept them. If this isn't fixed, a clever lawyer might find a sympathetic audience.

Google Chrome 126.0.6478.128 (Official Build) (64-bit) (cohort: Control)
Revision ae45fc71651ae70786a0af5755dd747eb2ac1f9d-refs/branch-heads/6478@{#1593}
OS Windows 11 Version 23H2 (Build 22631.3880)
JavaScript V8 12.6.228.21
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

If you're intending this as a bug report to be forwarded to engineering, please use the Feedback link or button on a relevant page. This is a user-to-user discussion forum, so most likely nobody with the ability to influence a fix for the problem will ever see this thread.

Thanks, I didn't see a "feedback" option, but I found "contact support" and submitted there.

If anyone does end up noticing this here first, the problem also exists in the general signup flow found at https://account.churchofjesuschrist.org/register

Are you able to reproduce this when running incognito? Cookie build-up is a known problem that causes odd behavior.

I find it surprising that such an obvious link issue exists unless there's something else in play.

Yes, I had reproduced in incognito. Today I received a response from support to use the feedback tool to submit. When I went to screen record, I found that the issue has since been resolved.

I didn't investigate deeply, but the behavior I had experienced was as if a higher level DOM element was capturing the click event, preventing default, and taking the action to check the box (something one might do to increase the click target for UX purposes while overlooking other implications).

Whether it was more widespread than my system's context, I do not know. Whatever the case, it's working now.