Apostolis Taxidaridis apostoiis

Mobile Safari does not support position: fixed when an input focused and virtual keyboard displayed.

To force it work the same way as Mobile Chrome, you have to use position: absolute, height: 100% for the whole page or a container for your pseudo-fixed elements, intercept scroll, touchend, focus, and blur events.

The trick is to put the tapped input control to the bottom of screen before it activates focus. In that case iOS Safari always scrolls viewport predictably and window.innerHeight becomes exactly visible height.

Open https://avesus.github.io/docs/ios-keep-fixed-on-input-focus.html in Mobile Safari to see how it works.

Please avoid forms where you have several focusable elements because more tricks to fix position will be necessary, those were added just for demonstration purposes.

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

What this does:

Within an <ion-scroll>, this directive creates sticky item headers that get bumped out of the way by the next item.

Demo: http://cl.ly/2u2X390s0H1a

Requirements:

Needs UnderscoreJS for its _.throttle utility.
Must be used within an or

Semantic commits

Writing commits is a fast and simple process which we do all day. Imagine them becoming powerful for us which finally give them some attention. The following semantic commits will do so and have the aim to:

Generate a changelog with commits for end-user
Generate a speaking summary for customer
Generate a easy to read list of changes for developer
In general: Make commits parseable by some script

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

⇐ back to the gist-blog at jrw.fi

Advanced SCSS

Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.

I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.

This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso

	/**
	* For more information see this tutorial: http://blog.webbb.be/use-jekyll-with-gulp/
	*
	* Libs import
	* --> How to install? npm install --save-dev gulp-minify-html
	* @type {[type]}
	*/
	var gulp = require('gulp'),
	path = require('path'),

	.logo a {
	display: block;
	width: 52px;
	height: 52px;
	background: url(../img/logo.jpg) 0 0 no-repeat;
	text-indent: 100%;
	white-space: nowrap;
	overflow: hidden;
	}

	class Array
	def skip_first?(accumulator)
	return 1 if accumulator.nil?
	return 0 unless accumulator.nil?
	end

	def my_inject(accumulator = nil)
	start = skip_first? accumulator
	accumulator \|\|= self.first

	.wrapper{
	width: 550px;
	text-align: justify;
	background: firebrick;
	font-size: 0;
	font-size: 12px\9; /* IE6-9 only hack */
	}

	.wrapper div{
	background: white;