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 URL's 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 it's URL and the proper URL extention.
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 Skypack, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ES6 import
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>@media tests</h1>
<div class="grid">
<div class="grid--item">
<h2>@media hover</h2>
<p>This works as normal across mobile and desktop (background colour changes on desktop with a mouse, doesn't on a touch device).</p>
<a href="#">A link to test hover</a>
<p>A slightly more complicated example to show more detail on a touch device to avoid missing information that would usually be revealed on hover.</p>
<a class="hover-example" href="#" title="#">
<div class="hover-example--inner">
<p class="heading">Fancy CTA</p>
<div class="content">
<p>Description explaining what happens you click this link</p>
<p>Find out more</p>
</div>
</div>
</a>
<p><a href="https://caniuse.com/?search=%40media%20hover" title="Check out the Can I use support around @media hover">Can I use</a> support for @media hover.</p>
</div>
<div class="grid--item">
<h2>@media pointer</h2>
<p>This checks the input capability and can be used to adjust styling accordingly. This example has an checkbox with varying sizes depending on pointer type.</p>
<input id="test" type="checkbox" />
<label for="test">Look at me!</label>
<p><a href="https://caniuse.com/?search=%40media%20pointer" title="Check out the Can I use support around @media pointer">Can I use</a> support for @media pointer.</p>
</div>
</div>
body {
padding: 2em;
}
.grid {
display: grid;
gap: 3em;
@media only screen and (min-width: 50em) {
grid-template-columns: repeat(2, minmax(0,1fr));
}
}
a,
a:visited {
color: hotpink;
text-decoration: underline;
@media (hover: hover) {
&:hover {
background: yellow;
text-decoration: none;
}
}
}
.hover-example,
.hover-example:visited {
background-color: hotpink;
color: white;
display: block;
max-width: 20em;
text-decoration: none;
transition: background-color .25s ease-in-out,
color .25s ease-in-out;
// Query to check if hovering is possible
@media (hover: hover) {
.hover-example--inner {
overflow: hidden;
.content {
transform: translateY(100%);
transition: transform .25s ease-in-out;
}
}
&:hover {
background-color: hotpink;
color: black;
.hover-example--inner {
.content {
transform: translateY(0);
}
}
}
}
}
.hover-example--inner {
display: flex;
flex-direction: column;
justify-content: flex-start;
padding: 1em;
.heading {
font-size: 2em;
margin: 0 0 auto;
text-transform: uppercase;
}
.content {
margin: 2em 0 0;
p {
&:last-child {
margin: 0;
}
}
}
}
/* =MDN example - https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pointer
NOTE - This is for primary input device, not ALL input devices (that's any-pointer, works similiary)
----------------------------------------- */
input[type="checkbox"] {
-moz-appearance: none;
-webkit-appearance: none;
appearance: none;
border: solid;
margin: 0;
}
input[type="checkbox"]:checked {
background: gray;
}
// Query to check for things like a mouse, touchpad, drawing tablet
@media (pointer: fine) {
input[type="checkbox"] {
border-width: 1px;
border-color: blue;
height: 15px;
width: 15px;
}
}
// Query to check for things like a remote control i.e. tvs or consoles. NOTE - Also picked up on mobiles (when testing on iPhone 7+) and when using Dev Tools and selecting a mobile view
@media (pointer: coarse) {
input[type="checkbox"] {
border-width: 2px;
border-color: red;
height: 30px;
width: 30px;
}
}
// Query to check for no input i.e. mobiles. NOTE - Tough to replicate when 'none' is true
@media (pointer: none) {
input[type="checkbox"] {
border-width: 2px;
border-color: green;
height: 15px;
width: 30px;
}
}
// Combining the two queries? Allows targetting specific device sets
// Taken from https://www.smashingmagazine.com/2022/03/guide-hover-pointer-media-queries/
@media (hover: none) and (pointer: coarse) {
// Smartphones and touchscreens
}
@media (hover: none) and (pointer: fine) {
// Stylus devices / screens
}
@media (hover: hover) and (pointer: coarse) {
// TVs and consoles
}
@media (hover: hover) and (pointer: fine) {
// Standard desktops / laptops
}
Also see: Tab Triggers