/* Most of the styles are taken from impress.js demo */ html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video { margin: 0; padding: 0; border: 0; font-size: 100%; font: inherit; vertical-align: baseline; } /* HTML5 display-role reset for older browsers */ article, aside, details, figcaption, figure, footer, header, hgroup, menu, nav, section { display: block; } body { line-height: 1; } ol, ul { list-style: none; } blockquote, q { quotes: none; } blockquote:before, blockquote:after { content: ""; content: none; } q:before, q:after { content: ""; content: none; } table { border-collapse: collapse; border-spacing: 0; } /* * Now here is when interesting things start to appear. * * We set up styles with default font and nice gradient in the background. * * And yes, there is a lot of repetition there because of -prefixes but we don't * * want to leave anybody behind. */ body { font-family: "PT Sans", sans-serif; min-height: 740px; background: white; } /* * Now let's bring some text styles back ... */ b, strong { font-weight: bold; } i, em { font-style: italic; } /* * ... and give links a nice look. */ a { color: inherit; text-decoration: none; padding: 0 0.1em; background: rgba(255, 255, 255, 0.5); text-shadow: -1px -1px 2px rgba(100, 100, 100, 0.9); border-radius: 0.2em; -webkit-transition: 0.5s; -moz-transition: 0.5s; -ms-transition: 0.5s; -o-transition: 0.5s; transition: 0.5s; } a:hover, a:focus { background: white; text-shadow: -1px -1px 2px rgba(100, 100, 100, 0.5); } /* * Because the main point behind the impress.js demo is to demo impress.js * * we display a fallback message for users with browsers that don't support * * all the features required by it. * * All of the content will be still fully accessible for them, but I want * * them to know that they are missing something - that's what the demo is * * about, isn't it? * * And then we hide the message, when support is detected in the browser. */ .fallback-message { font-family: sans-serif; line-height: 1.3; width: 780px; padding: 10px 10px 0; margin: 20px auto; border: 1px solid #E4C652; border-radius: 10px; background: #EEDC94; } .fallback-message p { margin-bottom: 10px; } .impress-supported .fallback-message { display: none; } /* * Now let's style the presentation steps. * * We start with basics to make sure it displays correctly in everywhere ... */ .step { position: relative; width: 1800px; padding: 40px; margin: 20px auto; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; -ms-box-sizing: border-box; -o-box-sizing: border-box; box-sizing: border-box; font-family: "PT Serif", georgia, serif; font-size: 48px; line-height: 1.5; } /* * ... and we enhance the styles for impress.js. * * Basically we remove the margin and make inactive steps a little bit transparent. */ .impress-enabled .step { margin: 0; opacity: 0.3; -webkit-transition: opacity 1s; -moz-transition: opacity 1s; -ms-transition: opacity 1s; -o-transition: opacity 1s; transition: opacity 1s; } .impress-enabled .step.active { opacity: 1; } /* * These 'slide' step styles were heavily inspired by HTML5 Slides: * * https://html5slides.googlecode.com/svn/trunk/styles.css * * ;) * * They cover everything what you see on first three steps of the demo. */ .slide { display: block; width: 1200px; height: 700px; padding: 40px 60px; background-color: white; border: 1px solid rgba(0, 0, 0, 0.3); border-radius: 10px; box-shadow: 0 2px 6px rgba(0, 0, 0, 0.1); color: #666666; text-shadow: 0 2px 2px rgba(0, 0, 0, 0.1); font-family: "Open Sans", Arial, sans-serif; font-size: 30px; line-height: 36px; letter-spacing: -1px; } .slide q { display: block; font-size: 50px; line-height: 72px; margin-top: 100px; } .slide q strong { white-space: nowrap; } /* * And now we start to style each step separately. * * I agree that this may be not the most efficient, object-oriented and * * scalable way of styling, but most of steps have quite a custom look * * and typography tricks here and there, so they had to be styled separately. * * First is the title step with a big

(no room for padding) and some * * 3D positioning along Z axis. / .big { width: 600px; text-align: center; font-size: 60px; line-height: 1; } .big b { display: block; font-size: 250px; line-height: 250px; } .big .thoughts { font-size: 90px; line-height: 150px; } / * This step has some animated text ... / #ing { width: 900px; } / * ... so we define display to `inline-block` to enable transforms and * * transition duration to 0.5s ... / .eff b { display: inline-block; -webkit-transition: 0.5s; -moz-transition: 0.5s; -ms-transition: 0.5s; -o-transition: 0.5s; transition: 0.5s; } / * ... and we want 'positioning` word to move up a bit when the step gets * * `present` class ... / .present.eff .positioning { -webkit-transform: translateY(-10px); -moz-transform: translateY(-10px); -ms-transform: translateY(-10px); -o-transform: translateY(-10px); transform: translateY(-10px); } .present.eff .rotating { -webkit-transform: rotate(-10deg); -moz-transform: rotate(-10deg); -ms-transform: rotate(-10deg); -o-transform: rotate(-10deg); transform: rotate(-10deg); -webkit-transition-delay: 0.25s; -moz-transition-delay: 0.25s; -ms-transition-delay: 0.25s; -o-transition-delay: 0.25s; transition-delay: 0.25s; } .present.eff .scaling { -webkit-transform: scale(0.7); -moz-transform: scale(0.7); -ms-transform: scale(0.7); -o-transform: scale(0.7); transform: scale(0.7); -webkit-transition-delay: 0.5s; -moz-transition-delay: 0.5s; -ms-transition-delay: 0.5s; -o-transition-delay: 0.5s; transition-delay: 0.5s; } / * And as the last thing there is a workaround for quite strange bug. * * It happens a lot in Chrome. I don't remember if I've seen it in Firefox. * * Sometimes the element positioned in 3D (especially when it's moved back * * along Z axis) is not clickable, because it falls 'behind' the * * element. * * To prevent this, I decided to make non clickable by setting * * pointer-events property to `none` value. * * Value if this property is inherited, so to make everything else clickable * * I bring it back on the #impress element. * * If you want to know more about `pointer-events` here are some docs: * * https://developer.mozilla.org/en/CSS/pointer-events * * There is one very important thing to notice about this workaround - it makes * * everything 'unclickable' except what's in #impress element. * * So use it wisely ... or don't use at all. / .impress-enabled { pointer-events: none; } .impress-enabled #impress { pointer-events: auto; } .color { color: red; } #front.step img { display: block; margin: auto; width: 100%; height: auto; } /# sourceMappingURL=reflow.css.map */