- 21 Oct, 2018 17 commits
-
-
XhmikosR authored
-
Nicolay Hvidsten authored
The current documentation for .flex-fill indicated that the flex items would have equal widths, regardless of content. This update ensures that the documentation reflects the fact that the width of the flex items depends on their actual content.
-
Andrew Luca authored
-
Martijn Cuppens authored
-
XhmikosR authored
-
Andrew Pucci authored
Define new variable for card header color
-
ysds authored
-
ysds authored
-
Martijn Cuppens authored
Removes the grid.css file of the grid example and makes use of utility classes
-
Andrey authored
-
Martijn Cuppens authored
-
Martijn Cuppens authored
-
Doug Puchalski authored
The outline button variant mixin should use the hover mixin, as does the non-outline version.
-
midzer authored
-
Martijn Cuppens authored
-
Roy Klutman authored
-
- 20 Oct, 2018 23 commits
-
-
XhmikosR authored
-
719media authored
user-select has no effect on before/after pseudo elements
-
andresgalante authored
-
Ian Walter authored
When gradients are enabled there is still a hover state on disabled buttons since the hover rules apply to background-image and disabled rules apply to background-color. This applies the logic already present in dropdowns to buttons. This fix was originally proposed by @ysds.
-
semenyakNik authored
-
Martijn Cuppens authored
-
XhmikosR authored
Requires jekyll-toc v0.8.0.
-
XhmikosR authored
-
XhmikosR authored
* remove unused rules * use Sass nesting in more places * use the core mixins in more places * use the color variables more
-
XhmikosR authored
-
Mark Otto authored
-
Johann-S authored
-
patrickhlauke authored
Firefox currently seems extremely fickle - with `pan-y` if fires pointercancel as soon as a touch strays even a pixel or so vertically. While `touch-action: pan-y` would be ideal (allowing users to scroll the page even when their finger started the scroll on the carousel), this prevents a swipe that isn't perfectly/only horizontal to be recognised by Firefox.
-
patrickhlauke authored
in particular, no need to use originEvent, and preventDefault() only needed for touch events
-
patrickhlauke authored
these may also be the cause of weird behavior in Chrome/Surface, where scrolling vertically triggers slide advance
-
patrickhlauke authored
-
patrickhlauke authored
- my fault, my original advice of using `touch-action: pan-x` is exactly the value we *don't* want to have the browser handle...
-
Johann-S authored
-
Johann-S authored
-
Johann-S authored
-
Christian Oliff authored
Useful suggestion from Google in the Web App Manifest documentation. https://developers.google.com/web/fundamentals/web-app-manifest/#start-url
-
galczo5 authored
-
Andres Galante authored
-