Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

>Promote gracefully higher resolution automatically only if devicePixelRatio is more than 1 and connection is WiFi/3G+ and there's no roaming involved. I guess this is not a use case neither, isn't it?

This is a great use case. However, we found that exposing information about whether an user is on WiFi, 3G, or otherwise using roaming is a great way to track users so we have to come up with some solution that doesn't involve directly exposing such information.

> I also would like to have the freedom to improve inputs as I need for my daily tasks, as well as textareas for editing related tasks and everything else you can do today with builtins.

This is not a use case. We must state what those improvements are. Use cases state end results, not means to get there.

> I'd like to have table rows I can drag and drop and resize accordingly with their content or container

This is a great use case too. It seems like what you want is `draggable` and `dropzone` attributes that's [being deleted from the HTML specification](https://github.com/whatwg/html/issues/2331), and make it work with table rows. We should come up with a better mechanism for drag & drop since this is an area we're facing serious accessibility issues.

> I'd like to have Custom Elements primitives for any element I need so that other libraries using innerHTML don't have to worry about setting up the content and I don't want to listen via MutationOserver all the time to every node 'cause I have connectedCallback and disconnectedCallback to do it and per each element I've defined.

But presumably, those primitives or library need to be compassable? e.g. if you want to make a helper to make an element focusable, and another to make it participate in the form submission, you may want to use both.

In that case, what we need might be something like adding the support to MutationObserver to observe connected/disconnected.

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