- From: Andrea Giammarchi <notifications@github.com>
- Date: Wed, 22 Feb 2017 03:03:29 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 22 February 2017 11:04:04 UTC
> If so, what do you want to change about img elements? 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? 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. I'd like to have table rows I can drag and drop and resize accordingly with their content or container, I want a mechanism to be able to setup whatever is placed on the document that is a known type. 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. Are these use cases? -- 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-281637967
Received on Wednesday, 22 February 2017 11:04:04 UTC