Re: Minimum viable custom elements

On Wed, Feb 4, 2015 at 12:41 PM, Chris Bateman <chrisb808@gmail.com> wrote:

> Yeah, I had noted in that post that wrapping a native element with a
> custom element was an option - only drawback is that the markup isn't as
> terse (which is generally advertised as one of the selling points of Custom
> Elements). But that doesn't seem like a deal breaker to me, if subclassing
> needs to be postponed.
>
> Chris
>
>
As I pointed out ealier:

<input is="x-foo">

<x-foo><input></x-foo>

seems like barely a ternseness savings worth discussing.



-- 
Brian Kardell :: @briankardell :: hitchjs.com