Web components (best practise) question:
-
Web components (best practise) question:
If I want to "enhance" an input, I've should wrap, right? I can't do `as` (I'm living around 5 years ago…)
i.e.
<rem-upgrade><input></rem-upgrade>
because without/failed js would still give me the input
-
@rem ...and then file another WebKit bug to implement `is`
-
@slightlyoff balls. That `is` really did seem to be a really sensible move. I'd love one to day to know the story behind the resistance.
-
@rem @slightlyoff it's because if you extend a native element with a new property and that property is later added in the browser, that would break the web. Is similar to why is it so bad to mess with native objects prototypes.
-
@loucyx @rem @slightlyoff maybe I’m thick, but… I don’t understand? Everyone except Apple is okay with reserving the is= property and that should be enough, right? The wrappers feel like more of a risk, which is why the dash has to be there so nobody squats on <accordion> but instead has to do <cool-accordion> or am I missing something?
-
-
@slightlyoff @hejsna @loucyx tee rif ick
-