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.
<share-actions>
<p>Copy this link to share with your friends</p>
<p>
<code>https://example.com</code>
</p>
</share-actions>
.share-actions li {
position: relative;
}
.share-actions [role="alert"] {
position: absolute;
inset: 0;
align-content: center;
text-align: center;
text-transform: uppercase;
letter-spacing: var(--uppercase-kerning);
font-weight: var(--font-bold);
font-size: var(--size-step-00);
background: var(--color-primary);
color: var(--color-light);
}
.share-actions [role="alert"]:empty {
display: none;
}
class ShareActions extends HTMLElement {
constructor() {
super();
}
// Returns a url prop value or the current page url as a fallback
get url() {
return this.getAttribute("url") || window.location.href;
}
// Returns a title prop value or the page <title>
get title() {
return this.getAttribute("title") || document.title;
}
// Looks for a meta description and extracts the value if it is found. Returns an empty string if not
get description() {
const metaDescriptionElement = document.querySelector(
'meta[name="description"]'
);
return metaDescriptionElement
? metaDescriptionElement.getAttribute("content")
: "";
}
// Determine if this browser can use the share API
get hasShareSupport() {
return navigator.share;
}
// Determine if this browser can use the clipboard API
get hasClipboardSupport() {
return navigator.clipboard;
}
// Takes the event trigger context (<button>), triggers the share API, then passes that
// context and alert text to the renderAlert method
triggerShare(context) {
navigator
.share({
title: this.title,
url: this.url,
text: this.description
})
.then(() => {
this.renderAlert("Thanks!", context);
})
.catch((error) => console.error("Error sharing", error));
}
// Takes the event trigger context (<button>), triggers the clipboard API, then passes that
// context and alert text to the renderAlert method
copyToClipboard(context) {
navigator.clipboard
.writeText(this.url)
.then(() => {
this.renderAlert("Copied!", context);
})
.catch((error) => console.error(error));
}
// Takes message text, the event context and an optional millisecond value for clearing the
// alert. It then renders that as a sibling (to the button) alert element *or* a local alert
// element to this component. If neither are available, nothing happens here.
renderAlert(text, context, clearTime = 3000) {
const alert = context
? context.nextElementSibling
: this.querySelector('[role="alert"]');
if (alert) {
alert.innerText = text;
setTimeout(() => {
alert.innerText = "";
}, clearTime);
}
}
// Takes an event, works out the method based on the trigger's 'data-method' attribute
// then invokes the right event handler
handleClick(event) {
const method = event.currentTarget.dataset.method;
switch (method) {
case "share":
this.triggerShare(event.currentTarget);
return;
case "clipboard":
this.copyToClipboard(event.currentTarget);
return;
}
}
// Finds all buttons and attaches a click event to our handler
assignEvents() {
const buttons = this.querySelectorAll("button");
if (buttons.length) {
buttons.forEach((button) =>
// Without doing this approach of invoking the event handler and instead
// passing the function right in `this.handleClick` the following won't work:
// 1. 'this' is out of scope so the trigger methods can't be found in our event handler
// 2. event.currentTarget doesn't work which is needed to ensure the event trigger and not its children
// is always the correct target in our handler
button.addEventListener("click", (event) => this.handleClick(event))
);
}
}
connectedCallback() {
// No support is available for either share or clipboard APIs so we bail out here
// and let the component's child HTML take over
if (!this.hasShareSupport && !this.hasClipboardSupport) {
console.log("No support so revert to MVE");
return;
}
// Support of at least one API is available so now we render those buttons conditionally
this.innerHTML = `
<ul class="share-actions cluster" role="list">
${
this.hasShareSupport
? `
<li>
<button class="button" data-method="share">Share</button>
<div role="alert"></div>
</li>
`
: ""
}
${
this.hasClipboardSupport
? `
<li>
<button class="button" data-method="clipboard">Copy URL</button>
<div role="alert"></div>
</li>
`
: ""
}
</ul>
`;
// Buttons are now rendered so we can assign the events
this.assignEvents();
}
}
customElements.define("share-actions", ShareActions);
Also see: Tab Triggers