This guide often referrs to "Block and Inline formatting contexts" and how elements behave when part of these contexts. This guide details what formatting contexts are and how we can make use of the way they behave.
Everything on a page is part of a "formatting context", or an area which has been defined to lay out content in a particular way. A Block Formatting Context will lay child elements out according to Block Layout rules, a Flex Formatting Context will lay its children out as flex items, etc. Each formatting context has specific rules about how layout behaves when in that context.
The html
element defines the initial Block Formatting Context (BFC) for your page. This means all the elements inside <html></html>
lay themselves out according to Normal Flow following the rules for block and inline layout. Elements participating in a BFC use the rules outlined by the CSS Box Model, which defines how an element's margins, borders and padding interact with other blocks in the same context.
The html
element is not the only element capable of creating a new BFC. Other CSS properties will create a BFC too. This is useful because a new BFC will behave much like our document, becoming a mini-layout inside the main layout. A BFC will contain everything inside it, float and clear will only apply to items inside the same formatting context, and margins only collapse between elements in the same formatting context.
In addition to the root element of our document (the html
element) ,a new BFC is created in the following situations:
position: fixed
and position: sticky
display: inline-block
display: table-cell
, including anonymous table cells created when using the display: table-*
propertiesdisplay: table-caption
visible
display: flow-root
contain: layout
, content
, or strict
column-span: all
Let's have a look at a couple of these in order to see the effect creating a new BFC.
In the example below, we have a floated element inside a <div>
with a border applied. The content of that div
has floated alongside the floated element. As the content of the float is taller than the content alongside it, the border of the div now runs through the float. As explained in the guide to in-flow and out of flow elements, the float has been taken out of flo so the background and border of the div only contain the content and not the float.
Creating a new BFC would contain the float. A typical way to do this in the past has been to set overflow: auto
or set other values than the initial value of overflow: visible
.
Setting overflow: auto
created a new BFC containing the float. Our div
now becomes a mini-layout inside our layout. Any child element will be contained inside it.
The problem with using overflow
to create a new BFC is that the overflow
property is meant for telling the browser how you wish to deal with overflowing content. There are some occasions in which you will find you get unwanted scrollbars or clipped shadows when you use this property purely to create a BFC. In addition, it is potentially not very readable for a future developer, as it may not be obvious why you used overflow for this purpose. If you do this, it would be a good idea to comment the code to explain.
display: flow-root
A newer value of display
gives us the ability to create a new BFC without any other potentially problematic side-effects. Using display: flow-root
on the containing block will create a new BFC .
With display: flow-root;
on the div
, everything inside that container participates in the block formatting context of that container, and floats will not poke out of the bottom of the element.
The value name of flow-root
makes sense when you understand you are creating something that acts like the root
element (html
) in terms of how it creates a new context for the flow layout inside it.
Inline formatting contexts exist inside other formatting contexts and can be thought of as the context of a paragraph. The paragraph creates an inline formatting context inside which such things as strong
, a
, or span
elements are used on text.
The Box Model does not fully apply to items participating in an inline formatting context. In a horizontal writing mode line, horizontal padding, borders and margin will be applied to the element and push the text away left and right. However, margins above and below the element will not be applied. Vertical padding and borders will be applied but may overlap content above and below as, in the inline formatting context, the line boxes will not be pushed apart by padding and borders.
This guide covers flow layout and is therefore not referring to other possible formatting contexts. As such, it is useful to understand that creating any kind of formatting context will change the way elements inside that formatting context behave. This behaviour is always described in the specification and also here on MDN.
In this guide, we have looked in more detail at the Block and Inline formatting contexts and the important subject of creating a Block Formatting Context (BFC). In the next guide, we will find out how normal flow interacts with different writing modes.
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Flow_Layout/Formatting_Contexts_Explained