On Mon, Feb 17, 2014 at 11:03 AM, Edward O'Connor eocon...@apple.comwrote: I think Ryosuke's content.add/remove are a better base layer than content select. In fact, content select is straightforwardly implementable / explainable on top of MO + content.add/remove, but there are several use
Hi everyone, First time caller, long time listener. From what I understand, the browser vendors seem to be bundling style scoped with the Shadow DOM spec. I'd like to start a discussion around decoupling the two and asking that vendors prioritize shipping style scoped over Shadow DOM as a whole.
*claps for sharing JSBin* Would love to see more of this on public-webapps when possible :) On Tue, Apr 22, 2014 at 10:46 AM, Dimitri Glazkov dglaz...@chromium.orgwrote: BTW, here's a jsbin that implements yield/transclude using existing Shadow DOM plumbing: http://jsbin.com/pacim/1/edit
Thanks for the mentioning the Ember issue Chris :) I've filed it here: https://github.com/tildeio/htmlbars/issues/288 On Thu, Feb 5, 2015 at 7:13 AM, Chris Bateman chrisb...@gmail.com wrote: As an example I made a simple input-based Custom Element which prevents alphabetic input, and dropped it
FWIW, we're working to implement what we call named blocks in Ember.js and believe this proposal aligns very closely to what our users have been asking us to build for them. - Erik On Wednesday, April 22, 2015, Tab Atkins Jr. jackalm...@gmail.com wrote: This is literally reinventing Selectors