Most of the time, clicking an element with Lens active starts a capture without any issues. But there are a few specific situations where Lens stops before capturing and tells you why. Here’s what each one means and what to do.
“This element is inside a Web Component” #
If you click an element that lives inside a Web Component (Shadow DOM), Lens shows: “This element is inside a Web Component. Internal styles aren’t accessible through standard CSS. Try picking the outer element.”
No diagnosis is counted. The capture is cancelled before it starts.
Web components use an isolated style scope that browser extensions can’t read through standard CSS APIs. This is a browser-level restriction, not something specific to Lens. The outer wrapper element that contains the Web Component is readable. Try clicking that instead. You may not get the exact property you were looking for, but you’ll get the CSS context of the containing element, which is often where constraints that affect the inner content originate.
If you’re on a site built heavily with web components (some Shopify themes, custom React or Vue builds), you’ll hit this more often. The fix lives at the code level in those cases and requires developer handoff regardless.
“Lens updated while you were capturing” #
If Chrome updated the Lens extension in the background while you had an active capture in progress, the next time you open the popup you’ll see: “Lens updated while you were capturing. Pick your element again.”
No diagnosis was counted. The capture data from before the update is gone. Click the Lens icon, pick your element again, and continue from there.
The picker activates but clicking doesn’t register #
If the element picker activates (your cursor changes) but clicking an element on the page doesn’t start a capture, try refreshing the page first. Extensions that inject code into pages sometimes need a fresh page load to attach correctly, especially on tabs that were open before the extension was installed or updated.
If refreshing doesn’t help, check whether the site has a Content Security Policy that restricts extension scripts. Some sites with strict security policies block extension content scripts from running. There’s no workaround in that case. See Extension Not Capturing Correctly for more troubleshooting steps.
The WordPress admin toolbar #
If you click on the WordPress admin toolbar at the top of the page (the black bar with the site name, edit links, etc.), Lens shows a message and cancels the capture without counting a diagnosis. The admin toolbar has its own isolated CSS scope and diagnosing it isn’t something Lens is designed for. Navigate to the front-end page with the visual problem and pick the element there instead.