## BAD

#  This is invalid because the div (block level elment) is inside of the span (in-line element), and it displays/prints a div that in this case isn't needed for element positioning, and really it should be omitted.  Note that because we are using a separate print stylesheet unless we add the easyAdd definition to the print stylesheet we won't actually see the div's styling when we print the page.

<span class="noprint">
  <% if current_user.role.manage_community_classes? %>
	<div id="easyAdd"><%= link_to 'Add a Class', new_community_class_path %></div>
  <% end %>
</span>


## GOOD, BUT...

#  This validates, but it still prints the div...

<% if current_user.role.manage_community_classes? %>
	<div id="easyAdd"><span class="noprint"><%= link_to 'Add a Class', new_community_class_path %></div></span>
<% end %>


## IDEAL

# This validates and doesn't print the div.  The only problem is that if the div is already using a class it can't also use the "noprint" class, so... we lucked out here... and this is idea for situations like this... but the above example may need to be used in situations where a div class is already specified

<% if current_user.role.manage_community_classes? %>
	<div id="easyAdd" class="noprint"><%= link_to 'Add a Class', new_community_class_path %></div>
<% end %>


##  How else could all this be done?

# print.css could contain all of the same div definitions from screen.css that we do not want to print, but would need to use display:none; for each to keep them from printing.