What it will now do:
- Lint the php files against relevant PHP versions.
- Lint the js files once - the result won't change across PHP versions.
- Check against WPCS once - the result won't change across PHP versions.
What I have changed:
- Added linting against PHP 7 and HHVM, with HHVM being allowed to fail.
- Added js linting and style check per example from Twenty Sixteen.
- Moved to the faster container based environment for running travis.
- Script will no longer pull in PHPCS, WPCS and the JS linters in every build. Now they will only be pulled in when needed.
- Limited the clone depth for quicker cloning of external repositories.
- Removed the pulling in of WP and running builds against different WP versions as this wasn't used at all in the actual test scripts.
This patch allows the user to view a site on a touch screen tablet and
access child menus by clicking on the parent once, or access the parent
by clicking on it twice. Props @iamtakashi for the original fix.
* Separate scoping and assignment so that a decision does not need to be made as to whether we should intermix spaces and tabs on the left
* Restore the previously removed nav-menu class addition to the first unordered list in `#site-navigation`.
* Restore the `.navigation-main.toggled-on .nav-menu` selector.
* Remove rules for the `.main-small-navigation ul` selector.
* Only set button and menu if container is not null.
* Break up the "return early" conditional into multiple parts.
* Shorten the name of the toggled class from `toggled-on` to `toggled`.
* Restore the "Hide menu toggle button if menu is empty." documentation.
* Remove the `nav-menu` class. The previous code would replace any custom custom classes applied via `wp_nav_menu()` or template file.
* Replace the `nav-menu` selector is style.css with selectors that will target both a custom nav menu and a page menu. These changes could use critical feedback. Do you know of an edge case where they might not work as expected?