Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114)

alice left a comment (WICG/webcomponents#1114)

> I think developer tools should expose "validity" (I think this term is rather confusing, but I can't immediately think of something better).

I think developer tools should definitely have a way of exposing the computed attr-associated element which is used internally, at the very least. Might that be enough for expressing "validity" in this instance, or do you also think we need a coarser, squiggly-line/other error indicator type of UI?

> The caveat to all this is that generally HTML getters do return the computed value where possible.

I think you could make an argument that this is as much (or as little) the computed value as something like `el.htmlFor` is. I think most getters which return elements and pre-date element reflection are read-only?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1114#issuecomment-3393131938
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1114/3393131938@github.com>