| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
Use `assert.strictEqual`/`assert.true`/`assert.false`
|
|
|
|
* @babel/cli ^7.14.8 → ^7.15.5
* @babel/core ^7.14.8 → ^7.15.4
* @babel/preset-env ^7.14.8 → ^7.15.6
* @rollup/plugin-commonjs ^19.0.1 → ^20.0.0
* @rollup/plugin-node-resolve ^13.0.2 → ^13.0.4
* autoprefixer ^10.3.1 → ^10.3.4
* clean-css-cli ^5.3.0 → ^5.3.3
* eslint ^7.31.0 → ^7.32.0
* eslint-config-xo ^0.37.0 → ^0.38.0
* eslint-plugin-import ^2.23.4 → ^2.24.2
* eslint-plugin-unicorn ^34.0.1 → ^36.0.0
* hugo-bin ^0.74.0 → ^0.76.1
* qunit ^2.16.0 → ^2.17.1
* postcss ^8.3.5 → ^8.3.6
* rollup ^2.53.3 → ^2.56.3
* vnu-jar 21.6.11 → 21.9.2
|
|
In case of a modal with fading enabled, a prevented show event can cause show to not showing the modal anymore.
See #34055
Co-authored-by: XhmikosR <[email protected]>
|
|
Dropdown: support `.dropdown-item` wrapped in `<li>` tags
|
|
`aria-haspopup="true"` is really intended to signal that an ARIA `menu` will be opened on activation. as a result, some assistive technologies will announce controls with `aria-haspopup="true"` as a menu or menu item (e.g. JAWS and NVDA).
In addition, `aria-haspopup` seems to trigger a bug in Edge/Narrator where the `aria-expanded` state is not correctly announced at the moment when `aria-haspopup` is present.
This now makes the dropdown button more like a generic disclosure widget control - see also https://www.w3.org/TR/wai-aria-practices-1.2/examples/disclosure/disclosure-navigation.html01
|
|
* @babel/cli ^7.13.0 → ^7.13.14
* @babel/core ^7.13.8 → ^7.13.14
* @babel/preset-env ^7.13.9 → ^7.13.12
* @rollup/plugin-commonjs ^17.1.0 → ^18.0.0
* @rollup/plugin-node-resolve ^11.2.0 → ^11.2.1
* autoprefixer ^10.2.4 → ^10.2.5
* clean-css-cli ^5.2.0 → ^5.2.2
* eslint ^7.21.0 → ^7.23.0
* eslint-plugin-unicorn ^28.0.2 → ^29.0.0
* globby ^11.0.2 → ^11.0.3
* hugo-bin ^0.69.0 → ^0.70.0
* karma ^6.1.1 → ^6.3.2
* postcss ^8.2.6 → ^8.2.9
* qunit ^2.14.0 → ^2.14.1
* rollup ^2.40.0 → ^2.44.0
* stylelint ^13.11.0 → ^13.12.0
Also lock jQuery to v3.5.1 since 3.6.0 has a bug that affects at least our tests
|
|
|
|
Carousel: use buttons, not links, for prev/next controls
|
|
The `test` method on regexes does not behave like `match` on strings
for checks if the regex matches when the global modifier (g) is present.
Also adds a unit test on tooltips for sanitizing the same template twice.
Co-authored-by: XhmikosR <[email protected]>
|
|
Simplify karma.conf.js
`customLaunchers` does not seem to be needed.
|
|
|
|
Pin karma and linkinator due to failures
|
|
* Bump version to v4.6.0.
* Dist
|
|
* rename constants
* enforce the constants to be Boolean
* use the coverage plugin only one time, on the latest jQuery run
* fix karma `logLevel`
|
|
|
|
|
|
Remove unnecessary `_getCustomClass` method.
`customClass` will be in the configuration already, even if it is provided in the data attributes, and jQuery's [`addClass()`](https://api.jquery.com/addclass/) method will handle it, either `this.config.customClass` is a function or a class name (even if it is a blank string).
Co-authored-by: XhmikosR <[email protected]>
|
|
Be consistent with Popper's name.
|
|
Handle Chromium to run Karma
|
|
Don't hide modal when `config.keyboard` is false
|
|
Co-authored-by: XhmikosR <[email protected]>
|
|
When starting a cycle for a carousel, it only checks for a default interval, and not an interval defined on the slide element via data props. This adds a check in before creating the interval to move to the next slide.
Co-authored-by: XhmikosR <[email protected]>
|
|
tests: fix sanitizer test.
The test template does not include a `script` tag so the test always returned true.
|
|
|
|
* Replace visually hidden span with aria-current in tests
* Remove redundant visually hidden "(current)" when `aria-current` already used
Closes #31891
|
|
|
|
|
|
Enforce ES5 for tests
|
|
- add unit test to count how many events are thrown when widget contains multiple tags inside label
- add a parameter to toggle, if click event is provided onto an input then don't trigger another change event already thrown by the browser
- simplify the case where toggle interface is called click provide from input itself OR it's a button without label. If label is present, then browser propagate click event from childrens through label and then cause multiple calls to toggle
- the test assumes that `.btn` class is always set onto the label if there's one, otherwise need to update this plugin and look for label around the input
Test with keyboard, mouse and js click call
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* clear timeout before showing the toast
* Add unit test
* Remove the check for timeout
* Check for clearTimeout to have been called
Co-authored-by: XhmikosR <[email protected]>
# Conflicts:
# js/tests/unit/toast.spec.js
|
|
* @rollup/plugin-node-resolve 8.1.0
* popper.js 1.16.1
* qunit 2.10.1
* rollup 2.21.0
|
|
|
|
Prevent overflowing static backdrop modal animation
TODO: backport the test too
|