Added Header and Footer support using Skia

chrome/browser/resources/print_preview/print_preview.html

Index: chrome/browser/resources/print_preview/print_preview.html
diff --git a/chrome/browser/resources/print_preview/print_preview.html b/chrome/browser/resources/print_preview/print_preview.html
index 0aef75cc92dffbda6e4ca1cbb6fc5ec64bde9786..888517f8854ebcc1473afdfbe809530ca8008b35 100644
--- a/chrome/browser/resources/print_preview/print_preview.html
+++ b/chrome/browser/resources/print_preview/print_preview.html
@@ -56,6 +56,15 @@
         </div>
       </div>
       <hr>
+      <div id="options-option" class="two-column option visible">

[dpapad, 2011/07/19 15:38:04]

I feel that the "options" label is really generic (and only contains one
option). How about naming this whole section "Headers and footers" instead of
"Options" and the label of the checkbox to "Enable" instead of "Headers and
footers"?

[Aayush Kumar, 2011/07/19 18:37:19]

Let me hold these changes off until we decide for sure what the UI will look
like.  In one of the e-mails, there was a thought that margins and headers and
footers be clubbed into one zippy.  In that case, 'options' may be an
appropriate name.  :)
On 2011/07/19 15:38:04, dpapad wrote:

+        <h1 i18n-content="optionsLabel"></h1>
+        <div>
+          <input id="header-footer" type="checkbox" checked/>
+          <label for="header-footer" i18n-content="optionHeaderFooter">
+          </label>
+        </div>
+      </div>
+      <hr>
       <div id="system-dialog-div">
         <button id="system-dialog-link" class="link-button"
             i18n-content="systemDialogOption"></button>