Fixes issue #59 - #61
Conversation
|
Thanks @jrock2004! I was trying to remember why we limited the attributes to begin with, and I think I figured it out: in many situations, we're copying attributes from an Perhaps instead of a whitelist, we can maintain blacklists in each direction (select->input, input->select)? |
|
Would that be something that a user would have to pass in themselves? Or do we just create such list? If so any ideas on what to blacklist? |
|
Probably something we should provide. Users can override this attribute copy method if they want to anyway. I'm looking at the spec for the select and input elements on MDN. You can check my math, but it looks like the limitations are only in one direction. Any valid attribute on a I'm also wondering whether or not it's wise to copy event handler attributes (like Some research: Attribute blacklist for input-to-select transitionBasically a list of attributes that are unique to input elements.
Attribute blacklist for select-to-input transitionI could not find any attributes that Attributes that are definitely shared
|
I was not sure the meaning behind limiting attr copying to just a few attributes. Removed them all. If there was a reason I could re-write it pull all data attributes and some other known ones