xHikaruMx

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

Share Counts

I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.

If you want to roll up all of these into a single jQuery plugin check out Sharrre

Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.

Twitter

	<?php
	/*
	##############################
	########### Search ###########
	##############################

	Included are steps to help make this script easier for other to follow
	All you have to do is add custom ACF post types into Step 1 and custom taxonomies into Step 10
	[list_searcheable_acf list all the custom fields we want to include in our search query]
	@return [array] [list of custom fields]

	# import config.
	# You can change the default config with `make cnf="config_special.env" build`
	cnf ?= config.env
	include $(cnf)
	export $(shell sed 's/=.*//' $(cnf))

	# import deploy config
	# You can change the default deploy config with `make cnf="deploy_special.env" release`
	dpl ?= deploy.env
	include $(dpl)

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title>Title</title>

	<!-- we use 'preload_' instead of 'preload' to make it testable in chrome -->
	<link rel="preload_" onload="console.log(this, 'script');" href="http://code.jquery.com/jquery-1.12.1.js" as="script" />
	<link rel="preload_" onload="console.log(this, 'style');" href="https://cdn.jsdelivr.net/bootstrap/3.3.6/css/bootstrap.min.css" as="style" />
	<link rel="preload_" onload="console.log(this, 'font');" href="LatoLatin-Regular.woff" as="font" type="font/woff" crossorigin="" />

	<?php

	/**
	* HTML5 Styles Dropdown
	*
	* @author Bryan Willis
	* @link https://www.tinymce.com/docs/demo/format-html5/
	*/
	function mce_html5_formatting( $init ) {

	<?php

	/**
	* [list_searcheable_acf list all the custom fields we want to include in our search query]
	* @return [array] [list of custom fields]
	*/
	function list_searcheable_acf(){
	$list_searcheable_acf = array("title", "sub_title", "excerpt_short", "excerpt_long", "xyz", "myACF");
	return $list_searcheable_acf;
	}

	// Query arguments
	$popular_args = array(
	'posts_per_page' => $size,
	'meta_key' => '_base_popular_posts_count',
	'orderby' => 'meta_value_num'
	'year' => date('Y'), // Current year
	'monthnum' => date('n') // Current month
	);

	<?php
	function custom_search($search, $wp_query) {
	global $wpdb;

	//サーチページ以外だったら終了
	if (!$wp_query->is_search)
	return $search;
	if (!isset($wp_query->query_vars))
	return $search;

	<?php
	/**
	* WordPress Query Comprehensive Reference
	* Compiled by luetkemj - luetkemj.com
	* Japanese translated by hissy
	*
	* CODEX: http://wpdocs.sourceforge.jp/%E9%96%A2%E6%95%B0%E3%83%AA%E3%83%95%E3%82%A1%E3%83%AC%E3%83%B3%E3%82%B9/WP_Query#.E3.83.91.E3.83.A9.E3.83.A1.E3.83.BC.E3.82.BF
	* Source: https://core.trac.wordpress.org/browser/tags/3.9/src/wp-includes/query.php
	* Original: https://gist.github.com/luetkemj/2023628/9e911982440141a13cb1dd8ba1ad6b35cd7bbdd7
	*/