Remove bottom section

Hi @mesaul,

Thanks for reporting this—it’s a bug, not something you’ve misconfigured, and
I’ve reproduced it.

That section is a fallback: it lists the notes at the bottom of the post so they’re still
reachable for visitors whose browser doesn’t run the plugin’s JavaScript, including screen
reader users. Normally the plugin’s script takes over and hides it, so you never see it.

The clue is that clicking a word jumps you down to it. That only happens when the script
isn’t running at all—when it works, a click expands the note in place and never navigates.
So the visible section is the symptom; the real problem is that
inline-context/build/frontend.js isn’t executing on your pages.

The usual cause, and one that fits “this just started happening”, is a caching or performance
plugin that delays, defers, or combines JavaScript (WP Rocket’s “Delay JavaScript execution”,
LiteSpeed, Autoptimize, Perfmatters, or a host-level optimizer). A JavaScript error from
another plugin or the theme can do the same.

**Try this now:** in your optimization plugin, exclude this file from JS delay/defer/combine
and clear the cache:

inline-context/build/frontend.js

That should restore click-to-expand, and the bottom section will disappear on its own.

If it doesn’t, could you tell me your theme, which caching/optimization plugin you use, and
whether the browser console shows any errors on a post with notes? A link to an affected post
would help too.

One thing to avoid: hiding the section with CSS. It hides the symptom but leaves the script
broken, so the notes still won’t open, and the links now point at a hidden element — which
makes the note content completely unreachable for screen reader and keyboard users. While the script is broken, that section is what’s keeping your notes accessible.

A fix is coming in the next release, in the coming days: the script will initialize properly
even when an optimization plugin loads it late, so you won’t need the exclusion above. I’ll
follow up here when it’s out. Thanks again—this turned up a real accessibility problem I’d
otherwise have missed.

Version 2.8.2 released today that fixes this bug. Thanks for reporting.