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.
<article class="post">
<header class="post-header">
<div class="content post-header-inner">
<h1>Fixed backgrounds on a mobile browser without using JavaScript!</h1>
<time class="post-date">October 6th 2016</time>
<div class="post-meta">
<span class="author">by <span class="author-name">Brian Hayes</span></span>
</div>
</div>
</header>
<div class="post-content">
<div class="content">
<a href="https://joeyred.github.io/fixed-mobile-background-demo/" target="_blank"><h2>Click Here to See the Working Demo on GitHub</h2></a>
<p class="note"><span>PLEASE NOTE:</span> It seems that when being rendered on iOS Safari through CodePen, the actual height of the viewport isn't correctly calculated. The calculated height ends up being the height of the entire document, and not the viewport. So, yes this method does work, but it doesn't render correctly on CodePen on mobile. I've set up <a href="https://joeyred.github.io/fixed-mobile-background-demo/" target="_blank">a demo page on GitHub</a> that shows that this does in fact work.</p>
<p>Quid securi etiam tamquam eu fugiat nulla pariatur. Cum ceteris in veneratione tui montes, nascetur mus. Quisque placerat facilisis egestas cillum dolore. Ambitioni dedisse scripsisse iudicaretur. Quisque ut dolor gravida, placerat libero vel, euismod.</p>
<p>Fabio vel iudice vincam, sunt in culpa qui officia. Paullum deliquit, ponderibus modulisque suis ratio utitur. Quisque ut dolor gravida, placerat libero vel, euismod. Inmensae subtilitatis, obscuris et malesuada fames. Salutantibus vitae elit libero, a pharetra augue. Magna pars studiorum, prodita quaerimus. Excepteur sint obcaecat cupiditat non proident culpa. Curabitur est gravida et libero vitae dictum.</p>
<p>Integer legentibus erat a ante historiarum dapibus. Etiam habebis sem dicantur magna mollis euismod. Non equidem invideo, miror magis posuere velit aliquet. Fabio vel iudice vincam, sunt in culpa qui officia. Donec sed odio operae, eu vulputate felis rhoncus. Prima luce, cum quibus mons aliud consensu ab eo. Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Non equidem invideo, miror magis posuere velit aliquet. Quis aute iure reprehenderit in voluptate velit esse. At nos hinc posthac, sitientis piros Afros.</p>
<p>Non equidem invideo, miror magis posuere velit aliquet. Phasellus laoreet lorem vel dolor tempus vehicula. Etiam habebis sem dicantur magna mollis euismod. A communi observantia non est recedendum. Quisque placerat facilisis egestas cillum dolore. Plura mihi bona sunt, inclinet, amari petere vellent. Nec dubitamus multa iter quae et nos invenerat. Vivamus sagittis lacus vel augue laoreet rutrum faucibus. Quam temere in vitiis, legem sancimus haerentia.</p>
</div>
</div>
</article>
<footer>
<div class="content">
<h2>There you have it!</h2>
<p>
A totally fixed background without ever having to deal with javascript, or even fake elements. A complete HTML & CSS solution.
</p>
<h3>
<a href="https://joeyred.github.io/fixed-mobile-background-demo/" target="_blank">
Click Here to See the Working Demo on GitHub
</a>
</h3>
<p class="note"><span>PLEASE NOTE:</span> It seems that when being rendered on iOS Safari through CodePen, the actual height of the viewport isn't correctly calculated. The calculated height ends up being the height of the entire document, and not the viewport. So, yes this method does work, but it doesn't render correctly on CodePen on mobile. I've set up <a href="https://joeyred.github.io/fixed-mobile-background-demo/" target="_blank">a demo page on GitHub</a> that shows that this does in fact work.</p>
<hr />
<p>Background photo by <a href="https://unsplash.com/@scottwebb">Scott Webb</a> from <a href="https://unsplash.com/photos/Yohivf5JWvg">unsplash.com</a></p>
</div>
</footer>
// This is what makes the background right here.
html::before {
content: ' ';
display: block;
background-image: url('https://images.unsplash.com/photo-1427694012323-fb5e8b0c165b');
background-position: center;
background-size: cover;
height: 100vh;
width: 100vw;
top: 0;
bottom: 0;
left: 0;
right: 0;
position: fixed;
z-index: -10; // This is pretty important.
}
// This is just the stuff to make the pen look pretty.
html {
font-family: "source sans pro";
font-weight: 400;
color: #fdfdfd;
}
h1, h2, h3 {
font-family: lato;
font-weight: 300;
text-transform: uppercase;
letter-spacing: 1px;
}
a {
text-decoration: none;
color: #FFC74E;
transition: color 200ms ease-in-out;
&:hover, &:focus {
color: #C84EFF;
}
}
hr {
border: #555 1px solid;
}
.post {
font-size: 1.125rem;
}
.content {
max-width: 50rem;
margin: 0 auto;
}
.post-header-inner {
display: flex;
flex-flow: column nowrap;
min-height: 25rem;
padding: 0.5rem 1.5rem;
// text-shadow: 1px 1.5px 4px rgba(167, 221, 255, 0.8);
text-shadow: 0.5px 2px 2px rgba(1, 1, 1, 0.4);
h1 {
font-size: 2rem;
color: #333;
}
.post-date {
color: #B28B36;
}
.post-meta {
width: 100%;
margin-top: auto;
color: #FFF;
text-shadow: 1px 1.5px 4px rgba(1, 1, 1, 0.8);
}
.author-name {
font-size: 1.3rem;
font-weight: 400;
}
}
.post-content {
background: rgba(0, 0, 0, 0.6);
backdrop-filter: blur(18px);
padding: 1rem 1.5rem;
}
.note {
color: #D3D3D3;
border: 3px solid red;
padding: 0.625rem;
span {
font-weight: bold;
color: red;
}
}
footer {
padding: 1rem 1.5rem;
background-color: #222;
padding-bottom: 4rem;
}
Also see: Tab Triggers