I wonder if for the declarative case, the source location could be stored
with/for the template at parse time, as it is being removed?

On Mon, Dec 25, 2023, 4:35 a.m. Sebastian Zartner <
[email protected]> wrote:

> On Thu, 30 Nov 2023 at 17:33, Nicolas Chevobbe <[email protected]>
> wrote:
>
>> I did not went over the spec yet, but is there any feature we should
>> consider that would help debugging them easily?
>>
>
> The only feature I can imagine is to give a hint in the Inspector whether
> the Shadow DOM was created declaratively or imperatively (via JavaScript).
> So I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1871813 for that.
> For imperatively created Shadow DOM, you could link to the statement in
> the JS code. For that I filed
> https://bugzilla.mozilla.org/show_bug.cgi?id=1871814. For declaratively
> defined Shadow DOM you can't provide such linking, because the related
> <template> element is removed at parse time. I don't know if there's any
> additional thing that could help debugging Declarative Shadow DOM.
>
> Sebastian
>
>
>> On Thursday, November 30, 2023 at 4:57:06 PM UTC+1 Adam Vandolder wrote:
>>
>>> *Summary: *Declarative ShadowDOM is a recent addition to the HTML & DOM
>>> standards that enables the usage of shadow roots in a declarative manner
>>> directly within HTML, without the need for using Javascript and
>>> attachShadow.
>>>
>>> *Bug: *1712140 Implement Declarative Shadow DOM
>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1712140>
>>>
>>> *Specification: *[whatwg/html] Add declarative Shadow DOM features
>>> <https://github.com/whatwg/html/pull/5465>
>>>
>>> *Platforms: *All
>>>
>>> *Pref: *dom.webcomponents.shadowdom.declarative.enabled
>>>
>>> This feature is already shipping in both Blink and Webkit.
>>>
>>> *web-platform-tests: *https://wpt.fyi/results/shadow-dom/declarative
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "[email protected]" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bea4a8e4-d06d-4708-ab03-8600cdda8eecn%40mozilla.org
>> <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bea4a8e4-d06d-4708-ab03-8600cdda8eecn%40mozilla.org?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> [email protected]" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAERejNYJHBjXBdBWs6arL3O8bvO6zaxvhQ9i_pUDC4CCqY5XVg%40mail.gmail.com
> <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAERejNYJHBjXBdBWs6arL3O8bvO6zaxvhQ9i_pUDC4CCqY5XVg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CALr9EBDF-mANk12K%2B5J92oLjZHNCEjWjpGgPFCGPi-oy1zrD-Q%40mail.gmail.com.

Reply via email to