We should consider removing all CSS rules that provide `:hover` and `:active` pseudo element behavior for `screen-reader-text` elements.
In IE 10/11, the `screen-reader-text` element, normally hidden, pops up when you hover your mouse over it, obscuring content — the Archives Widget drop-down menu is a good example.
According to the latest from the core a11y team: https://make.wordpress.org/accessibility/2015/02/09/hiding-text-for-screen-readers-with-wordpress-core/ -- we only need the `:focus` pseudo element class.
Props to @lancewillett for figuring this out.
Reverse media queries to use min-width instead of max-width, taking a
mobile-first approach to the navigation menu. It displays as the
default, and disappears at widths above 600px.
Fixes#579.
* 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.
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.
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.
A default background color is needed for any time there is no custom background color.
This happens to use the browser's default `#fff`, and is meant more as a reminder for theme authors.
See #515.
We can safely increase the textarea width from 98% to 100%.
```box-sizing``` handles the layout nicely and it won't allow the overflow.
If more details is needed, please see: http://davidwalsh.name/textarea-width this is the best example I could find.
Minor CSS optimization for border and border color.
For the border itself, we don't need to include the color in ```border: {}```, color is already added in ```border-color: {}```.
Since the Theme uses shorthands for padding/margins, why not do the same for the border colors as well.
The leading whitespace is needed to replace this `_s` instance with the theme name.
It's obviously a hack, since it also leaves the theme name with a leading white space, but short of adding a new replace logic for this specific line in `style.css`, it's the easiest way to achieve that.
See #304, where this was brought up before.
Chris Schmieder
mrwweb
Tammie Lister
David A. Kennedy
Dmitry Mayorov
jrfnl
sarah ✈ semark
Cor van Noorloos
Caroline Moore
Ulrich Pogson
Christopher Crouch
Hugo Baeta
Chris Wilcoxson
Gabriel Luethje
Konstantin Obenland
Ian Dunn
Kazue Igarashi
Tim Moore
Ram Ratan Maurya
Emil Uzelac
Stefan Brechbühl
Yash Gupta
Mike Griffiths
Fränk Klein
Greg Rickaby
Slobodan Manic