I suggest to include suffix it would be useful for the unit

example:

150 sqm, 6 ft and 5 km

To reproduce the error or describe your requirement with a jsfiddle url would be appreciated:

• Fork this with vanilla JS component: https://jsfiddle.net/nosir/kbaxx64s/
• Fork this with React JS component: https://jsfiddle.net/nosir/gLLsrxxf/

If it's mobile related, please specify your devi

e.g. isPassportNumber, etc.

In the current API documentation https://github.com/selectize/selectize.js/blob/master/docs/api.md, under the "items" section, the addItem function does not describe what type or format should the value argument be. It was only after a dug in that I realized it takes a single argument which should be equal to the value attribute of the option tag. I assumed, the type of value argument would

（必填）这个需求解决了什么问题 What problem does this feature solve

?表格内有一个或多个操作按钮，我希望在点击这些按钮后显示loading，并在稍后处理完毕后恢复。

（必填）请填写问题链接来描述为什么无法实现该功能，例如（jsfiddle、codesandbox、jsrun） Reproduction link

?如果要实现这样的功能，就需要使用 $event 把原生DOM 事件传入处理方法，但目前vxe-button好像无法这样传入（表格内用原生非vxe-按钮要单独调样式）。

The README and provided example has:

let suggestions = states().filter((state) => {
    return state.name.toLowerCase().slice(0, inputLength) === inputValue
  })

I think it should be something equivalent to:

const suggestions = states().filter(
  state =>
    inputLength > 0 &&
    state.name.toLowerCase().slice(0, inputLength) === inputValue
)

Otherwise the sug

It would be nice to remove some useless backets on documentation code.

Example:

<TextInputMask
  type={'cpf'}
  value={this.state.cpf}
  onChangeText={text => {
    this.setState({
      cpf: text
    })
  }}
/>

It would be better a example like this

<TextInputMask
  type='cpf'
  value={this.state.cpf}
  onChangeText={text => {
    this.setState({
      

I'm trying to use Hyperform to detect when the form switches between an invalid and valid state so I can switch disabling of the submit button.

If I monitor the "valid" event on the form it keeps getting triggered even though elements within the form are still invalid.

If I run form.checkValidity() on startup each field will indicate an "invalid" event and checkValidity returns false. It see

I think it'll be useful if we can an option to display the chips under the input box instead of at the top as in cases when there are a lot of chips, the input keeps shifting down. it'll be nice to have the input stay at the top and the chips displayed under it. Take a look at the following pic.
![long list](https://cloud.githubusercontent.com/assets/3509404/21218405/714d870a-c2eb-11e6-9be2-c8f61

Hi, in the examples you have a findFilm method that has this line of code:

const regex = new RegExp(${query.trim()}, 'i');

But if you type special characters in the autocomplete textinput (like + and others) it will crash the app. Special characters must be escaped.

An example fix:
const regex = new RegExp(${query.trim().replace(/[-[]/{}()*+?.\^$|]/g, "\$&")}}`, 'i

Instead on Tab-out the original value ist restored.

suggested solution:

unformat (value) {
  var emptyString = typeof value === 'string' && value === ''
  value = parseFloat(value.replace ? value.replace(",",".") : value)
  const toUnformat = emptyString ? this.emptyValue : value
  return accounting.unformat(toUnformat, this.decimalSeparatorSymbol)
}

The condition

Kosovo, which is relatively a new country is missing from the list of countries.

See jsfiddle at http://jsfiddle.net/d5w4jpxq/71/ :

<input name="hashtags" type="tags" pattern="^#" placeholder="#hashtags">

Still allows data that doesn't start with a hash to be entered. The docs mention HTML5 pattern support - should we use pattern to limit the input or should we do this via change events?

Issue: Numbers (Texts) not visible on iPhone simulators and real devices.

Working on Android: Tested on Sony Xperia Z5. Xiaomi A1.
Working on Web: Tested on Chrome 68.0.3440.106 (Official Build) (64-bit), Safari Version 11.1 (13605.1.33.1.2).
Not working: Tested on iPhone (6, 6+, 7)

![image from ios 1](https://user-images.githubusercontent.com/15571610/44145760-53828ac8-a0a6-11e8-9

dialog.trigger = document.getElementById('someElement'); must be typed before document.getElementById('test1').addEventListener('onOk', function() { this.value = x.time.toString(); });

Below is the report after running yarn audit command

yarn audit v1.17.3
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ low │ Regular Expression Denial of Service │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ braces

Issue description

I've came across a proptype warning when passing an int as options key.
focusItem is declared as a string in App.js seems reasonable enough so i think a simple conversion is enough as a think many people may try to pass an int as the option key, my case was passing the product_id from a an api.

I know that this is against the PropTypes use but i think an exception he