Add Class(es) to <html>

Adding Classes

In CodePen, whatever you write in the HTML editor is what goes within the <body> tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html> tag. If you want to add classes there that can affect the whole document, this is the place to do it.

Stuff for <head>

About the <head>

In CodePen, whatever you write in the HTML editor is what goes within the <body> tags in a basic HTML5 template. If you need things in the <head> of the document, put that code here.

!

Insecure Resource

The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.

CSS Preprocessor

About CSS Preprocessors

CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.

CSS Base

About CSS Base

It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.

NormalizeResetNeither

Vendor Prefixing

About Vendor Prefixing

To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit- or -moz-.

Add External Stylesheets/Pens

Any URL's added here will be added as <link>s in order, and before the CSS in the editor. If you link to another Pen, it will include the CSS from that Pen. If the preprocessor matches, it will attempt to combine them before processing.

About External Resources

You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.

If the stylesheet you link to has the file extension of a preprocessor, we'll attempt to process it before applying.

You can also link to another Pen here, and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.

JavaScript Preprocessor

About JavaScript Preprocessors

JavaScript preprocessors can help make authoring JavaScript easier and more convenient. For instance, CoffeeScript can help prevent easy-to-make mistakes and offer a cleaner syntax and Babel can bring ECMAScript 6 features to browsers that only support ECMAScript 5.

You're using npm packages, so we've auto-selected Babel for you here, which we require to process imports and make it all work. If you need to use a different JavaScript preprocessor, remove the packages in the npm tab.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

About External Resources

You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.

If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.

You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.

JS

"use strict";
/**
* Promises A+
* inspired by:
* http://joseoncode.com/2013/05/23/promises-a-plus/
*/
var workingWebservice = "https://api.github.com/users/jufa/repos";
var brokenWebservice = "https://api.github.baduri";
var webserviceUnderTest;
webserviceUnderTest = workingWebservice;
//var webserviceUnderTest = brokenWebservice;
// so this is how we do it with jQuery callbacks and deferals:
// we use the chainable, clear, but non-standard .done() and .error()
$.ajax(webserviceUnderTest).done(function(data){
for (var i = 0; i < data.length; i++) {
$('#promos').append('<li><h3>'+data[i].name+'</h3><p>'+data[i].description+'</p></li>');
}
}).error(function(error){
$('#promos').append('Error: ', error.state());
});
// but we want to be compliant with the Promise A+ standard
// which is interoperable between many other asynchronous libraries.
// q.js is a popular stand-alone (not part of a bigger framework)
// implementation; we could use it to
// 'wrap'the non standard jQuery asynchronous callback scheme
// to produce standard promises:
// first, use the Q.defer factory method to make a 'deferral' object.
// A Deferral object is a container for any asynchronous style event
// that we want to work with using the Promises A+ standard:
var d = Q.defer();
// Now we have something that contains:
// a promise object we can pass around using chaining i.e.
// doSomething.then(doSomethingElse()).then(doAThirdThing());
// a reject method - which is called if something goes wrong in this chain opf promises,
// like an timeout in a webservice call
// a resolve method - which is called when the promise returns with success and data!
//so now we tie the jQuery asynchronous callback functions .done and .error to this
// standard deferral object's reject and resolve methods, so the two together behave to the A+ standard.
// the trick here is to tie in three things:
// 1. Assign the reslt of the nonstandard jQuery asynch function to the standard promise in
// our new deferal object
// 2. Pass the nonstandard success callback's data to the resolve method
// our new deferal object
// 3. Pass the nonstandard error callback's data to the reject method
// our new deferal object:
var ourNewPromise = d.promise; //Step 1 complete!
ourNewPromise = $.ajax(webserviceUnderTest)
.done(function(data){
d.resolve(data); //step 2 complete!
})
.error(function(error){
d.reject(error); //step 3 complete!
});
// and NOW we can handle the asynchronous result using the standard
// Promise A+ standard notation and patterns, such as .then, intead of .done!
ourNewPromise.then(function(data){
for (var i = 0; i < data.length; i++) {
$('#promospromise').append('<li><h3>' + data[i].name + '</h3><p>' + data[i].description + '</p></li>');
}
}, function(error){
console.log(error);
$('#promospromise').append('Error: ', error.state());
});
//is this a big deal? I think it is if you are using many libraries that need to speak the same asynchronous language. The alternative is callback nesting, callbacks, and other design patterns which can make code maintenance a brace and bracket hunt!

!

999px

🕑 One or more of the npm packages you are using needs to be built. You're the first person to ever need it! We're building it right now and your preview will start updating again when it's ready.