News for hackers. Stuff that matters.
Re:Introducing Custom Elements by jessedhillon on Saturday November 19, 2016 @04:46PM (#12995870)
But in reality, the server would have to emit

  <image-carousel delay="10" images="['...', '...']" end-behavior="cycle">

Thus making us no more free from the details of the component than we were before.
Re:Introducing Custom Elements by abiox on Saturday November 19, 2016 @05:42PM (#12996137)
> no more free from the details

i suppose it depends on what you mean by "the details."

details can be just the inputs required by "the interface" or it can be specifics of "the implementation". the purpose of an interface is often to distance (perhaps even "free", depending) the user from the implementation.

Re:Introducing Custom Elements by rictic on Sunday November 20, 2016 @04:08PM (#13001234)
Parameters aren't implementation details.

Implementation details are stuff like "It's written in framework X so you need to call that framework's init method after document load, then do frameworkX.initCarousel(document.querySelectorAll('.image-carousel')).onEnd((carousel) => carousel.cycle())".