mminguezz

// Sticky Nav Component
var Sticky = (function() {
  'use strict';

  var CSS_CLASS_ACTIVE = 'is-fixed';

  var Sticky = {
    element: null,
    position: 0,
    addEvents: function() {

mminguezz

# EditorConfig helps developers define and maintain consistent
# coding styles between different editors and IDEs
# http://editorconfig.org

# Find Plugin
# http://editorconfig.org/#download

# Install tools
# ```npm install -g editorconfig-tools```
# run ```editorconfig-tools fix **/*```

mminguezz

/* calc() and attr() tests */

span {outline: 1px solid #ccc;}
.a {font-size: 2em;}
.aa {font-size: calc(1em * 2);}

body {margin: 0;}
p {margin-left: 1.5em;}
.wrapper {padding-top: 2em; clear: left;}
.content {

mminguezz

<?php
$string = '
	<div class="page-nav-header">
		<h1>Compose</h1>
		<ul class="nav nav-tabs">
			<li id="type-email"<%= compose_type == \'email\' ? \' class="active"\' : \'\' %>><a href="#" class="email change-type-email">E-mail</a></li>
			<li id="type-twitter"<%= compose_type == \'twitter\' ? \' class="active"\' : \'\' %>><a href="#" class="twitter change-type-twitter">Twitter</a></li>
		</ul>
		<br clear="all" />
	</div>

mminguezz

Just jotting some notes on delivering webfonts performantly…

still an incomplete draft.

basics

• identify which fonts you NEED for the first render (A), and which you dont (B)
• you want the network reqs for A to start ASAP. ideally the @font-face req is in a style tag, following CRP guidelines
  • you can also preload it with font load events API https://www.igvita.com/2014/01/31/optimizing-web-font-rendering-performance/
• you can use the upcoming preload if you know the font URL ahead of time.