On Wed, May 27, 2026 at 2:17 PM Mike Taylor <[email protected]> wrote: > > On 5/26/26 10:16 a.m., Noam Rosenthal wrote: > > > Debuggability > > No information provided > What's the planned story here?
Oh, sorry, I should have filled this out. This is a valid question that we considered and discussed while developing the feature. The solution is similar to how we approach debuggability for declarative shadow DOM. If there is a patch mismatch (e.g. a <template for=foo> without <?marker name="foo" ?>), the template is attached like a normal template. So having stray `<template for=something>` elements in your document is a sign that something went wrong, similar to stray <template shadowrootmode=open>. This mechanism is generally consistent with not throwing JS errors or console warnings for HTML parsing errors. In addition to this, the devtools team added support for processing instructions in the elements panel, and we've added support for them in `view-source://`. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZEoV8ygSb6DBhaCUc6RWo8cNTkK3EGy%2B0i34XcDzScWg%40mail.gmail.com.
