- 25 Mar, 2020 1 commit
-
-
Johann-S authored
-
- 23 Mar, 2020 1 commit
-
-
Martijn Cuppens authored
-
- 18 Mar, 2020 1 commit
-
-
Johann-S authored
-
- 09 Mar, 2020 1 commit
-
-
Martijn Cuppens authored
The `prev()` function doesn't take nodes other than elements into account. Also we could simplify things a lot using the `previousElementSibling` property. This property isn't fully supported in IE, it only works for elements, but since the `element` variable is an element, we can safely use it here. I've also added an additional test. I don't think we had this issue in v4, since we relied on jQuery back then. Ref. https://developer.mozilla.org/en-US/docs/Web/API/NonDocumentTypeChildNode/nextElementSibling
-
- 31 Oct, 2019 1 commit
-
-
Steffen Roßkamp authored
-
- 07 Oct, 2019 1 commit
-
-
XhmikosR authored
-
- 03 Oct, 2019 1 commit
-
-
Johann-S authored
-
- 22 Aug, 2019 1 commit
-
-
Markus Hatvan authored
* Enable and fix all occurrences with no-mixed-operators rule * Take care of the max-depth warning in button.js Signed-off-by:
mhatvan <markus_hatvan@aon.at>
-
- 02 Aug, 2019 1 commit
-
-
Johann-S authored
-
- 23 Jul, 2019 3 commits
-
-
Johann-S authored
-
Anton Bershanskiy authored
-
Johann-S authored
-
- 03 Jun, 2019 1 commit
-
-
XhmikosR authored
-
- 08 May, 2019 1 commit
-
-
XhmikosR authored
-
- 10 Apr, 2019 1 commit
-
-
XhmikosR authored
-
- 17 Mar, 2019 1 commit
-
-
Johann-S authored
-
- 13 Mar, 2019 1 commit
-
-
XhmikosR authored
-
- 11 Mar, 2019 2 commits
- 26 Feb, 2019 2 commits
- 20 Feb, 2019 19 commits
-
-
XhmikosR authored
-
Johann-S authored
-
XhmikosR authored
-
Johann-S authored
-
Johann-S authored
-
XhmikosR authored
-
Johann-S authored
-
Alessandro Chitolina authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-