Bug 1350703 - Typo fixes in code-comments within layout/XUL. r=dholbert
authorPaul Bignier <paul.bignier@gmail.com>
Sun, 26 Mar 2017 18:37:10 +0200
changeset 397873 b94b13d756c19e06fcdb833b3736d3aa920fbaa6
parent 397872 d60cdc45458895430a3f1dcef45a3d23987961bf
child 397874 189dbcbf21e2a9af235fd2413f253e2fb3287ef8
push id7391
push usermtabara@mozilla.com
push dateMon, 12 Jun 2017 13:08:53 +0000
treeherdermozilla-beta@2191d7f87e2e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdholbert
bugs1350703
milestone55.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1350703 - Typo fixes in code-comments within layout/XUL. r=dholbert DONTBUILD because comment-only.
layout/xul/nsImageBoxFrame.cpp
--- a/layout/xul/nsImageBoxFrame.cpp
+++ b/layout/xul/nsImageBoxFrame.cpp
@@ -92,20 +92,20 @@ nsImageBoxFrameEvent::Run()
 
   event.mFlags.mBubbles = false;
   EventDispatcher::Dispatch(mContent, pres_context, &event, nullptr, &status);
   return NS_OK;
 }
 
 // Fire off an event that'll asynchronously call the image elements
 // onload handler once handled. This is needed since the image library
-// can't decide if it wants to call it's observer methods
+// can't decide if it wants to call its observer methods
 // synchronously or asynchronously. If an image is loaded from the
 // cache the notifications come back synchronously, but if the image
-// is loaded from the netswork the notifications come back
+// is loaded from the network the notifications come back
 // asynchronously.
 
 void
 FireImageDOMEvent(nsIContent* aContent, EventMessage aMessage)
 {
   NS_ASSERTION(aMessage == eLoad || aMessage == eLoadError,
                "invalid message");