Skip to content

Commit d646112

Browse files
committed
[Samples]: Fixed typos.
1 parent 6d029b4 commit d646112

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

samples/contacts-widget.html

+1-1
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ <h1>Contacts Widget</h1>
4949
// &hellip;
5050

5151
// Asynchronously loads users from server and invokes [callback] for each user loaded
52-
Contacts.prototype.loadUsers = function(callback)
52+
Contacts.prototype.loadUsers = function(userCount, callback)
5353
{
5454
// &hellip;
5555
}

samples/widget-theming.html

+2-2
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ <h1>Contacts Widget</h1>
6060

6161
<p>Then, a separate stylesheet in the <code>/src/ui/themes/</code> directory is used to apply colors, backgrounds, and all those wonderful barnacles that typically comprise a theme. Despite strictly enforced naming conventions, the structure is somewhat brittle and, on occasion, one rule clobbers another, subtly breaking the beautiful house of cards, causing users grief&mdash;and throwing Howard into panic mode. Panic mode gets old quickly.</p>
6262

63-
<p>Moving widget layout styles to <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped">scoped stylesheets</a> next to respective widgets goes a long way to make layout less brittle. Further, putting these scoped styles <em>inside</em> each widget's shadow DOM subtree ensures that the these styles are <strong>contained</strong> to the widgets. Sure, it's a bit of a refactoring, but that beats arguing with mom. Howard goes to work. An hour later, the <code>/src/ui/layout/widgets.css</code> stylesheet is drained and all widgets look like this ()<code>/src/ui/widgets/contacts.js</code>, for example):</p>
63+
<p>Moving widget layout styles to <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped">scoped stylesheets</a> next to respective widgets goes a long way to make layout less brittle. Further, putting these scoped styles <em>inside</em> each widget's shadow DOM subtree ensures that the these styles are <strong>contained</strong> to the widgets. Sure, it's a bit of a refactoring, but that beats arguing with mom. Howard goes to work. An hour later, the <code>/src/ui/layout/widgets.css</code> stylesheet is drained and all widgets look like this (<code>/src/ui/widgets/contacts.js</code>, for example):</p>
6464

6565
<pre class="prettyprint"><code>
6666
var ui = ui || {};
@@ -86,7 +86,7 @@ <h1>Contacts Widget</h1>
8686
// &hellip;
8787

8888
// Asynchronously loads users from server and invokes [callback] for each user loaded
89-
Contacts.prototype.loadUsers = function(callback)
89+
Contacts.prototype.loadUsers = function(userCount, callback)
9090
{
9191
// &hellip;
9292
}

0 commit comments

Comments
 (0)