The following code adds a [placeholder] class name to the <body>
element:
document.body.classList.add( "foo-bar" );
Question: How should the class name inserted at [placeholder] be formatted?
diff --git a/README.md b/README.md | |
index 9731e95..7c730ce 100644 | |
--- a/README.md | |
+++ b/README.md | |
@@ -50,8 +50,8 @@ cd jquery-ui | |
# Install the node module dependencies | |
npm install | |
-# Run the build task | |
-grunt build |
<?xml version="1.0"?> | |
<entries> | |
<entry type="method" name="jQuery.widget"> | |
<title>Widget Factory</title> | |
<signature> | |
<argument name="name" type="String"> | |
<desc>The name of the widget to create, including the namespace.</desc> | |
</argument> | |
<argument name="base" type="Function" optional="true"> | |
<desc>The base widget to inherit from. This must be a constructor that can be instantiated with the `new` keyword. Defaults to <code>jQuery.Widget</code>.</desc> |
<!doctype html> | |
<html lang="en"> | |
<head> | |
<meta charset="utf-8"> | |
<title>jQuery 2.1.0 Parse/Execute Test</title> | |
</head> | |
<body> | |
<script>var start = new Date();</script> |
export CLICOLOR=1 | |
export LSCOLORS=GxFxCxDxBxegedabagaced | |
# Sexy Bash Prompt, inspired by "Extravagant Zsh Prompt" | |
# Screenshot: http://img.gf3.ca/d54942f474256ec26a49893681c49b5a.png | |
# A big thanks to \amethyst on Freenode | |
if [[ $COLORTERM = gnome-* && $TERM = xterm ]] && infocmp gnome-256color >/dev/null 2>&1; then export TERM=gnome-256color | |
elif infocmp xterm-256color >/dev/null 2>&1; then export TERM=xterm-256color |
module.exports = function( grunt ) { | |
"use strict"; | |
var version = "2.1.1", | |
exclude = [ "ajax" ], | |
dest = "jquery-built.js" | |
exclude.forEach(function( module, index ) { | |
exclude[ index ] = "-" + module; | |
}); |
The following code adds a [placeholder] class name to the <body>
element:
document.body.classList.add( "foo-bar" );
Question: How should the class name inserted at [placeholder] be formatted?
Test gist for playing with the GitHub API. |
Client-side form validation is a notoriously painful development experienece. Yet, despite HTML5 constraint validation—a series of APIs designed to make form validation way easier—being implemented in most browsers, no one actually uses it. In this talk you'll see why. We'll discuss constraint validation's pain points, and how you can overcome them in your own applications. Come learn how to use HTML5 form validation today!
Building hybrid apps can be hard. In addition to actually coding an application, you also have to deal platform-specific configuration files, icons, permissions, deployment procedures, and more.
That's where the Telerik Platform comes in. With a series of tools—including cloud-based builds, dozens of high-quality (and free) Cordova plugins, and a whole lot more—Telerik provides everything you need to take the pain out of hybrid development. Come learn how you can focus less on the platform-specific nuances of hybrid development, and more on building awesome apps.