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.
<!-- We now give the menu a class as well as an id, we'll change the class with JavaScript to alter the styleing -->
<ul id="menu" class="menu-up">
<!-- The menu item ID's are the section ID's with the word "link" added to the end -->
<li id="aboutlink" class="menu-link">About Me</li>
<li id="portfoliolink" class="menu-link">Portfolio</li>
<li id="bloglink" class="menu-link">Blog</li>
</ul>
<!-- The wrapper gets a class too -->
<div id="wrapper" class="wrapper-up">
<header>
<!-- clicking this word will check and uncheck the checkbox -->
<p id="show-menu">Menu</p>
<h1>Mobile Push Menu and smooth scrolling anchor links with JavaScript</h1>
<p>Click on the word Menu above to open or close the menu.</p>
<p>The anchor links on this page are no longer done with html. The Javascript now calculates the position the scrollbar is at using the body.scrollTop property and the position the browser should scroll to using the element.offsetTop property. Then in scrolls incrementally using the scrollBy method. The setInterval method is used to repeat the scrollBy method every 5 milliseconds.</p>
<h2>Potential Problems</h2>
<p>Currently the mouse cursor doesn't change to a pointer when hovering over these links, which could be confusing. That's easily fixed with CSS and :hover.</p>
<p>The scrolling happens at a constant speed. It might be made nicer with an ease-in and/or ease-out, but that would require a bit more code.</p>
<p>This works well in Chrome and Safari but IE and Firefox won't recognize <em>document.body.scrolltop</em>. The prefer <em>document.documentElement.scrollTop</em>. To accomodate both, replace <em>document.body.scrolltop</em> with <em>(document.documentElement && document.documentElement.scrollTop) || document.body.scrollTop</em></p>
<p>These links are now completely useless if JavaScript is disabled. To make them still functional we could have left the orignal anchor tags in place and then added <em>return: false</em> to the onclick even handlers.</p>
</header>
<section id="about">
<h2>About Me</h2>
<p class="top">Back to top</p>
</section>
<section id="portfolio">
<h2>Portfolio</h2>
<p class="top">Back to top</p>
</section>
<section id="blog">
<h2>Blog</h2>
<p class="top">Back to top</p>
</section>
</div>
/* We move the positioning and the transition into the menu and wrapper's various classes because they're subject to change. */
#menu {
position: absolute;
}
#wrapper {
position: relative;
}
/* The 'up' classes are the default state where the elements are positioned on page load */
.menu-up {
-webkit-transition: top .3s ease-in;
transition: top .3s ease-in;
top: -5em;
}
.wrapper-up {
-webkit-transition: top .3s ease-in;
transition: top .3s ease-in;
top: 0;
}
/* The 'down' classes shift the elements when the menu button is clicked. */
.menu-down {
-webkit-transition: top .3s ease-in;
transition: top .3s ease-in;
top: 0em;
}
.wrapper-down {
-webkit-transition: top .3s ease-in;
transition: top .3s ease-in;
top: 5em;
}
/* The 'off' classes move the menu to the same position as the up classes. The difference is we turn off the transition so that the canvas doesn't scroll up after we jump to a link further down the page. */
.menu-off {
-webkit-transition-property: none;
transition-property: none;
top: -5em;
}
.wrapper-off {
-webkit-transition-property: none;
transition-property: none;
top: 0em;
}
/* Unnecessary styling stuff */
#menu {
background-color: #FAD89B;
width: calc(100% - 56px);
}
header, section {
height: 1000px;
}
header {
background-color: #B598A2;
}
#about {
background-color: #73799E;
}
#portfolio {
background-color: #809E90;
}
#blog {
background-color: #BCBD9C;
}
document.getElementById("show-menu").onclick=function toggleMenu() {
if (document.getElementById("menu").className == "menu-up"
|| document.getElementById("menu").className == "menu-off") {
document.getElementById("menu").className = "menu-down";
document.getElementById("wrapper").className = "wrapper-down";
} else {
document.getElementById("menu").className = "menu-up";
document.getElementById("wrapper").className = "wrapper-up";
}
} //this function toggles the menu and wrapper between up and down positions
var menuLinks = document.getElementsByClassName("menu-link"); //An array containing the three menu links.
var clickedSection; // Will store the section ID after a link is clicked
var timer; // Stores the interval which makes the scrolling possible
var topLinks = document.getElementsByClassName("top"); // Contains the 'return to top links'
var fromTop; //Will store how far from the top the scrollbar is
var vOffset; //will store how far from the top an element is.
var scrollSpeed = 20; //This variable alters the scroll speed
for (i=0; i<=3; i++) {
if (menuLinks[i]) {
menuLinks[i].addEventListener("click", function() {
clickedSection = this.id.replace("link",""); //Saves the name of the section the user has selected
menuSelect();
});
}
}
function menuSelect() {
document.getElementById("menu").className = "menu-off";
document.getElementById("wrapper").className = "wrapper-off";
vOffset = document.getElementById(clickedSection).offsetTop; //Calculates how far in pixels the selected element is from the top
fromTop = document.body.scrollTop; //Calculates how far in pixels the current scroll position is from the top
timer = setInterval(scrollDown, 5); //calls the function scrollDown once every 5 milliseconds until clearInterval is applied
}
for (i=0; i<topLinks.length; i++) {
topLinks[i].addEventListener("click", function() {
fromTop = document.body.scrollTop; //Calculates how far in pixels the current scroll position is from the top
timer = setInterval(scrollUp, 5); //calls the function scrollUp once every 5 milliseconds until clearInterval is applied
})
}
function scrollUp(){
window.scrollBy(0, -scrollSpeed); //Scrolls up by the number of pixes specified by scrollSpeed
fromTop -= scrollSpeed; //Updates fromTop to the current position
if (fromTop <= 0) {
clearInterval(timer);
} //stops scrolling when top is reached
}
function scrollDown(){
window.scrollBy(0, scrollSpeed); //Scrolls down by the number of pixes specified by scrollSpeed
fromTop += scrollSpeed; //Updates fromTop to the current position
if (fromTop >= vOffset) {
clearInterval(timer);
} //stops scrolling when selected element is reached
}
Also see: Tab Triggers