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

I would try to give a list for most generic and essential questions. Only upon those answered, the full list has a sence.
* should DCE provide completely declarative programming capabilities to build web app, i.e. **declarative web app**?
   * if so, _running with JS disabled_ is answered: yes.
   * if so,  [should template be functionally complete](https://github.com/WICG/webcomponents/issues/997) is answered: yes.
   * if so, _should DCE support the modular development?_ is answered: yes. along with:
       * DCE loaded from page and declared inline and from external URL
       * WC lib with scoped custom registry + tag maps + import maps, compatible with CDN deployment
*  should DCE be effect-free? I.e. its content should be not able to change anything in container.
    *  if so, a bunch of perks for implementers like parallel load and rendering including streaming all the way load-parse-render-diff-merge.
    * if so, there is a need to sync some state with the parent 
* should DCE state be serialize-able and persisted inline?
    *  if so, full hydration support from SSR to off-screen render   

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

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