This fixes a glitch highlighted in #3259, where the css class stopped applying
when the view was moved to a different controller.
We're moving to having each view responsible for their layout, and commonly having
override classes explicitly in the relevant views. So we can follow that pattern here.
/* Overrides for pages that use new layout conventions */
-.users-new,
-.users-create,
-.users-terms,
-.users-confirm {
- .content-heading .content-inner {
- height: 200px;
- }
+.header-illustration-heading {
+ height: 200px;
}
.header-illustration {
+<% content_for :heading_class, "header-illustration-heading" %>
<% content_for :heading do %>
<h1><%= t ".heading" %></h1>
<div class='header-illustration confirm-main'></div>
+<% content_for :heading_class, "header-illustration-heading" %>
<% content_for :heading do %>
<h1><%= t "users.new.title" %></h1>
<div class='header-illustration new-user-main'></div>
<%= javascript_include_tag "user" %>
<% end %>
+<% content_for :heading_class, "header-illustration-heading" %>
<% content_for :heading do %>
<h1><%= t ".title" %></h1>
<div class='header-illustration new-user-main'></div>
<%= javascript_include_tag "user" %>
<% end %>
+<% content_for :heading_class, "header-illustration-heading" %>
<% content_for :heading do %>
<h1><%= t ".heading" %></h1>
<div class='header-illustration new-user-terms'></div>