I asked Claude to link a text string (“see how it works”) to a section later on in a page. This was Claude’s answer:
On the scroll: the Inspector’s Advanced → ID field (Elements’ normal way to create anchor targets) turns out not to be writable through the automation interface — I tried every plausible property name and filed a field report about the gap. The workaround is clean, though: I created a one-line custom component called “Anchor: How It Works” that renders an invisible <div id="how-it-works"> with a bit of scroll-margin so the section doesn’t land flush against the viewport top, dropped it immediately above the How section, and pointed the “See how it works” button at #how-it-works (same tab). Elements ships with smooth scrolling enabled site-wide, so the button should now glide down to the section.
One step needs your hands in the app, and I want to be straight about why: connecting a button to a modal is done through the Link panel’s “Modal” target type, and that particular link type isn’t reachable through the automation interface (it only speaks URL/page/anchor/resource links — I’ve noted this in the field-report log along with the Advanced ID gap). So: select the hero’s “See how it works” button, open its Link control, and choose Link → Modal → the modal I just added. That replaces the dead #how-it-works text link currently on it, which likely also explains why the anchor never fired — the plain-text link type may not render as a real navigable href in the core button, something the modal approach makes moot.
I’m not sure what it’s trying to do here, and this isn’t something I’m familiar with. I asked it to pop up a video when someone hit that button. This was its response.