Pen Settings

CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URL's added here will be added as <link>s in order, and before the CSS in the editor. If you link to another Pen, it will include the CSS from that Pen. If the preprocessor matches, it will attempt to combine them before processing.

+ add another resource

You're using npm packages, so we've auto-selected Babel for you here, which we require to process imports and make it all work. If you need to use a different JavaScript preprocessor, remove the packages in the npm tab.

Add External Scripts/Pens

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.

+ add another resource

Use npm Packages

We can make npm packages available for you to use in your JavaScript. We use webpack to prepare them and make them available to import. We'll also process your JavaScript with Babel.

⚠️ This feature can only be used by logged in users.

Code Indentation


Save Automatically?

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

HTML Settings

Here you can Sed posuere consectetur est at lobortis. Donec ullamcorper nulla non metus auctor fringilla. Maecenas sed diam eget risus varius blandit sit amet non magna. Donec id elit non mi porta gravida at eget metus. Praesent commodo cursus magna, vel scelerisque nisl consectetur et.

	<legend>What is the question?</legend>
	<input type="radio" id="tobe" name="radiobutton" value="Be" checked>
	<label for="tobe">To Be</label>
	<input type="radio" id="orradio" name="radiobutton" value="Or">
	<label for="orradio">Or</label>
	<input type="radio" id="nottobe" name="radiobutton" value="Not Be">
	<label for="nottobe">Not to Be</label>
              @supports(-webkit-appearance: none) {
/* 	AKA, only do this if `-webkit-appearance: none` is supported. 
	Which means IE11 and Opera Mini will get the old browser-styled checkbox. 
	Which works just fine. Old browsers can get old looking things. */
 	input[type="radio"] , 
	fieldset input[type="radio"] {
		/*  Remove the default styling.
		    `-webkit-appearance` is not an official CSS property 
			& likely never will be. But it's also in 95% of browsers, 
			non-webkit included, yes, as a `-webkit` property. 
			Firefox, Edge, Chrome, Opera all implemented `-webkit-appearance`.  
			Plus it *will* stick around. Browsers can't remove it. 
			So use it like this...                                 */
		-webkit-appearance: none;
		/* Style the radio button container. */
		width: 1.4rem;
		height: 1.4rem;
		border-radius: 50%;
		border: 1px solid #808080;
		margin: 0.3rem 0 0 0;
		padding: 0;
	fieldset input[type="radio"]:checked {
		/* Prepare for placing the new checkmark. */
		position: relative;
		/* Do a bug fix to keep iOS from adding dark background. */
		background: none;
	fieldset input[type="radio"]:checked::after {
		/* Place (position) the new “filled-in” blob. */
		position: absolute;
		top: 0.3rem;
		left: 0.3rem;
		width: 0.7rem;
		height: 0.7rem;
		background: #0c4364;
		border-radius: 50%;
		content: "";
	/* Focus styles. */
	fieldset:focus-within  {
		border-color: #0b8663;
	fieldset:focus-within legend {
		color: #0b8663;
	fieldset input[type="radio"]:focus {
		border: 1px solid teal;

	/* Layout for the Fieldset. Needs work. To be continued... */
	fieldset {
		display: grid;
		grid-template-columns: min-content 1fr;
		margin: 3rem 0;
		border: 1px solid #808080;
		grid-column: 2;
		min-width: 12rem; /* this is a hack. hmmf. */
	legend {
		margin: 0 0 0.5rem -1rem;
		padding: 0.6rem 0.5rem 0.4rem 0.8rem;	
		color: black;
		background: #eee;
		width: fit-content;
	label {
		display: block;
		padding: 0.6rem 0 0.5rem 0.6rem;

/* Add a bit of styling to the page & typography. Totally optional. */
body {
	margin: 2rem;
	font-family: Avenir, Roboto, sans-serif;
🕑 One or more of the npm packages you are using needs to be built. You're the first person to ever need it! We're building it right now and your preview will start updating again when it's ready.