-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Comparing changes
Open a pull request
base repository: jquery/jquery-ui
base: 6be875c
head repository: jquery/jquery-ui
compare: 47036d1
- 9 commits
- 75 files changed
- 2 contributors
Commits on Mar 30, 2023
-
Tests: Test only valid values for Datepicker defaultDate, min/maxDate
The docs say that valid periods when using string value and period pairs as relative dates are "y", "m", "w", and "d" https://api.jqueryui.com/datepicker/ Closes gh-2143
Configuration menu - View commit details
-
Copy full SHA for f8990e6 - Browse repository at this point
Copy the full SHA f8990e6View commit details
Commits on May 9, 2023
-
Demos:Tests: Avoid self-closing HTML tags
Self-closing tags are reported by newer versions of the htmllint Grunt plugin. They also don't make sense in our HTML files since they are not XHTML-compliant and they run in HTML mode anyway.
Configuration menu - View commit details
-
Copy full SHA for 697db3b - Browse repository at this point
Copy the full SHA 697db3bView commit details -
Tests: Fix tooltip tests by destroying tooltips
Some tests were not properly destroying tooltips which made tests start to fail with the new QUnit.
Configuration menu - View commit details
-
Copy full SHA for 3cbc4c4 - Browse repository at this point
Copy the full SHA 3cbc4c4View commit details -
Tests: Switch from QUnit.jsDump to QUnit.dump
`QUnit.jsDump` was renamed to `QUnit.dump` in QUnit 2.0.
Configuration menu - View commit details
-
Copy full SHA for d001fcf - Browse repository at this point
Copy the full SHA d001fcfView commit details -
Configuration menu - View commit details
-
Copy full SHA for ed86c7f - Browse repository at this point
Copy the full SHA ed86c7fView commit details -
Tests: Make Puppeter really fire Chrome on macOS
Also, workaround issues with QUnit Chrome bridge: the Chrome bridge from `grunt-contrib-qunit` is now getting injected into every single iframe, including an empty one that has no intention of running QUnit tests. Since that bridge requires QUnit, it fails with an error in such cases. Workaround the issue by wrapping the bridge in another function that bails early if QUnit is not defined.
Configuration menu - View commit details
-
Copy full SHA for 65bf87b - Browse repository at this point
Copy the full SHA 65bf87bView commit details -
Build: Stop using ::set-output in GitHub Actions
The `set-output` workflow is deprecated in favor of using environment variables, see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Configuration menu - View commit details
-
Copy full SHA for 39a98d7 - Browse repository at this point
Copy the full SHA 39a98d7View commit details -
Build: Update dependencies, including QUnit 1 -> 2
Also, fix htmllint lang exclusion patterns.
Configuration menu - View commit details
-
Copy full SHA for 57e2dfa - Browse repository at this point
Copy the full SHA 57e2dfaView commit details -
Build: Fork vendors to remove QUnit deprecated API usage
Changes: * add `tests/lib/vendor/**/*` to `.eslintignore` * move `qunit-composite` to `tests/lib` so that we can modify it * move `qunit-assert-classes` to `tests/lib` so that we can modify it * move `qunit-assert-close` to `tests/lib` so that we can modify it * replace `assert.push` with `assert.pushResult` * remove usage of `QUnit.extend`
Configuration menu - View commit details
-
Copy full SHA for 47036d1 - Browse repository at this point
Copy the full SHA 47036d1View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 6be875c...47036d1