Re: [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041)

> I'm not sure the use cases warrant a sophisticated observer object like StyleSheetObserver

The only benefits of a special observer class as proposed that I see are:

1.   If we want the ability to finesse how the observing should take place, including any filtering abilities that may become available, that could be better handled in the low level code
2.  Be able to specify to include monitoring for CSS rules adjusted via JavaScript via a single unified API.

But I think even if such needs become pressing in the future, we could add that on (a StyleSheetObserver).  

The simplicity of the suggested alternative I think not only makes sense from the "baby steps" point of view, but even from a developer point of view, it is a simpler API, so if none of that finessing is needed, providing the developer a shorter path to what they need would always be useful.

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

Message ID: <WICG/webcomponents/issues/1041/2629025603@github.com>