Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)

Another example would be the hamburger menu, which might likely be 1% JavaScript, 10% HTML, 89% CSS.  We know we will need one instance for the top menu.  We *might*, later, need to reuse the menuing capabilities it provides by some pieces of the page, lazily loaded.  Again, seems like we are doubling the payload to accommodate complex scenarios (lots of dynamic content), at the expense of simple, static-ish scenarios.  I'm perfectly fine doing one first, holding off on the other, but I just wanted to provide my use cases (there may be others).

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

Message ID: <WICG/webcomponents/issues/1009/1526078848@github.com>

Received on Thursday, 27 April 2023 17:35:28 UTC