Brian Kardell bkardell

Imagine that we define a function that can do a unit of work some time later called doSomeAsyncWork. You pass it how long you want to wait before doing the work and a 'work' function which receives both resolve and reject...

var doSomeAsyncWork = function (timeMs, work) {
   return new Promise(function (resolve, reject) {
       setTimeout(function () {
        work(resolve, reject);
 }, timeMs);

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title>Standard HTML5 test</title>
	<!-- Dependencies -->
	</head>

	<body>
	<!-- use the following markup for each media element -->

	var oldPut = IDBObjectStore.prototype.put,
	oldGet = IDBObjectStore.prototype.get;

	IDBObjectStore.prototype.put = function (o) {
	// create a debuggable point...
	return oldPut.call(this, o);
	}
	IDBObjectStore.prototype.get = function (o) {
	// create a debuggable point...
	return oldGet.call(this, o);

	var oReq;

	try{
	oReq = new XMLHttpRequest();
	oReq.addEventListener("load", function () { console.log("success event"); });
	oReq.addEventListener("error", function () { console.error("error event"); });
	oReq.open("GET", "http://www.example.org/example.txt");
	oReq.send();
	} catch (e) {
	console.error("error thrown");

	<BODY>
	<HEADER>
	<TITLE>The World Wide Web project</TITLE>
	<NEXTID N="55">
	</HEADER>
	<BODY>
	<H1>World Wide Web</H1>The WorldWideWeb (W3) is a wide-area<A
	NAME=0 HREF="WhatIs.html">
	hypermedia</A> information retrieval
	initiative aiming to give universal

	<!DOCTYPE html>
	<html>
	<head>
	<title>Online Art Project</title>
	<style>
	.gameboard {
	clear: both;
	display: block;
	border: 1px solid red;
	background-color: #cfcffc;

	<section>
	<h1>What's this?</h1>
	<p>"Actionable" elements (ie, elements like <code><a>,<button>,<input type="button"></code>) have no ideal patterns around how you manage tooltips in a way that it simultaneously accessible and touch friendly. It's easy enough to add <code>aria-describedby</code> and some CSS involving <code>:hover, :focus</code> to most elements, but these elements are different: clicking them doesn't just set focus, it activates some behavior. This means that there is no way for users of touch-based devices to get the same sort of information. You can add a help button but this easily leaves blind users in the lurch because the button itself isn't described and they likely have no idea that the _next_ element contains help for this one. In a word, this situation kind of sucks. A user might needs to know what that button does before they want to click it, but we cannot dedicated a major portion of the UI to always showing a descrition of it. Figuring out an ap

	function componentToHex(c) {
	var hex = c.toString(16);
	return hex.length == 1 ? "0" + hex : hex;
	}

	function rgbToHex(color) {
	return componentToHex(color.red) + componentToHex(color.green) + componentToHex(color.blue);
	}