Current behavior

When showCloseButton: true and the text is long enough the text goes behind the close button.

Expected behavior

The text should avoid the button.

Live demo

https://jsfiddle.net/jn4pozu0/1/

The circular progress component seems to supersede the spinner, but there's no indication in the docs which is the newer/preferred component. Maybe one should be deprecated, or at least marked as such in the docs?

Or do they serve some different purpose? Is it just the difference in animation?

Bug

• Codepen:
  https://codepen.io/timneyens/pen/VwYdbBK

• The steps to reproduce the issue, e.g.:

  1. Focus on the input field in FireFox
  2. Type c, and wait for suggestions to appear
  3. Press test button
  4. Click outside the container to close suggestions

  Observed behaviour: Suggestions stay open

  Expected behaviour: Suggestions should be closed

Migrating from v0 to v1

I think experimentation is the only way to get things right. In v0, we've been experimenting a lot, often with approaches that were controversial by the time we came up with them. Some of them worked. Some others, not so much. I tried to keep the good things in v1, improve the things that could be improved and discard the ones that weren't good at all.

I've been wor

This is a really minor issue, but hopefully will also be an easy fix.

Because of recent physical workspace set up changes, I've been experimenting with docking Optikey to the bottom of my screen (rather than the top, as has been my preference in the past).

With Optikey set up this way (docked to the bottom), the expand dock and collapse dock icons on the mouse keyboard appear to be drawn for

Currently, the documentation site https://dowjones.github.io/react-dropdown-tree-select/ is housed under docs folder.

The advantages of this approach are:

• easier to do at the start of the project
• one package.json for dependencies (easier to manage)
• examples closer to source
• easier to test changes while developing locally

Disadvantages

• biggest one being the confli

Are you reporting a bug?

renderInputComponent is not optional? when it's undefined it should render the default input component. For now I have to do this

if (custom) {
  return (
    <Autosuggest
      {...props}
      renderInputComponent={() => this.customComponent()}
    />
  )
}

return `<Autosuggest  {...props} renderInputComponent={() => this.customComponent()} />`
`

When focusing an active accordion trigger a unique focus style should be available

This should just require a new css focus selector for the button when in the aria-expanded state

Need to tighten up the mobile layout of the site so it's actually nice to look at and easy to read.

Also need to swap to an off canvas nav for mobile

The agg_size parameter is described as integer, but a string works : we can set agg_size for multiple aggregation levels by separating levels with ;. For instance agg_size=1000;100