Fix #1971 and restore #1837

.eslintrc.js

@@ -0,0 +1,30 @@
+module.exports = {
+    "env": {
+        "browser": true,
+        "es2021": true
+    },
+    "extends": "eslint:recommended",
+    "overrides": [
+    ],
+    "parserOptions": {
+        "ecmaVersion": "latest"
+    },
+    "rules": {
+        "indent": [
+            "error",
+            4
+        ],
+        "linebreak-style": [
+            "error",
+            "windows"
+        ],
+        "quotes": [
+            "error",
+            "double"
+        ],
+        "semi": [
+            "error",
+            "always"
+        ]
+    }
+};

.github/ISSUE_TEMPLATE.md

@@ -6,7 +6,7 @@ that maintainers have limited time to fix issues, triage, and understand
 them.
 
 If you've never done so, please read the
-[guide to reporting issues](https://github.com/selectize/selectize.js/wiki/Reporting-issues-guide)
+[guide to reporting issues](https://github.com/fabienwnklr/selectize.js/wiki/Reporting-issues-guide)
 in the Wiki to help us better understand your issue.
 
 Place an `x` in the checklist steps (`[ ]` becomes `[x]`) to demonstrate

.github/workflows/UpdateContributors.yml

@@ -9,7 +9,7 @@ jobs:
     steps:
       - uses: risadams/contributors-update@v3.1.1
         with:
-          repo: selectize/selectize.js
+          repo: fabienwnklr/selectize.js
           output: CONTRIBUTORS.md
           exclude_bots: true
       - name: Commit changes

.github/workflows/stale.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/stale@v7
+    - uses: actions/stale@v8
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
         stale-issue-message: 'This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days'

.prettierrc

@@ -0,0 +1,9 @@
+{
+	"parser": "babel",
+	"arrowParens": "avoid",
+	"tabWidth": 4,
+	"useTabs": false,
+	"singleQuote": false,
+	"printWidth": 170,
+	"trailingComma": "es5"
+}

CHANGELOG.md

@@ -3,6 +3,32 @@
 <!-- Feel free to put either your handle and/or full name, according to
      your privacy needs -->
 
+## v0.15.6 · ?? ?? 2023
+
+- fix: blur input on close via close button on plugin `dropdown_header`
+_@fabienwnklr_
+
+## v0.15.5 · 11 04 2023
+
+- style: remove useless border top with plugin `auto_position`
+_@fabienwnklr_
+
+## v0.15.4 · 11 04 2023
+
+- style: issue with pos absolute arrow up/down fixed
+- style: text-decoration for close button on dropdown plugin
+- fixed: manage dropdown height if item out of viewport
+_@fabienwnklr_
+
+## v0.15.3 · 11 04 2023
+
+- fixed: toggle selected option on enter for select multiple
+- fixed: enhance `tag_limit` plugin for manage better and more configurable
+- fixed: style enhancement for more modern appareance
+_@fabienwnklr_
+
+## v0.15.2 ? 
+
 ## v0.15.1 · 17 11 2022
 
 - New feature: dynamically add option groups
@@ -22,7 +48,7 @@
 - _Breaking change:_ Removed the dependencies on MicroPlugin and Sifter - These are now included in the selectize package directly.
 
 - Fixed missing style for dropdown*header plugin [*@fabienwnklr\_](https://github.com/fabienwnklr)
-- Fixed ([#1818](https://github.com/selectize/selectize.js/issues/1818)) Scroll left when I click on a selectized item and page is scrolled right [_@fabienwnklr_](https://github.com/fabienwnklr)
+- Fixed ([#1818](https://github.com/fabienwnklr/selectize.js/issues/1818)) Scroll left when I click on a selectized item and page is scrolled right [_@fabienwnklr_](https://github.com/fabienwnklr)
 - Added option to enable setting the first option in the list as active.
 
   _@joshuan92_

CONTRIBUTING.md

@@ -34,11 +34,11 @@ to the [maintainers](selectize@risadams.com).
 
 > If you want to ask a question, we assume that you have read the available [Documentation](https://selectize.dev).
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/selectize/selectize.js/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
+Before you ask a question, it is best to search for existing [Issues](https://github.com/fabienwnklr/selectize.js/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/selectize/selectize.js/issues/new).
+- Open an [Issue](https://github.com/fabienwnklr/selectize.js/issues/new).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
 
@@ -58,7 +58,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 - Make sure that you are using the latest version.
 - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://selectize.dev). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/selectize/selectize.jsissues?q=label%3Abug).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/fabienwnklr/selectize.js/issues?q=label%3Abug).
 - Make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
   - Stack trace (Traceback)
@@ -73,7 +73,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-- Open an [Issue](https://github.com/selectize/selectize.js/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Open an [Issue](https://github.com/fabienwnklr/selectize.js/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
 - Explain the behavior you would expect and the actual behavior.
 - Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 - Provide the information you collected in the previous section.
@@ -92,12 +92,12 @@ This section guides you through submitting an enhancement suggestion for Selecti
 
 - Make sure that you are using the latest version.
 - Read the [documentation](https://selectize.dev) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/selectize/selectize.js/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Perform a [search](https://github.com/fabienwnklr/selectize.js/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
 
 #### How Do I Submit a Good Enhancement Suggestion?
 
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/selectize/selectize.js/issues).
+Enhancement suggestions are tracked as [GitHub issues](https://github.com/fabienwnklr/selectize.js/issues).
 
 - Use a **clear and descriptive title** for the issue to identify the suggestion.
 - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.

Makefile

@@ -1,8 +1,8 @@
 .PHONY: compile release test
-GULP=node_modules/.bin/gulp
+GULP="node_modules/.bin/gulp"
 CURRENT_VERSION := $(shell sed -n '/"version":/{s/.*"version": "\([^"]*\)".*/\1/p;q}' package.json)
-version ?= $(CURRENT_VERSION) ## Version to release
-
+version ?= $(CURRENT_VERSION)## Version to release
+# $(info $$var is [${version}])
 all: compile test ## (default) Run Compile and test targets
 test: ## runs all tests (equivalent to `npm test`)
 	npm test

README.md

@@ -2,19 +2,19 @@
 
 ![Selectize.js](docs/static/img/selectize-wordmark.png)
 
-→ Selectize is looking for [new members on the maintenance team](https://github.com/selectize/selectize.js/discussions/1678)!
+→ Selectize is looking for [new members on the maintenance team](https://github.com/fabienwnklr/selectize.js/discussions/1678)!
 
 [![NPM version](http://img.shields.io/npm/v/@selectize/selectize.svg?style=flat)](https://www.npmjs.com/package/@selectize/selectize)
 [![CDNJS version](http://img.shields.io/cdnjs/v/selectize.js.svg?style=flat)](https://cdnjs.com/libraries/selectize.js)
 \
-![Node.js CI](https://github.com/selectize/selectize.js/workflows/Node.js%20CI/badge.svg)
+![Node.js CI](https://github.com/fabienwnklr/selectize.js/workflows/Node.js%20CI/badge.svg)
 \
 [![Discussion & Help](https://img.shields.io/badge/Discuss-Keybase-cc004c?style=flat)](https://keybase.io/team/selectize)
 
 Selectize is an extensible [jQuery](http://jquery.com/)-based custom `<select>`; UI control. It's useful for tagging, contact lists, country selectors, and so on. The goal is to provide a solid & usable experience with a clean and powerful API.
 
 - [Demos](https://selectize.dev/docs/demos)
-- [Changelog](https://github.com/selectize/selectize.js/releases)
+- [Changelog](https://github.com/fabienwnklr/selectize.js/releases)
 - [Documentation](https://selectize.dev/docs/api)
 
 ## Features
@@ -138,8 +138,8 @@ You can then run the examples at `https://loopback.website:4000/`.
 
 ## License
 
-Copyright &copy; 2013–2016 [Brian Reavis](http://twitter.com/brianreavis) & [Contributors](https://github.com/selectize/selectize.js/graphs/contributors)\
-Copyright &copy; 2020-2022 Selectize Team & [Contributors](https://github.com/selectize/selectize.js/graphs/contributors)
+Copyright &copy; 2013–2016 [Brian Reavis](http://twitter.com/brianreavis) & [Contributors](https://github.com/fabienwnklr/selectize.js/graphs/contributors)\
+Copyright &copy; 2020-2022 Selectize Team & [Contributors](https://github.com/fabienwnklr/selectize.js/graphs/contributors)
 
 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: <http://www.apache.org/licenses/LICENSE-2.0>
 

SECURITY.md

@@ -16,4 +16,4 @@ The following versions are currently being supported with security updates.
 
 File an issue with details and create a pull request with proposed changes
 
-- [Open an issue!](https://github.com/selectize/selectize.js/issues/new)
+- [Open an issue!](https://github.com/fabienwnklr/selectize.js/issues/new)