Bug 861761 - Remove <blink> in perf-doc.html. r=dbaron
authorCykesiopka <cykesiopka.bmo@gmail.com>
Mon, 19 Aug 2013 08:48:24 -0400
changeset 156885 16c7519f1973ef0faa5a4d1de089f92fe80a33d3
parent 156884 198caba447af5a34c72d831d808966b34b6742aa
child 156886 ba7f87cc10736793571b708b41ce144b265b30ac
push id407
push userlsblakk@mozilla.com
push dateTue, 03 Dec 2013 03:32:50 +0000
treeherdermozilla-release@babf8c9ebc52 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdbaron
bugs861761
milestone26.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 861761 - Remove <blink> in perf-doc.html. r=dbaron
tools/performance/layout/perf-doc.html
--- a/tools/performance/layout/perf-doc.html
+++ b/tools/performance/layout/perf-doc.html
@@ -88,17 +88,17 @@ files which is dropped in the Tables sub
 
 <li>
 Lasty, stare at the table and the values in it and decide if performance
 is geting better, worse, or staying the same.</li>
 </ul>
 
 <h3>
 The PerfTools</h3>
-<blink>IMPORTANT: </blink>The tools created for monitoring performance
+IMPORTANT: The tools created for monitoring performance
 are very tightly coupled to output from the layout engine. As Viewer (or
 Mozilla) is run it spits-out various timing values to the console. These
 values are captured to files, parsed and assembled into HTML tables showing
 the amount of CPU time dedicated to parsing the document, creating the
 content model, building the frame model, and resolving style during the
 building of the frame model. All of the scripts that make up the perftool
 are locate in the directory <tt>\mozilla\tools\performance\layout.</tt>
 Running them from another location <i>may</i> work, but it is best to run