Headings check escapes confinement

Is it flagging things as errors outside the specified check areas, or just showing other headings in the little visualizer?

What I am trying to do at the moment is have the page outline visualizer ignore the check roots and show all headings, but for errors in headings to only be flagged if they are within the specified check roots. But that means I'm running the same DOM dive two different ways and have to keep track of which tree I'm using at all times, so errors on my own part would not be surprising...

I wasn't seeing anything for errors outside of the specified container, I just worry it may be confusing for some users to see headings tagged outside of their control, and wanted to make sure it was by design.

Fair enough. The functionality is by design, but maybe I should revisit the design in a future iteration so there is a visual distinction between the editable headings and the template headings. Though in a lot of contexts I just won't know which it is; there are often a lot of template headings within the editable area.

Keeping it as is I think is fine, just making a note someplace in documentation, though this issue may also take care of that. It's not hard to put in some simple ignores if needed.

Oofta; found a real issue in the wild. The caps lock test is escaping confinement.

Fixed in 2.2.9 → .