HTMLInputProps without ref or key

[giladgray]

Fixes #943

Changes proposed in this pull request:

• HTMLInputProps alias uses InputHTMLAttributes instead of HTMLProps (does not include ref or key)
• remove const { ref, ...htmlInputProps } = inputProps workaround!!
• add TagInput inputRef prop because inputProps does not expose it anymore.

[blueprint-bot]

HTMLInputProps doc

Preview: documentation | landing | table

[giladgray]

❓ question:
Components that compose InputGroup and accept inputProps?: HTMLInputProps & IInputGroupProps* expose inputRef to access the <input> element, but as it stands currently they do not provide a method to access the InputGroup component class instance. Such components could safely support ref: (ref: InputGroup) => void because it's all in a nested object, but should they?

* - most of the select components and Date[Range]Input do this.

[adidahiya]

Such components could safely support ref: (ref: InputGroup) => void because it's all in a nested object, but should they?

no, we don't need it yet

[giladgray]

agreed that we don't need a way to ref the InputGroup -- ref'ing the <input> is the useful one.