HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.
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.
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.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
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.
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-
.
We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).
Any URLs added here will be added as <link>
s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.
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.
You can also link to another Pen here (use the .css
URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
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.
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.
Search for and use JavaScript packages from npm here. By selecting a package, an import
statement will be added to the top of the JavaScript editor for this package.
Using packages here is powered by esm.sh, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ESM usage.
All packages are different, so refer to their docs for how they work.
If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
Visit your global Editor Settings.
<h1>Detect Transition Start</h1>
<p>There is no method for detecting a css transition start in JavaScript. This demo uses the transitionEnd event in a sneaky way to detect transition start.</p>
<p>It requires wrapping the transitionEnd event with a custom event 'transition-end'. This alone is useful for dealing with browser prefixes.</p>
<p>But this solution is not yet ideal. It also requires some specific css with an invisible 0.00001s transition to detect the start. It doesn't matter what property you transition but it must change. The search for a better solution continues...<p>
<a id="hover-me">Hover me</a>
<div id="transition-status"></div>
<p>This could be useful in cases similar to how the window resize event is used. If the height or width of a container is changing with css transitions, you may wish to update something during the transition. Not just when it ends.<p>
#hover-me{
transition: opacity 0.00001s linear, color 3s linear; /* must be 0.00001s. 0s did not work :( */
background: #CCC;
padding: 10px;
border-radius: 10px;
border: solid 1px;
display: inline-block;
}
#hover-me:hover{
opacity: .999999; /* Doesn't matter what property but it must change */
color: red;
cursor: pointer;
}
#transition-status{
margin: 1em 0;
}
// Detect which transition event (from modernizer)
var whichTransitionEvent = function(){
var t;
var el = document.createElement('fakeelement');
var transitions = {
'transition':'transitionend',
'OTransition':'oTransitionEnd',
'MozTransition':'transitionend',
'WebkitTransition':'webkitTransitionEnd'
};
for(t in transitions){
if( el.style[t] !== undefined ){
return transitions[t];
}
}
};
var transitionEvent = whichTransitionEvent();
if(transitionEvent){
// Set-up transition-start custom event
if (window.CustomEvent) {
var transitionStartEvent = new CustomEvent('transition-start',{'bubbles': true, 'cancelable': true});
var transitionEndEvent = new CustomEvent('transition-end',{'bubbles': true, 'cancelable': true});
} else {
var transitionStartEvent = document.createEvent('CustomEvent');
var transitionEndEvent = document.createEvent('CustomEvent');
transitionStartEvent.initCustomEvent('transition-start', true, true);
transitionEndEvent.initCustomEvent('transition-end', true, true);
}
document.body.addEventListener(transitionEvent, function(evnt) {
// Guard detect and trigger transition start here
var target = evnt.target || evnt.srcElement;
console.log(evnt.elapsedTime);
// FF does not report the exact time here.
if(evnt.elapsedTime <= 0.00001){
evnt.target.dispatchEvent(transitionStartEvent);
} else {
evnt.target.dispatchEvent(transitionEndEvent);
}
});
}
var statusElm = document.getElementById("transition-status");
var hoverElm = document.getElementById("hover-me");
hoverElm.addEventListener('transition-start', function() {
var d = new Date();
statusElm.innerHTML = d.getHours() +':'+ d.getMinutes() +':'+ d.getSeconds() +':'+ d.getMilliseconds() +' Transition has started.';
});
hoverElm.addEventListener('transition-end', function() {
var d = new Date();
statusElm.innerHTML = d.getHours() +':'+ d.getMinutes() +':'+ d.getSeconds() +':'+ d.getMilliseconds() +' Transition has ended.';
});
Also see: Tab Triggers