Adding client code for new Windows 10 First Run Experience

chrome/browser/resources/welcome/win10/inline.css

Index: chrome/browser/resources/welcome/win10/inline.css
diff --git a/chrome/browser/resources/welcome/win10/inline.css b/chrome/browser/resources/welcome/win10/inline.css
new file mode 100644
index 0000000000000000000000000000000000000000..e2b56d82e86493f0bfde4f1e6e694b9340690fcb
--- /dev/null
+++ b/chrome/browser/resources/welcome/win10/inline.css
@@ -0,0 +1,240 @@
+/* Copyright 2016 The Chromium Authors. All rights reserved.
+ * Use of this source code is governed by a BSD-style license that can be
+ * found in the LICENSE file. */
+
+* {

[michaelpg, 2016/10/22 03:19:00]

err, can we be more specific? You probably mean "html, body" and possibly "ol".

[Patrick Monette, 2016/10/24 20:49:39]

Done.

+  margin: 0;
+  padding: 0;
+}
+
+body {
+  box-sizing: border-box;
+  color: var(--paper-grey-900);
+  display: flex;
+  flex-direction: column;
+  font-size: 100%;
+  justify-content: center;
+  min-height: 100vh;
+}
+
+a {
+  color: var(--google-blue-500);
+  text-decoration: none;
+}
+
+strong {
+  font-weight: 500;
+}
+
+.content {
+  margin: 0 auto;
+  padding: 4em 1.5em 1.5em 1.5em;
+}
+
+.header-logo {
+  content: -webkit-image-set(url(/logo-large.png) 1x,
+                             url(/logo-large2x.png) 2x);
+}
+
+.heading {
+  font-size: 2.125em;
+  line-height: 1.6em;
+  margin-bottom: 0.5em;
+  margin-top: 1.2em;
+}
+
+.sections {
+  margin-bottom: 3em;
+}
+
+.section.expandable {
+  border-top: 1px solid var(--google-grey-300);
+}
+
+.section.expandable:last-child {
+  border-bottom: 1px solid var(--google-grey-300);
+}
+
+.section.expandable .section-heading {
+  color: var(--google-blue-500);
+  cursor: pointer;
+}
+
+.section-heading {
+  align-items: center;
+  display: flex;
+  padding: 1.5em 0;
+}
+
+.section-heading-text {
+  flex: 1;
+  font-weight: 500;
+}
+
+.section.expandable .section-heading-text {
+  font-weight: normal;
+}
+
+.section.expandable.expanded .section-heading-text {
+  font-weight: 500;
+}
+
+.section-heading-expand {
+  height: 1.25em;
+  opacity: 0.54;
+  transition: transform 150ms cubic-bezier(.4, .2, 0, 1) 50ms;
+  width: 1.25em;
+}
+
+.section.expandable.expanded .section-heading-expand {
+  transform: rotate(180deg);
+  transition-delay: 150ms;
+}
+
+.section-steps {
+  overflow: hidden;
+}
+
+.section-steps li {
+  margin-bottom: 1em;
+  margin-left: 1.25em;

[michaelpg, 2016/10/22 03:19:00]

make RTL friendly

[Patrick Monette, 2016/10/24 20:49:39]

First time doing this. I added a second styling for [dir="rtl"] that overrides
the regular style.

Is that enough?

[michaelpg, 2016/10/24 21:30:08]

That's fine. Technically, the style guide prefers using -webkit-padding-start,
-webkit-padding-end, -webkit-margin-start, etc.:
http://www.chromium.org/developers/web-development-style-guide but it amounts to
the same thing.

[Patrick Monette, 2016/10/24 23:11:33]

Okay I went with -webkit-*-start. I like it better and there are less lines of
code.

+  padding-left: 1em;
+}
+
+.section-steps li:last-child {
+  margin-bottom: 1em;
+}
+
+.section.expandable .section-steps {
+  max-height: 0;
+  opacity: 0;
+  transition: max-height 300ms cubic-bezier(.4, .2, 0, 1) 50ms, opacity 150ms;
+}
+
+.section.expandable.expanded .section-steps {
+  max-height: 28.75em;
+  opacity: 1;
+  transition: max-height 300ms cubic-bezier(.4, .2, 0, 1) 50ms,
+              opacity 150ms 250ms;
+}
+
+.button {
+  -webkit-font-smoothing: antialiased;
+  background: var(--paper-blue-a200);
+  border-radius: 2px;
+  box-shadow: inset 0 0 0 1px rgba(0, 0, 0, .1);
+  color: #fff;
+  display: inline-block;
+  font-size: .75em;
+  font-weight: 500;
+  line-height: 1.75em;
+  min-width: 2em;
+  padding: 0 1em;
+  text-align: center;
+  transition: 300ms cubic-bezier(.4, .2, 0, 1);
+  will-change: box-shadow;
+}
+
+.button:hover {
+  background: var(--paper-blue-a400);
+  box-shadow: inset 0 0 0 1px rgba(0, 0, 0, .1), 0 1px 2px rgba(0, 0, 0, .24)
+}
+
+.logo-small {
+  content: -webkit-image-set(url(/logo-small.png) 1x,
+                             url(/logo-small2x.png) 2x);
+  display: inline;
+  height: 1.25em;
+  vertical-align: top;
+  width: 1.25em;
+}
+
+.screenshot {
+  display: block;
+  height: 440px;
+  margin: 0 auto;
+  max-width: 100%;
+  position: relative;
+  top: -96px;
+  width: 720px;
+}
+
+.screenshot-image {
+  box-shadow:  0 0 0 1px rgba(0, 0, 0, .12), 0 1px 2px rgba(0, 0, 0, .24);
+  height: 48vw;
+  margin: 1em 0;
+  max-height: 300px;
+  max-width: 400px;
+  min-height: 150px;
+  min-width: 200px;
+  position: relative;
+  width: 64vw;
+}
+
+#screenshot-image--default {
+  background: -webkit-image-set(
+    url(https://www.gstatic.com/chrome/login/win10/default-small.webp) 1x,

[michaelpg, 2016/10/22 03:19:00]

o_O why are we loading from the web?

[Patrick Monette, 2016/10/24 20:49:39]

It was a conscious decision made in order to not inflate the binary size.

I don't think there is a policy against that, but if this is a problem, we could
bundle the images. That would add ~78 kb to the binary.

[tmartino, 2016/10/24 21:06:20]

Michael, I'm forwarding you the thread where this decision was made.

[michaelpg, 2016/10/24 21:30:08]

If laforge is ok with it and it went through a security review, SGTM.

+    url(https://www.gstatic.com/chrome/login/win10/default-small@2x.webp) 2x);
+  background-repeat: no-repeat;
+  background-size: cover;
+}
+
+#screenshot-image--taskbar {
+  background: -webkit-image-set(
+    url(https://www.gstatic.com/chrome/login/win10/pin-small.webp) 1x,
+    url(https://www.gstatic.com/chrome/login/win10/pin-small@2x.webp) 2x);
+  background-repeat: no-repeat;
+  background-size: cover;
+}
+
+.screenshot-html-overlay {
+  box-sizing: border-box;
+  font-size: 6px;
+  line-height: 0;
+  position: absolute;
+}
+
+#screenshot-html-overlay--browser {
+  left: 54.8%;
+  top: 53%;
+}
+
+#screenshot-html-overlay--edge {
+  left: 65%;
+  top: 63.5%;
+}
+
+#screenshot-html-overlay--taskbar {
+  left: 31%;
+  top: 73%;
+}
+
+#screenshot-html-overlay--taskbar div {
+  color: #ccc;
+  font-family: Tahoma, Verdana, Segoe, sans-serif;
+  font-weight: 500;
+}
+
+#screenshot-html-overlay--icon {
+  background-image: url(/logo-small.png);
+  background-size: cover;
+  height: 8%;
+  left: 46%;
+  top: 90%;
+  width: 6%;
+}
+
+/* This value is precisely set so that the text over the screenshot starts
+   scaling at the same time the image starts scaling too. */

[michaelpg, 2016/10/22 03:19:00]

nit:

/* This value...
 * scaling at... */

[Patrick Monette, 2016/10/24 20:49:39]

Done.

+@media (min-width: 312px) {
+  .screenshot-html-overlay {
+    font-size: 1.95vw;
+  }
+}
+
+/* Font-size used when the screenshot exactly reaches its max size. */
+@media (min-width: 626px) {
+  .screenshot-html-overlay {
+    font-size: 12.2px;
+  }
+}