GTK: Add a dialog for printing.

Add an infobar directing users to tell us if they have problems with printing.

Hide printing behind --enable-printing flag on linux/gtk.

BUG=9847
TEST=none
Review URL: http://codereview.chromium.org/200138

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26400 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 32 insertions, 12 deletions

diff --git a/chrome/browser/resources/linux-splash-chrome.html b/chrome/browser/resources/linux-splash-chrome.html
index 8430a43..6ea8589 100644
--- a/chrome/browser/resources/linux-splash-chrome.html
+++ b/chrome/browser/resources/linux-splash-chrome.html
@@ -44,12 +44,12 @@
     <p>Every minute spent triaging and de-duplicating bugs is a minute spent
     not fixing them.  If you have a good bug report (e.g. includes a
     stack trace or a reduced test case), first verify it exists in the <a
-      href="http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/">latest
-      build</a>, then <a
-      href="http://code.google.com/p/chromium/issues/list?can=1&q=os:linux">
-      verify it hasn't been filed already</a>, then <a
-      href="http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux">file
-      your bug using the Linux-specific template</a>.
+    href="http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/">
+    latest build</a>, then <a
+    href="http://code.google.com/p/chromium/issues/list?can=1&q=os:linux">
+    verify it hasn't been filed already</a>, then <a
+    href="http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux">
+    file your bug using the Linux-specific template</a>.
 
     <h3>How to help</h3>
 
@@ -57,6 +57,16 @@
     have <a href="http://dev.chromium.org/">documentation for developers</a> as
     well as mailing lists and an IRC channel.
 
+    <h3>Printing</h3>
+
+    Basic printing support is now available with the --enable-printing flag.
+    There is no support for page preview, adjusting the margins, editing the
+    header/footer, etc. If you have bug reports, please file them, but be sure
+    to
+    <a href="http://code.google.com/p/chromium/issues/list?can=2&q=label:Printing#">
+    search existing issues</a> first, because we know a lot of features are
+    missing.
+
     </div>
 
     <p></p>
diff --git a/chrome/browser/resources/linux-splash.html b/chrome/browser/resources/linux-splash.html
index 06f5a85..26a0361 100644
--- a/chrome/browser/resources/linux-splash.html
+++ b/chrome/browser/resources/linux-splash.html
@@ -42,12 +42,12 @@
     <p>Every minute spent triaging and de-duplicating bugs is a minute spent
     not fixing them.  If you have a good bug report (e.g. includes a
     stack trace or a reduced test case), first verify it exists in the <a
-      href="http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/">latest
-      build</a>, then <a
-      href="http://code.google.com/p/chromium/issues/list?can=1&q=os:linux">
-      verify it hasn't been filed already</a>, then <a
-      href="http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux">file
-      your bug using the Linux-specific template</a>.
+    href="http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/">
+    latest build</a>, then <a
+    href="http://code.google.com/p/chromium/issues/list?can=1&q=os:linux">
+    verify it hasn't been filed already</a>, then <a
+    href="http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux">
+    file your bug using the Linux-specific template</a>.
 
     <h3>How to help</h3>
 
@@ -55,6 +55,16 @@
     have <a href="http://dev.chromium.org/">documentation for developers</a> as
     well as mailing lists and an IRC channel.
 
+    <h3>Printing</h3>
+
+    Basic printing support is now available with the --enable-printing flag.
+    There is no support for page preview, adjusting the margins, editing the
+    header/footer, etc. If you have bug reports, please file them, but be sure
+    to
+    <a href="http://code.google.com/p/chromium/issues/list?can=2&q=label:Printing#">
+    search existing issues</a> first, because we know a lot of features are
+    missing.
+
     </div>
 
     <p></p>