Andrew Duthie aduth

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

There are two types of markup in Liquid: Output and Tag.

Output markup (which may resolve to text) is surrounded by

{{ matched pairs of curly brackets (ie, braces) }}

Tag markup (which cannot resolve to text) is surrounded by

This demonstrates the implementation of full text search for documents in Indexed DB.

Word-breaking and stemming is used to create a list of terms for each document.
Document records are annotated with the list of terms when added to the database.
A multi-entry index on the list of terms is populated.
A query is similarly processed into a list of terms.
A join over the terms is implemented using multiple cursors on the index.

The necessity of annotating records with the word list to populate the index is a limitation of the current Indexed DB API. A feature request to support custom

React lifecycle cheatsheet

Method	Side effects¹	State updates²	Example uses
Mounting
`componentWillMount`		✓	Constructor equivalent for `createClass`
`render`			Create and return element(s)
`componentDidMount`	✓	✓	DOM manipulations, network requests, etc.
Updating
`componentWillReceiveProps`		✓	Update `state` based on changed `props`

REST API Contributor Day

Plan for the day

Improve documentation
- Something we explain very poorly in the REST API handbook; hoping to explain it today to de-mystify
- Handbook is what was on WP-API.org -- some stuff in there is very good and some that is out of date
- We have some guides but they are not organized
- We want to come up with a coherent content architecture
Expand the endpoints presented by the API

	# ## Backbone model caching
	# This is a simple solution to the problem "how do I make less requests to
	# my server?".
	#
	# Whenever you need a model instance, this will check first if the same thing
	# has been fetched before, and gives you the same instance instead of fetching
	# the same data from the server again.
	#
	# Reusing the same instance also has the great side-effect of making your
	# model changeable from one part of your code, with your changes being available

	#
	# Working with branches
	#

	# Get the current branch name (not so useful in itself, but used in
	# other aliases)
	branch-name = "!git rev-parse --abbrev-ref HEAD"
	# Push the current branch to the remote "origin", and set it to track
	# the upstream branch
	publish = "!git push -u origin $(git branch-name)"

	import { Component } from "React";

	export var Enhance = ComposedComponent => class extends Component {
	constructor() {
	this.state = { data: null };
	}
	componentDidMount() {
	this.setState({ data: 'Hello' });
	}
	render() {

	#!/bin/bash
	set -e

	show_help() {
	cat << EOF
	Usage: ${0##*/} [-u USER] [-p PASS] [-P PORT] [-H HOST] [DATABASE]
	${0##*/} -h

	Open a standard connection in Sequel PRO.

	import { h, Component } from 'preact';
	import Markup from 'preact-markup';
	import register from './preact-custom-element';

	// just a proxy component: WC -> Preact -> WC
	const A = () => <x-b foo="initial foo from <x-a>" />;

	// stateful component that can re-render
	class B extends Component {
	render(props, state) {