Pen Settings

HTML

About HTML Preprocessors

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.

Learn more · Versions

Adding Classes

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.

About the <head>

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.

!
Insecure Resource

The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.

CSS

About CSS Preprocessors

CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.

Learn more · Versions

CSS Base

About CSS Base

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.

Vendor Prefixing

About Vendor Prefixing

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).

Add External Stylesheets/Pens

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.

Powered by Algolia
About External Resources

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.

Learn more

+ add another resource

JavaScript

About JavaScript Preprocessors

JavaScript preprocessors can help make authoring JavaScript easier and more convenient.

Learn more · Versions

Babel includes JSX processing.

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.

Powered by Algolia
About External Resources

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.

Learn more

+ add another resource

Packages

Add Packages

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.

Powered by Algolia
About Packages

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.

Behavior

Auto Save

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.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.

HTML 

              
                <!DOCTYPE HTML>

<html>

	<head>

		<meta charset="UTF-8">

		<meta name="viewport" content="width=device-width, initial-scale=1.0">

		<link rel="stylesheet" type="text/css" href="style.css"/>

		<title>

		CSS NULL CELL TOKEN TEST CASE

		</title>

	</head>

	<body>

		<div id="container">

			<div id="header">CSS NULL CELL TOKEN TEST CASE</div>

      <div id="text">
        
        <p>
          
          <b>To Whom It May Concern:</b>
        
        </p>
        
        <br>
        
        <p>
          
          As per the current CSS Grid spec, it seems <strong>Null Cell Tokens</strong> placed in <b>ROWS</b> after the <b>LAST</b> grid item are not supposed to contribute anything to the grid vertical dimensions.
          
        </p>
        
        <br>
        
        <p>
          
          Fortunately, Google Chrome, as per version 72.0.3626.96 does take into account <strong>Null Cell Tokens</strong> placed after the last grid item to contribute to its parent vertical dimensions, which to me, seems the most logical too.
        
        </p>
        
        <br>
        
        <p>
          
          It is easier to layout your whole website with one grid, while being able to center all your items both vertically and horizontally with the use of Fr units on Null Cell Tokens.
          
        </p><br>
        
        <p>
          
          This CODE PEN will run differently on Firefox because of this issue.
          
        </p>
        
        <br>
        
        <p>
          
          <img src="http://charbelnicolas.com/cipher/img/chromevsfirefox.png">
          
        </p>
        
        <br>
          
        <p>
          
          If you check the CSS code, you can see the <b><i>minmax(2rem, 1fr)</i></b> set on the first row and on the last one will always center the grid items vertically on the whole viewport without the need of anything else. I think it is counterintuitive to allow the use of Null Cell Tokens on the top row and in between items but not at the last row in the grid.
          
        </p>
        
        <br>
          
        <p>
          
          You could argue that while not the best solution, it would be easy just to name the <b><i>grid-area</i></b> where the Null Cell Token is and add a <b><i>div</i></b> to the html, but why do it when Google Chrome's solution is already so elegant? Why clutter the CSS and HTML files with more lines of code?
          
        </p>
        
        <br>
          
        <p>
          
          Or better yet, please tell me why it shouldn't work like it already does in Google Chrome. Why not make things easier for everyone and more intuitive?
          
        </p>
          
        <br>
          
        <p>
          
          <i>Please check this CODE PEN on Chrome and on Firefox to see the difference. A scrollbar must be present to see the issue. The box containing this text should <b>NOT</b> touch the bottom of the browser window.</i>
          
        </p>
        
		</div>

	</body>

</html>
!

CSS 

              
                * {
	box-sizing: border-box;
	color: rgb(255, 255, 255);
	font-family: 'Dosis', sans-serif;
	font-size: 16pt;
}

body {
	background-color: rgb(117, 154, 184);
	padding: 0;
	margin: 0;
}

#container {
	display: grid;
	height: 100vh;
	width: 100vw;
	overflow: auto;
	grid-template-columns: 1fr 60vw 1fr;
	grid-template-rows: minmax(2rem, 1fr) auto 1rem auto minmax(2rem, 1fr);
	grid-template-areas:
		". . ."
		". header ."
		". . ."
		". text ."
		". . .";
}

#header {
	grid-area: header;
	font-size: 2rem;
	line-height: 2rem;
	font-weight: 600;
	text-align: center;
	user-select: none;
}

#text {
	grid-area: text;
	background-color: rgb(70, 154, 184);
	padding: 2rem;
	border: solid 1px;
	overflow-wrap: break-word;
}

p {
  padding: 0;
  margin: 0;
}
!

JS
!
999px

Console