There is no actual vulnerability in the existing implementation, as we
can only fetch existing elements (no DOM injection is possible). Plus,
the only call occurring on those elements is `HTMLElement#focus`.
Consider this an extra, more future-proof precaution.
In short this updates `travis.yml`'s indent size to 2 spaces as per
WordPress' development repo and Jetpack.
Inserts final newline.
Uses a period at the end of each sentence.
* Remove custom arguments from `the_posts_navigation()` and `the_post_navigation()`.
* Adjust fallbacks for `the_posts_navigation()` and `the_post_navigation()`.
* update pot file.
* merge master for style.css and style.scss.
Fairly minor and noncommittal change. It does encourage theme authors
to think about semantically versioning their themes but doesn’t require
`_s` to take a strong stand on it.
It also removes an obstacle from submitting the generated theme to the
WordPress.org Theme Directory, as it refuses themes with non-numeric
version numbers.
Fixes https://github.com/Automattic/underscores.me/issues/8
Closes https://github.com/Automattic/underscores.me/pull/20
Props @ScottSmith95.
At some point in the past it was believed that a leading whitespace was
necessary for a proper replacement.
Let’s see if the existing replace handler can indeed handle it without
it.
See
7671cad568
2f871a1ae28119b8dbf1
The reset we used was a mix of Normalize, the Paul Irish reset,
sprinkled with some blueprint.css, and base styles. It was hard to
maintain and just seemed outdated (setting the base font-size to 10px
instead of 16px, among other things).
Normalize sets saner defaults and is generally just not as disruptive
as a full reset.
The code was added as is, has only its comments stripped (for now), and
is not mixed with any styles to make future updates to it as easy as
possible.
See #3, #44, #174, #267, #617.
Even with WordPress’ commitment to backwards compatibility, we should
probably not bank on private functions being around for ever, and tying
our functionality to it.
This will go old school and do a version check to provide compatibility
with older versions of WordPress. Again, this is only temporary until
4.3 is out.
See #644.
Fixes#636.
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.
