devtools

Description When using browser extension DevTools (Chrome/Firefox), Electron or the standalone app together with , starting the component inspector from the devtools UI also toggles the Vite overlay panel on the page, so the two inspectors interfere with each other (see #1004). The client's component inspect handlers unconditionally emit the RPC. That RPC exists to minimize the overlay while inspecting (), which is only meaningful when the devtools itself is embedded in the page (iframe inside the Vite overlay). This PR guards both emits with , so: Embedded (Vite overlay iframe): emits are kept — panel still minimizes during inspection Extension panels (Chrome/Firefox), Electron, standalone: emits are skipped — no more unexpected overlay toggling on any platform fixes #1004 Validation [x] (13/13 turbo tasks) [x] [x] [x] (85/85) [x] Manually verified in Chrome: inspecting from the extension panel no longer opens the Vite overlay

Problem Description When developing a frontend project with both Chrome Vue DevTools and vite-plugin-vue-devtools installed, selecting a component using Chrome Vue DevTools’ “Select component in the page” or inspecting a component triggers the following issues: vite-plugin-vue-devtools automatically opens its Inspector panel, causing interference. It is not possible to fully disable or prevent the in-page Inspector overlay from vite-plugin-vue-devtools. The overlay negatively affects the page interaction experience. Expected Behavior When used together with Chrome Vue DevTools, each Inspector should operate independently without triggering the other. Provide configuration options to completely disable the in-page Inspector overlay from vite-plugin-vue-devtools. Additional Notes The overlay UI displayed on top of the page significantly affects interactions. When testing mobile layouts, this popup may take up a large portion of the screen, and closing the devtools panel might also close the popup unintentionally. https://github.com/user-attachments/assets/e53d9403-ce43-4f49-8d90-efb3667e84e7

Node tags inherit the sans font, so a and an inside a tag label are hard to tell apart. The node label right next to them already uses (Roboto Mono), where the zero carries a dot, so this applies the same class to the tag. Fixes #1124