ckotzbauer / extended-listbox

A simple to use javascript component as powerful alternative to the HTML <select> tag

Extended Listbox

Extended Listbox is a simple to use javascript component as powerful alternative to the HTML <select> tag. The main problem of <select> tag is that last one isn’t flexible for customization with CSS. Extended Listbox solves this problem. This component creates a list structure based on <div> tags. The configuration is completely in JavaScript. It opens up great possibilities for customization. No jquery is needed.

In addition, this component provides other useful features like a search bar or grouped items.

Supported Browsers

• Edge latest
• Chrome latest
• Firefox latest

Installation

Install with NPM:

npm install extended-listbox

TypeScript definitions are included in the npm package.

Usage

Link the component and a stylesheet from your page.

<!-- include javascript and stylesheet -->
<link href="/path/to/extended-listbox.css" rel="stylesheet">
<script src="/path/to/extended-listbox.js"></script>

Size

Type	Size
Uncompressed, not minified	27,8 KB
Uncompressed, minified	11,3 KB
Compressed (gzip), not minified	5,1 KB
Compressed (gzip), minified	3,3 KB

Documentation

License

Changelog

Contributing

Please refer to the Contribution guildelines.

Code of conduct

Please refer to the Conduct guildelines.

Security

Please refer to the Security process.

extended-listbox's Issues

An in-range update of extract-text-webpack-plugin is breaking the build 🚨

Version 2.1.1 of extract-text-webpack-plugin just got published.

Branch	Build failing 🚨
Dependency	extract-text-webpack-plugin
Current Version	2.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As extract-text-webpack-plugin is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

Release v2.1.1

2.1.1 (2017-06-08)

Bug Fixes

• add a not null check for the content property before throwing error (#404) (58dd5d3)
• loader: rm unnecessary this.cacheable (caching) (#530) (c3cb091)
• don't extract from common async chunks (#508) (e595417)
• validation schema (schema-utils) (#527) (dfeb347)

Commits

The new version differs by 13 commits.

• 0271b39 chore(release): 2.1.1
• e595417 fix: don't extract from common async chunks (#508)
• a8ae003 chore(package): fix broken links && update devDependencies (#531)
• c3cb091 fix(loader): rm unnecessary this.cacheable (caching) (#530)
• eaa5236 docs: rm RELEASE.md (#532)
• 671e35e chore(package): update webpack-sources v0.1.0...1.0.1 (#526)
• dfeb347 fix: validation schema (schema-utils) (#527)
• d0e88d0 docs(README): add lead-in description (#517)
• 58dd5d3 fix: add a not null check for the content property before throwing error (#404)
• 6c50d8e Update README.md (#469)
• c63dc04 docs(README): clarify to set allChunks option when using CommonsChunkPlugin (#476)
• c40dc64 chore(package): reduce package size (#482)
• a284f3a docs(README): fix options table formatting (#478)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Regex error when using search bar

When you search inside the listbox and the search term contains control characters you get an invalid regex error.

An in-range update of css-loader is breaking the build 🚨

Version 0.27.2 of css-loader just got published.

Branch	Build failing 🚨
Dependency	css-loader
Current Version	0.27.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As css-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of karma is breaking the build 🚨

Version 1.4.1 of karma just got published.

Branch	Build failing 🚨
Dependency	karma
Current Version	1.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As karma is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v1.4.1

Bug Fixes

• runner: Make process kill timeout configurable (ffaa054), closes #2447
• runner: Make process kill timeout configurable - Fix Build (a128e5c), closes #2447
• runner: Test process kill timeout config (99a1d48), closes #2447

Features

• config: allow config to be a default export (9976dce)

Commits

The new version differs by 12 commits .

• acc997a chore: release v1.4.1
• e4833b7 chore: update contributors
• 9ff095e Merge pull request #2541 from vivganes/devdoc
• adf5532 docs(runner): Document processKillTimeout property
• 0bec015 Merge pull request #2533 from vivganes/dev
• b8b02aa Merge pull request #2537 from mattlewis92/switch-gooks-to-husly
• 27d9b12 Merge pull request #2536 from mattlewis92/default-export-config
• 48dad20 chore: switch from ghooks to husky
• 9976dce feat(config): allow config to be a default export
• 99a1d48 fix(runner): Test process kill timeout config
• a128e5c fix(runner): Make process kill timeout configurable - Fix Build
• ffaa054 fix(runner): Make process kill timeout configurable

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Wrong item is moved

moveUp and moveDown has a bug:

• If there is a item, which is focused then this is moved instead of the selected one.

An in-range update of typescript is breaking the build 🚨

Version 2.3.4 of typescript just got published.

Branch	Build failing 🚨
Dependency	typescript
Current Version	2.3.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

TypeScript 2.3.4

This release includes a new flag for tsserver to specify location of npm for nvm users.

Download:

• npm

Commits

The new version differs by 12 commits.

• 1a579d9 Update LKG
• e023dc3 Merge pull request #16113 from Microsoft/fixNpmLocationWithSpaces
• d7555ed Fix equals
• 47a0a7c Wrap npmLocation if needed
• 47bd5af Allow configurable npmLocation for typingsInstaller (#16084) (#16102)
• d333378 Merge branch 'release-2.3' of https://github.com/Microsoft/TypeScript into release-2.3
• f80ca90 Add project telemetry (#16085)
• fc4d109 Fix build breaks with the instrumenter
• 196aba6 Merge pull request #16051 from Microsoft/PortRulesProviderFixToRelease-2.3
• 9919b58 Updating compiler release version to 2.3.4
• 3b9ef4e Changes from CR feedback
• dcab328 RulesProvider performance improvements

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/jquery is breaking the build 🚨

Version 2.0.46 of @types/jquery just got published.

Branch	Build failing 🚨
Dependency	@types/jquery
Current Version	2.0.45
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/jquery is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of gulp-bump is breaking the build 🚨

Version 2.6.0 of gulp-bump just got published.

Branch	Build failing 🚨
Dependency	gulp-bump
Current Version	2.5.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As gulp-bump is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ bitHound - Code Details

• ❌ bitHound - Dependencies Details

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

[email protected]

• update dependencies to support versioning in xml content d18e56e

Commits

The new version differs by 3 commits .

• 55683fe Support builds for node v6+
• b356dda 2.6.0
• d18e56e Update dep bump-regex for xml content support

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Label Issue

Use new codecov-uploader

https://github.com/codecov/codecov-action
https://docs.codecov.com/docs/codecov-uploader
/kind cleanup

Proposal: Change multiselect behavior

• If multiselect is enabled, multiple items should only be selected if Ctrl-Key is pressed.
• If Ctrl is not pressed, then the behavior is like single selection (all previous selected items would be deselected)

An in-range update of awesome-typescript-loader is breaking the build 🚨

Version 3.0.5 of awesome-typescript-loader just got published.

Branch	Build failing 🚨
Dependency	awesome-typescript-loader
Current Version	3.0.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As awesome-typescript-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 3 commits .

• 02938eb chore(release): 3.0.5
• 7faa258 Merge pull request #376 from sod/feature/update-loader-utils
• 9fbc5b3 update loader-utils to ^1.0.2

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Refactor: Remove JQuery

• Use native DOM api

Demo?

Can you make a demo? this would be helpful for a neat project like this 😃

Dependency Dashboard

This issue provides visibility into Renovate updates and their statuses. Learn more

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore: update dependency path-parse to 1.0.7 [security]

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• deps: update dependency typescript to v4.4.2

---

• Check this box to trigger a request for Renovate to run again on this repository