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.
<header>
<nav>
<ul class="nav">
<li>
<a href="#0">Dropdown Menu <svg class="icon" viewBox="0 0 320 512" width="100" title="caret-down">
<path d="M31.3 192h257.3c17.8 0 26.7 21.5 14.1 34.1L174.1 354.8c-7.8 7.8-20.5 7.8-28.3 0L17.2 226.1C4.6 213.5 13.5 192 31.3 192z" />
</svg></a>
<ul class="submenu">
<li><a href="#0">One</a></li>
<li><a href="#0">Two</a></li>
<li><a href="#0">Three</a></li>
</ul>
</li>
<li>
<a href="#0">Dropdown Menu <svg class="icon" viewBox="0 0 320 512" width="100">
<path d="M31.3 192h257.3c17.8 0 26.7 21.5 14.1 34.1L174.1 354.8c-7.8 7.8-20.5 7.8-28.3 0L17.2 226.1C4.6 213.5 13.5 192 31.3 192z" />
</svg></a>
<ul class="submenu">
<li><a href="#0">One</a></li>
<li><a href="#0">Two</a></li>
<li><a href="#0">Three <svg class="icon icon-rotate" viewBox="0 0 320 512" width="100">
<path d="M31.3 192h257.3c17.8 0 26.7 21.5 14.1 34.1L174.1 354.8c-7.8 7.8-20.5 7.8-28.3 0L17.2 226.1C4.6 213.5 13.5 192 31.3 192z" />
</svg></a>
<ul class="submenu submenu-2">
<li><a href="#0">One</a></li>
<li><a href="#0">Two</a></li>
</ul>
</li>
<li><a href="#0">Four</a></li>
<li><a href="#0">Five</a></li>
</ul>
</li>
</ul>
</nav>
</header>
header {
background: oklch(35% 3% 265deg);
border-bottom: 1px solid oklch(44% 3% 265deg);
}
.nav {
display: flex;
justify-content: center;
gap: 2rem;
li {
/* Submenus are absolutely positioned within */
position: relative;
/* for mouse users this works, but list items themselves aren't focusable, hence the next line */
&:hover > a,
/* if any link inside is hovered or has focus, then keep that menu open! */
&:has(a:hover, a:focus) {
/* Ya know what actually, it would be fun to set like `--dropdown-open: true` here and move the styles out to a style query instead of nesting this deeply. */
> a + .submenu {
/* block-size fallback for browsers that can't animate to auto */
block-size: auto;
block-size: calc-size(auto);
border: 2px solid oklch(38% 3% 265deg);
/* this isn't really needed unless the menu isn't in the DOM at all to start or you intentionally wanted to `display: none` the submenus, which is generally a bad plan. */
/*
@starting-style {
block-size: 0;
}
*/
}
}
> a {
display: flex;
gap: 0.25rem;
padding: 1rem 0.5rem;
color: #cfd8dc;
&:hover,
&:focus {
color: white;
/* May want to do nicer focus styles that don't look cut off. */
svg {
opacity: 1;
translate: 0 1px;
}
}
}
}
}
.submenu {
/* For anything at "opens and closes" `ease-in-out` is decently nice */
transition: 0.15s ease-in-out;
/* If we were animating from `display: none;` then `transition-behavior` would help make that work, but we don't need it here. Actually, for menus like this, `display: none` is bad news as it means we wouldn't be able to tab through the items properly. */
/* transition-behavior: allow-discrete; */
/* Funny how you need to replicate this in @starting-style if you need that because of `display: none` */
block-size: 0;
/* Might as well let it grow wider if it needs to */
inline-size: max-content;
min-inline-size: 100%;
position: absolute;
top: calc(100% - 5px);
left: 15px;
background: oklch(24% 3% 265deg);
border-radius: 12px;
/* You can clip directionally with `clip` which is awesome. This could be a bug though, if a sub-sub menu went lower vertically down than the sub menu. */
overflow-y: clip;
overflow-x: visible;
li {
a {
display: flex;
color: white;
padding: 0.6rem 1.2rem;
&:hover,
&:focus {
background: oklch(45% 3% 265deg);
}
}
/* gotta do this cause can't fully clip overflow */
&:first-child a {
/* 12px border radius - 2px border = 10px */
border-top-left-radius: 10px;
border-top-right-radius: 10px;
}
&:last-child a {
border-bottom-left-radius: 10px;
border-bottom-right-radius: 10px;
}
}
}
.icon {
/* push right arrow to right */
margin-inline-start: auto;
fill: white;
opacity: 0.5;
inline-size: 0.7em;
transition: 0.1s ease-in-out;
&.icon-rotate {
rotate: -90deg;
}
}
/* Sub-sub menus */
.submenu-2 {
top: -5px;
left: 80%;
z-index: 1;
}
@layer foundation {
body {
font: 100% system-ui, sans-serif;
background: oklch(18% 3% 268deg);
margin: 0;
overflow: clip;
}
ul {
list-style: none;
padding: 0;
margin: 0;
a {
text-decoration: none;
}
* {
box-sizing: border-box;
}
}
// This was useful in some testing I was doing.
// setInterval(() => {
// console.log(document.activeElement);
// }, 250);
Also see: Tab Triggers