<pclass="component-description">Title bars can also house segmented controllers (with or without accompanying buttons). It all uses flex-box to create perfectly even spacing no matter their labels.</p>
<pclass="component-description">Popovers are designed to only fire from <ahref="#bars">title bars</a>. Set the value of the title href to the id of a popover, like so:</p>
<pclass="component-note">This will use push to replace everything in the .content div with the .content of two.html. Also, it will either update or remove .bar-title and .bar-tab according to their presences in two.html.</p>
<pclass="component-note">This will use push to replace everything in the .content div with the .content of two.html. Also, it will either update or remove .bar-nav and .bar-tab according to their presences in two.html.</p>
<pclass="component-description">Now that pages are being loaded through push, it's easy to specify transitions for animations between pages. There are three different transitions to chose from: <code>fade</code>, <code>slide-in</code>, or <code>slide-out</code>.</p>
@ -1030,7 +1030,7 @@ document
<pclass="component-description">A working version of push:</p>
<h3class="step-title">1. Fixed bars come first</h3>
<pclass="step-description">All fixed bars (<code>.bar-title, .bar-tab, .bar-header-secondary, .bar-footer</code>) should always be the first thing in the <code><body></code> of the page. This is really important!</p>
<pclass="step-description">All fixed bars (<code>.bar-nav, .bar-tab, .bar-header-secondary, .bar-footer</code>) should always be the first thing in the <code><body></code> of the page. This is really important!</p>
</li>
<liclass="step">
<h3class="step-title">2. Everything else goes in <code>.content</code></h3>