Changeset 56300 in webkit
- Timestamp:
- Mar 20, 2010 1:12:18 AM (14 years ago)
- Location:
- trunk/WebKitSite
- Files:
-
- 24 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/WebKitSite/ChangeLog
r56299 r56300 1 2010-03-20 Maciej Stachowiak <mjs@apple.com> 2 3 Reviewed by Mark Rowe. 4 5 Fix a bunch of HTML5 validation errors on various pages. 6 https://bugs.webkit.org/show_bug.cgi?id=36409 7 8 * building/build.html: 9 * building/checkout.html: 10 * building/debug.html: 11 * building/run.html: 12 * building/tools.html: 13 * coding/coding-style.html: 14 * coding/contributing.html: 15 * coding/major-objects.html: 16 * css/main.css: 17 (.asciiart): 18 * demos/index.html: 19 * header.inc: 20 * projects/compat/index.html: 21 * projects/css/index.html: 22 * projects/documentation/index.html: 23 * projects/goals.html: 24 * projects/index.html: 25 * projects/mathml/index.html: 26 * quality/bugpriorities.html: 27 * quality/bugwriting.html: 28 * quality/crashlogs.html: 29 * quality/lifecycle.html: 30 * quality/testing.html: 31 * quality/testwriting.html: 32 1 33 2010-03-19 Maciej Stachowiak <mjs@apple.com> 2 34 -
trunk/WebKitSite/building/build.html
r51932 r56300 18 18 19 19 <ol> 20 <li><p>Run the < tt>build-webkit</tt> <a href="/coding/scripts.html">script</a>20 <li><p>Run the <code>build-webkit</code> <a href="/coding/scripts.html">script</a> 21 21 to build WebKit.</p> 22 <p>Use the < tt>--debug</tt> option for a debug build, which includes22 <p>Use the <code>--debug</code> option for a debug build, which includes 23 23 debugging symbols and assertions:</p> 24 24 <p class="code">build-webkit --debug</p> … … 26 26 </ol> 27 27 28 <p>By default, < tt>build-webkit</tt> places build products in <tt>WebKit/WebKitBuild</tt>. You can specify a different build29 location on Mac in your Xcode preferences. On Windows, the < tt>WEBKITOUTPUTDIR</tt> environment variable can be used to30 set a different build products location. If you have set up a custom build location, then < tt>build-webkit</tt> will28 <p>By default, <code>build-webkit</code> places build products in <code>WebKit/WebKitBuild</code>. You can specify a different build 29 location on Mac in your Xcode preferences. On Windows, the <code>WEBKITOUTPUTDIR</code> environment variable can be used to 30 set a different build products location. If you have set up a custom build location, then <code>build-webkit</code> will 31 31 place the build products there.</p> 32 32 … … 44 44 <h2>Setting a Default Configuration</h2> 45 45 <ol> 46 <li><p>To set a default build configuration for < tt>build-webkit</tt> and46 <li><p>To set a default build configuration for <code>build-webkit</code> and 47 47 other <a href="/coding/scripts.html">scripts</a>, use the 48 < tt>set-webkit-configuration</tt> script:</p>48 <code>set-webkit-configuration</code> script:</p> 49 49 <p class="code">set-webkit-configuration --debug</p> 50 50 <p class="code">set-webkit-configuration --release</p> -
trunk/WebKitSite/building/checkout.html
r51733 r56300 43 43 <ol> 44 44 <li><p>Install the WebKit Support Libraries</p> 45 <p>Download the <a href="http://developer.apple.com/opensource/internet/webkit_sptlib_agree.html">WebKit Support Libraries</a> to the root of your source tree (< tt>C:\cygwin\home\<username>\WebKit</tt>).</p>46 <p>If the file is incorrectly named, rename it to < tt>WebKitSupportLibrary.zip</tt>. Do not extract its contents.</p>45 <p>Download the <a href="http://developer.apple.com/opensource/internet/webkit_sptlib_agree.html">WebKit Support Libraries</a> to the root of your source tree (<code>C:\cygwin\home\<username>\WebKit</code>).</p> 46 <p>If the file is incorrectly named, rename it to <code>WebKitSupportLibrary.zip</code>. Do not extract its contents.</p> 47 47 </ol> 48 48 </div> 49 49 50 50 <ol> 51 <li><p>Run the < tt>update-webkit</tt> <a href="/coding/scripts.html">script</a>51 <li><p>Run the <code>update-webkit</code> <a href="/coding/scripts.html">script</a> 52 52 to update your source tree.</p> 53 53 <p>If you downloaded the tarball, this will bring it up to date. Windows users … … 60 60 61 61 <h2>Keeping up to Date</h2> 62 <p>At any time, you can rerun the < tt>update-webkit</tt> script to update62 <p>At any time, you can rerun the <code>update-webkit</code> script to update 63 63 your source tree.</p> 64 64 -
trunk/WebKitSite/building/debug.html
r55170 r56300 11 11 </li> 12 12 <li><p>Set the project's build products location</p> 13 <p>To find the WebKit you built, Xcode needs to know the build products location that < tt>build-webkit</tt> used. You can set the build products location from the project's Info window.</p>13 <p>To find the WebKit you built, Xcode needs to know the build products location that <code>build-webkit</code> used. You can set the build products location from the project's Info window.</p> 14 14 <img src="info-tab.png"> 15 15 </li> … … 40 40 <p>To launch Safari in the Visual Studio or Visual C++ Express debugger, simply run:</p> 41 41 <p class="code">debug-safari</p> 42 <p>This command will launch the Visual Studio debugging environment, and attach to Safari connected to the debug build of WebKit.dll. There are a few things to keep in mind: 42 <p>This command will launch the Visual Studio debugging environment, and attach to Safari connected to the debug build of WebKit.dll. There are a few things to keep in mind:</p> 43 43 <ul> 44 44 <li>The instance of Safari is not running yet. You must press the F5 key (or the 'Run' button) to see anything happen.</li> … … 48 48 <p>You should consider including the command-line switch '<span class="code">/console</span>'. This causes Safari to run with an open DOS shell in which output messages, created with the <span class="code">LOG</span> macro, appear.</p> 49 49 <img src="console_vs2005.jpg"></li> 50 </ul> </p>51 <p>Alternatively, you can build, run, and debug WebKit from inside Visual Studio by opening the solution file: 50 </ul> 51 <p>Alternatively, you can build, run, and debug WebKit from inside Visual Studio by opening the solution file:</p> 52 52 <ol> 53 53 <li>Launch Visual Studio.</li> … … 57 57 <li>To build, select the 'Build' menu, then 'Build Solution'. To run, select the 'Debug' menu, then 'Start Debugging'.</li> 58 58 </ol> 59 </p>60 59 <p>It is also recommended that you follow <a href="http://developer.apple.com/internet/safari/windows_symbols_agree.html">the instructions to configure Visual Studio to use Apple's Safari for Windows symbol server</a>. This will give Visual Studio the information it needs to provide reliable backtraces when pausing in the debugger or when a crash occurs.</p> 61 60 </div> -
trunk/WebKitSite/building/run.html
r51733 r56300 6 6 <h2>Running WebKit</h2> 7 7 <ol> 8 <li><p>Execute the < tt>run-safari</tt> <a href="/coding/scripts.html">script</a>8 <li><p>Execute the <code>run-safari</code> <a href="/coding/scripts.html">script</a> 9 9 to run Safari with the WebKit version you <a href="build.html">built</a>.</p> 10 <p>Use the < tt>--debug</tt> option for a debug build:</p>10 <p>Use the <code>--debug</code> option for a debug build:</p> 11 11 <p class="code">run-safari --debug</p> 12 12 </li> … … 15 15 <div class="mac-instructions"> 16 16 <h4>Mac OS X</h4> 17 <p>The < tt>run-safari</tt> script sets the <tt>DYLD_FRAMEWORK_PATH</tt> environment variable to point to your build products,18 and then launches /Applications/Safari.app. < tt>DYLD_FRAMEWORK_PATH</tt> tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks.</p>17 <p>The <code>run-safari</code> script sets the <code>DYLD_FRAMEWORK_PATH</code> environment variable to point to your build products, 18 and then launches /Applications/Safari.app. <code>DYLD_FRAMEWORK_PATH</code> tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks.</p> 19 19 </div> 20 20 21 21 <div class="windows-instructions"> 22 22 <h4>Windows</h4> 23 <p>The < tt>run-safari</tt> script launches the Safari executable with the <tt>/frameworkPath</tt> command line switch set to point to your build products. The <tt>/debug</tt> command line switch will be set if you pass --debug to <tt>run-safari.</tt></p>23 <p>The <code>run-safari</code> script launches the Safari executable with the <code>/frameworkPath</code> command line switch set to point to your build products. The <code>/debug</code> command line switch will be set if you pass --debug to <code>run-safari.</code></p> 24 24 </div> 25 25 -
trunk/WebKitSite/building/tools.html
r51723 r56300 18 18 <ol> 19 19 <li><p>If you own Visual Studio 2005 (newer versions of Visual Studio are currently unsupported):</p> 20 <p>Install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?familyid=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC& displaylang=en">Microsoft Visual Studio 2005 Team Suite Service Pack 1</a>.</p>21 <p>If you are building from Vista, install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee-4acc0aace5b6& displaylang=en">Service Pack 1 Update for Windows Vista</a>.</p>22 <p>Install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=7c8729dc-06a2-4538-a90d-ff9464dc0197& displaylang=en">Visual Studio 2005 Service Pack 1 ATL Security Update</a>.</p>23 <p>Install the following hotfixes to improve Visual Studio's performance and responsiveness: 20 <p>Install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?familyid=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en">Microsoft Visual Studio 2005 Team Suite Service Pack 1</a>.</p> 21 <p>If you are building from Vista, install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee-4acc0aace5b6&displaylang=en">Service Pack 1 Update for Windows Vista</a>.</p> 22 <p>Install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=7c8729dc-06a2-4538-a90d-ff9464dc0197&displaylang=en">Visual Studio 2005 Service Pack 1 ATL Security Update</a>.</p> 23 <p>Install the following hotfixes to improve Visual Studio's performance and responsiveness:</p> 24 24 <ol> 25 25 <li><a target="installtools" href="http://code.msdn.microsoft.com/KB918559">KB918559</a></li> … … 28 28 <li><a target="installtools" href="http://code.msdn.microsoft.com/KB947315">KB947315</a></li> 29 29 </ol> 30 </p>31 30 <p>Use the default options for these installations.</p> 32 31 <li><p>If not, you can use Visual C++ Express 2005 (newer versions of Visual C++ Express Edition are currently unsupported):</p> 33 32 <p>Install <a target="installtools" href="http://go.microsoft.com/fwlink/?LinkId=51410">Visual C++ 2005 Express</a>.</p> 34 33 <p>Install <a target="installtools" href="http://download.microsoft.com/download/7/7/3/7737290f-98e8-45bf-9075-85cc6ae34bf1/VS80sp1-KB926748-X86-INTL.exe">Microsoft Visual C++ Express 2005 Service Pack 1</a>.</p> 35 <p>If you are building from Vista, install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee-4acc0aace5b6& displaylang=en">Service Pack 1 Update for Windows Vista</a>.</p>36 <p>Install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=7c8729dc-06a2-4538-a90d-ff9464dc0197& displaylang=en">Visual Studio 2005 Service Pack 1 ATL Security Update</a>.</p>37 <p>Install the <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb& displaylang=en">Windows Server 2003 R2 Platform SDK</a>, then follow steps 2 and 3 of “<a target="installtools" href="http://msdn.microsoft.com/en-us/library/ms235626(VS.80).aspx">How to: Use Visual C++ Express Edition with the Microsoft Platform SDK</a>.”</p>34 <p>If you are building from Vista, install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee-4acc0aace5b6&displaylang=en">Service Pack 1 Update for Windows Vista</a>.</p> 35 <p>Install <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=7c8729dc-06a2-4538-a90d-ff9464dc0197&displaylang=en">Visual Studio 2005 Service Pack 1 ATL Security Update</a>.</p> 36 <p>Install the <a target="installtools" href="http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb&displaylang=en">Windows Server 2003 R2 Platform SDK</a>, then follow steps 2 and 3 of “<a target="installtools" href="http://msdn.microsoft.com/en-us/library/ms235626(VS.80).aspx">How to: Use Visual C++ Express Edition with the Microsoft Platform SDK</a>.”</p> 38 37 <p>Use the default options for all installations.</p> 39 38 <p>In addition to the paths specified in step 3 of the Platform SDK installation instructions, you must also add the following include path. Update the Visual C++ directories in the Projects and Solutions section in the Options dialog box:</p> … … 47 46 <p>Download <a 48 47 href="http://svn.webkit.org/repository/webkit/trunk/WebKitTools/CygwinDownloader/cygwin-downloader.zip">cygwin-downloader.zip</a>.</p> 49 <p>Right-click < tt>cygwin-downloader.zip</tt> and choose <b>Extract All...</b>.48 <p>Right-click <code>cygwin-downloader.zip</code> and choose <b>Extract All...</b>. 50 49 Keep all the default options and click <b>Next</b> until the file is extracted and the cygwin-downloader folder opens.</p> 51 <p>Double-click < tt>cygwin-downloader.exe</tt>. This will download all the Cygwin packages you need.</p>50 <p>Double-click <code>cygwin-downloader.exe</code>. This will download all the Cygwin packages you need.</p> 52 51 <p>When all the packages have finished downloading, the Cygwin installer will launch. Choose <b>Install from Local Directory</b>, then click <b>Next</b> until the install is complete. If you are running Vista, the installer won't be able to launch automatically, so you will have to manually launch Cygwin's Setup.exe.</p> 53 52 <P>Vista may warn you that Cygwin did not install correctly. Ignore this warning and tell Vista that the install was successful.</p> -
trunk/WebKitSite/coding/coding-style.html
r54258 r56300 186 186 <h4 class="right">Right:</h4> 187 187 <pre class="code"> 188 for (int i = 0; i <10; i++)188 for (int i = 0; i < 10; i++) 189 189 doSomething(); 190 190 … … 194 194 <h4 class="wrong">Wrong:</h4> 195 195 <pre class="code"> 196 for (int i = 0 ; i <10 ; i++)196 for (int i = 0 ; i < 10 ; i++) 197 197 doSomething(); 198 198 -
trunk/WebKitSite/coding/contributing.html
r53782 r56300 30 30 <li><a href="#writecode">Develop</a> your changes.</li> 31 31 <li>Make sure your changes meet the <a href="/coding/coding-style.html">code 32 style guidelines</a>. The < tt>check-webkit-style</tt> script may be of32 style guidelines</a>. The <code>check-webkit-style</code> script may be of 33 33 help.</li> 34 <li>Run the layout tests using the < tt>run-webkit-tests</tt> script and make sure they all pass.34 <li>Run the layout tests using the <code>run-webkit-tests</code> script and make sure they all pass. 35 35 See the <a href="/quality/testwriting.html">testing page</a> for more information, as well as what you need to do if you've modified JavaScriptCore.</li> 36 36 <li>Add any <a href="#newfiles">new files</a> to your working directory.</li> 37 <li>Prepare a change log entry. You may have to add entries to multiple ChangeLogs. The < tt>prepare-ChangeLog</tt> script will create stub entries for you. See the <a href="#changelogs">paragraph about ChangeLogs</a> below.</li>38 <li>Create the patch using the < tt>svn-create-patch</tt> script.</li>37 <li>Prepare a change log entry. You may have to add entries to multiple ChangeLogs. The <code>prepare-ChangeLog</code> script will create stub entries for you. See the <a href="#changelogs">paragraph about ChangeLogs</a> below.</li> 38 <li>Create the patch using the <code>svn-create-patch</code> script.</li> 39 39 <li><a href="#submit">Submit</a> your patch for review to 40 40 <a href="https://bugs.webkit.org/">bugs.webkit.org</a>.</li> … … 73 73 and a company: 74 74 75 <p>< tt>Copyright (C) 2010 John Smith (jsmith@example.com)</tt></p>76 <p>< tt>Copyright (C) 2010 Company Inc. All rights reserved.</tt></p>75 <p><code>Copyright (C) 2010 John Smith (jsmith@example.com)</code></p> 76 <p><code>Copyright (C) 2010 Company Inc. All rights reserved.</code></p> 77 77 78 78 <p>In addition, make sure that any new source code and script files … … 93 93 94 94 <h3>Regression tests</h3> 95 <p>Once you have made your changes, you need to run the regression tests, which is done via the < tt>run-webkit-tests</tt> script.95 <p>Once you have made your changes, you need to run the regression tests, which is done via the <code>run-webkit-tests</code> script. 96 96 All tests must pass. Patches will not be landed in the tree if they break existing layout tests.</p> 97 97 … … 107 107 <h3 id="newfiles">Add new files to your working directory</h3> 108 108 <p>If your changes include adding new files (like new layout tests), 109 use the < tt>svn add</tt> command to mark these files for addition to the109 use the <code>svn add</code> command to mark these files for addition to the 110 110 repository. If you do not do this, the new files will be missing from 111 111 the patch file you generate below.</p> 112 112 113 <p>You can learn more about Subversion commands like < tt>svn add</tt>113 <p>You can learn more about Subversion commands like <code>svn add</code> 114 114 from the online book <a class="book" href="http://svnbook.red-bean.com/"> 115 Version Control with Subversion</a> and by using the < tt>svn help</tt>115 Version Control with Subversion</a> and by using the <code>svn help</code> 116 116 command.</p> 117 117 118 118 <h3 id="changelogs">ChangeLog files</h3> 119 <p>ChangeLogs are simple text files which provide historical documentation for all changes to the WebKit project. All patches require an entry to the ChangeLog. The < tt>prepare-ChangeLog</tt> script will create a basic entry containing a list of all files that have been changed. The first line contains the date, your full name, and your email address. Use this to write up a brief summary of the changes you've made. Don't worry about the "Reviewed by NOBODY (OOPS!)" line, the person landing your patch will fill this in.</p>119 <p>ChangeLogs are simple text files which provide historical documentation for all changes to the WebKit project. All patches require an entry to the ChangeLog. The <code>prepare-ChangeLog</code> script will create a basic entry containing a list of all files that have been changed. The first line contains the date, your full name, and your email address. Use this to write up a brief summary of the changes you've made. Don't worry about the "Reviewed by NOBODY (OOPS!)" line, the person landing your patch will fill this in.</p> 120 120 121 <p>There is one ChangeLog per top-level directory, if you changed code and tests you will need to edit at least two ChangeLogs. The < tt>prepare-ChangeLog</tt> script will create a stub entries for you. You should edit these stubs to describe your change, including the full url to the bug (<a href="http://trac.webkit.org/changeset/43259">example entry</a>, note that you can use <tt>--bug</tt> flag). (You should set EMAIL_ADDRESS and CHANGE_LOG_NAME in your environment if you will be running this script frequently.)</p>121 <p>There is one ChangeLog per top-level directory, if you changed code and tests you will need to edit at least two ChangeLogs. The <code>prepare-ChangeLog</code> script will create a stub entries for you. You should edit these stubs to describe your change, including the full url to the bug (<a href="http://trac.webkit.org/changeset/43259">example entry</a>, note that you can use <code>--bug</code> flag). (You should set EMAIL_ADDRESS and CHANGE_LOG_NAME in your environment if you will be running this script frequently.)</p> 122 122 123 123 <p>The line WARNING: NO TEST CASES ADDED OR CHANGED appears if prepare-ChangeLog did not detect the addition of test cases. If your patch does not require test cases (or test cases are not possible), you should include a line stating such. Otherwise all changes require test cases which should be mentioned in the ChangeLog.</p> 124 124 125 125 <h3>Create the patch</h3> 126 <p>WebKit uses < tt>svn-create-patch</tt> to create patches. The127 < tt>svn-create-patch</tt> script is a small wrapper around Subversion's128 < tt>diff</tt> command that better handles moved, added, and deleted files.126 <p>WebKit uses <code>svn-create-patch</code> to create patches. The 127 <code>svn-create-patch</code> script is a small wrapper around Subversion's 128 <code>diff</code> command that better handles moved, added, and deleted files. 129 129 This command is best run from the top level of your checkout 130 130 to make sure no changes are left out of your patch. It is not necessary to 131 131 break a patch into multiple files.</p> 132 132 133 <p>The < tt>svn-create-patch</tt> script does not create a file automatically.133 <p>The <code>svn-create-patch</code> script does not create a file automatically. 134 134 You need to redirect the output yourself using something like--</p> 135 135 <p class="code">svn-create-patch > MyExcellentPatch.txt</p> … … 157 157 alt="Bugzilla patch-submission options"></p> 158 158 159 <p>The patch checkbox and the < tt>review:?</tt> flag signal to159 <p>The patch checkbox and the <code>review:?</code> flag signal to 160 160 WebKit reviewers that your patch is ready for review. 161 161 Setting the review flag also sends an automatic e-mail to the … … 168 168 it into the source control repository. 169 169 A reviewer will typically either approve your patch 170 (by responding with an < tt>r=me</tt> in the bug report and marking the patch <tt>review:+</tt>) or request revisions171 to your patch (and mark the patch < tt>review:-</tt>). In rare cases a patch may be permanently rejected, meaning that the reviewer170 (by responding with an <code>r=me</code> in the bug report and marking the patch <code>review:+</code>) or request revisions 171 to your patch (and mark the patch <code>review:-</code>). In rare cases a patch may be permanently rejected, meaning that the reviewer 172 172 believes the feature should never be committed to the tree. The review process can consist of multiple iterations between you and 173 173 the reviewer as you submit revised patches.</p> … … 182 182 183 183 <h4 id="commitqueue">Optional: Use of the WebKit Commit Bot</h4> 184 <p>WebKit provides an automated system (commit-queue) for landing patches for any who would like to use it. To use the commit-queue, set the < tt>commit-queue:?</tt> flag on your patch. A committer will set <tt>commit-queue:+</tt> and an automated process will download, build, run the layout tests, and submit your patch on your behalf. If the <a href="http://build.webkit.org/">WebKit buildbots</a> are passing, your patch should be landed within 15 minutes after <tt>commit-queue:+</tt> is set. See the <a href="https://trac.webkit.org/wiki/CommitQueue">commit-queue documentation</a> for more information.</p>184 <p>WebKit provides an automated system (commit-queue) for landing patches for any who would like to use it. To use the commit-queue, set the <code>commit-queue:?</code> flag on your patch. A committer will set <code>commit-queue:+</code> and an automated process will download, build, run the layout tests, and submit your patch on your behalf. If the <a href="http://build.webkit.org/">WebKit buildbots</a> are passing, your patch should be landed within 15 minutes after <code>commit-queue:+</code> is set. See the <a href="https://trac.webkit.org/wiki/CommitQueue">commit-queue documentation</a> for more information.</p> 185 185 186 186 <h2>Obtaining Commit and Review Privileges</h2> -
trunk/WebKitSite/coding/major-objects.html
r47584 r56300 3 3 include("../header.inc"); 4 4 ?> 5 6 <style type="text/css">7 .asciiart {8 background-color: #eee;9 padding: 1em;10 margin-left: 2em;11 margin-right: 2em;12 overflow-x: auto;13 }14 </style>15 5 16 6 <h1>Major Objects in WebCore</h1> … … 43 33 / | \/ Replaced after navigation \/ | 44 34 / | | 45 / <------|<-- Ptrs to Frame are null after navigation[1] |35 /<------|<-- Ptrs to Frame are null after navigation[1] | 46 36 | | | 47 37 | +-----+-----+ +-------------+ | 48 | | DOMWindow | <--impl--+ JSDOMWindow |<------window----+38 | | DOMWindow |<--impl--+ JSDOMWindow |<------window----+ 49 39 | +-----+-----+ +-------------+ 50 40 | | 51 | | <-- Can be null for Documents created by XMLHttpRequest41 | |<-- Can be null for Documents created by XMLHttpRequest 52 42 | | 53 43 | +-----+-----+ +-------------+ 54 +-+ Document | <--impl--+ JSDocument |44 +-+ Document |<--impl--+ JSDocument | 55 45 +-----+-----+ +-------------+ 56 46 | 57 | <-- Can be null for DocumentType objects47 |<-- Can be null for DocumentType objects 58 48 | 59 49 +---+---+ +--------+ 60 | Node | <---impl---| JSNode |50 | Node |<---impl---| JSNode | 61 51 +-------+ +--------+ 62 52 </pre> -
trunk/WebKitSite/css/main.css
r53782 r56300 206 206 margin: 1em 0; 207 207 } 208 209 .asciiart { 210 background-color: #eee; 211 padding: 1em; 212 margin-left: 2em; 213 margin-right: 2em; 214 overflow-x: auto; 215 } -
trunk/WebKitSite/demos/index.html
r45221 r56300 18 18 <a href="editingToolbar"><h2>Editing Toolbar</h2></a> 19 19 <span class="datestamp">Added November 4th, 2007</span> 20 <p>The editing toolbar shows off a rich HTML editing toolbar in WebKit. It uses JavaScript and CSS to fade in and out and to implement the buttons that apply text formating and alignment. Click in the text area to see the toolbar appear. 20 <p>The editing toolbar shows off a rich HTML editing toolbar in WebKit. It uses JavaScript and CSS to fade in and out and to implement the buttons that apply text formating and alignment. Click in the text area to see the toolbar appear.</p> 21 21 22 22 <a href="sticky-notes"><h2>Sticky Notes</h2></a> -
trunk/WebKitSite/header.inc
r56299 r56300 2 2 <html> 3 3 <head> 4 <meta http-equiv="Content-Type" content="text/html;charset=utf-8">4 <meta charset="utf-8"> 5 5 <meta name="robots" content="noodp"> 6 6 … … 20 20 <![endif]--> 21 21 22 <script type="text/javascript">22 <script> 23 23 pic1 = new Image(8,9); 24 24 pic1.src="/images/green-bullet.png"; -
trunk/WebKitSite/projects/compat/index.html
r30968 r56300 39 39 can track the issue and screen the bug.</dd> 40 40 <dt>Reduce Bugs</dt> 41 <dd>Scan the bugs in the < tt>New Bugs</tt> component and help attach reductions and minimal failing test cases. Only when bugs are41 <dd>Scan the bugs in the <code>New Bugs</code> component and help attach reductions and minimal failing test cases. Only when bugs are 42 42 screened properly will a developer be able to determine the root cause of the problem and move it into the appropriate component. 43 43 <i>This is one of the most important ways you can help improve WebKit.</i> -
trunk/WebKitSite/projects/css/index.html
r39756 r56300 24 24 25 25 <dt>Finish CSS2.1 Support</dt> 26 <dd>Most of CSS2.1 has been implemented in WebKit, but a few holes remain. The new white-space values < tt>pre-wrap</tt> and <tt>pre-line</tt> are not yet26 <dd>Most of CSS2.1 has been implemented in WebKit, but a few holes remain. The new white-space values <code>pre-wrap</code> and <code>pre-line</code> are not yet 27 27 supported. Some of these features have been implemented in the current KHTML tree, and a merge may be possible for 28 28 some of these features. -
trunk/WebKitSite/projects/documentation/index.html
r38753 r56300 27 27 28 28 <dt>Existing Documentation</dt> 29 <dd><a href="http://developer.apple.com/documentation/Cocoa/Conceptual/DisplayWebContent/DisplayWebContent.html" />Introduction to WebKit Objective-C Programming Guide</a></dd>29 <dd><a href="http://developer.apple.com/documentation/Cocoa/Conceptual/DisplayWebContent/DisplayWebContent.html">Introduction to WebKit Objective-C Programming Guide</a></dd> 30 30 <dd>[TODO: Add links to other existing Apple docs]</dd> 31 31 -
trunk/WebKitSite/projects/goals.html
r24639 r56300 42 42 <dt>Hackability</dt> 43 43 <dd>To make rapid progress possible, we try to keep the code relatively easy to understand, even though web technologies are often complex. We try to use straightforward algorithms and data structures when possible, we try to write clear, maintainable code, and we continue to improve names and code structure to aid understanding. When tricky "rocket science" code is truly needed to solve some problem, we try to keep it bottled up behind clean interfaces. In addition, we make heavy use of automated regression tests as a safety net, to allow aggressive changes with less risk of regressions.</dd> 44 44 </dl> 45 45 46 46 <h3>Non-Goals</h3> -
trunk/WebKitSite/projects/index.html
r16495 r56300 50 50 51 51 <dt><a href="editing/index.html">HTML Editing</a> 52 <dd>The HTML editing project provides rich text editing capabilities both as WebKit API for applications and through support of < tt>contentEditable</tt>53 and < tt>designMode</tt> for use in Web pages.52 <dd>The HTML editing project provides rich text editing capabilities both as WebKit API for applications and through support of <code>contentEditable</code> 53 and <code>designMode</code> for use in Web pages. 54 54 55 55 <dt><a href="forms/index.html">HTML Forms</a> -
trunk/WebKitSite/projects/mathml/index.html
r48843 r56300 18 18 19 19 <h3>Get Involved!</h3> 20 <p><a href="../../contact.html">Come find us</a> on < tt>#webkit</tt> to get involved.</p>20 <p><a href="../../contact.html">Come find us</a> on <code>#webkit</code> to get involved.</p> 21 21 22 22 <?php -
trunk/WebKitSite/quality/bugpriorities.html
r39756 r56300 8 8 The relevant bugs are all of those whose product is "WebKit".</p> 9 9 10 <a name="standardrules"></a><h3>Standard priority rules</h3>10 <a id="standardrules"></a><h3>Standard priority rules</h3> 11 11 <p>Each bug is assigned the first appropriate priority listed below 12 12 from top to bottom.</p> … … 47 47 </ul> 48 48 49 <a name="commonadjustments"></a><h3>Common adjustments to priority</h3>49 <a id="commonadjustments"></a><h3>Common adjustments to priority</h3> 50 50 <ul> 51 51 <li>If there is a workaround, the priority may be moved down.</li> -
trunk/WebKitSite/quality/bugwriting.html
r48226 r56300 15 15 </p> 16 16 <p> 17 Versions of WebKit that are not part of a Safari release have a < tt>+</tt> after the version number, and their version number18 is generally higher then the latest released version of WebKit. So, for example, < tt>528+</tt> is an unofficial build of WebKit19 that is newer than the < tt>525.x</tt> version that shipped as part of Safari 3.1.2.17 Versions of WebKit that are not part of a Safari release have a <code>+</code> after the version number, and their version number 18 is generally higher then the latest released version of WebKit. So, for example, <code>528+</code> is an unofficial build of WebKit 19 that is newer than the <code>525.x</code> version that shipped as part of Safari 3.1.2. 20 20 </p> 21 21 <div style="display: none; text-align: center; font-weight: bold;" id="webkit_version"></div> … … 36 36 <li><b>Component</b> 37 37 <p>If you know the precise cause of a bug (i.e., you've reduced it to a failing test case and know the reason), then you can 38 assign a bug to a specific component such as < tt>CSS</tt> or <tt>HTML Editing</tt>.39 <p>If, however, there is any doubt in your mind as to the cause of the bug, then file it under < tt>New Bugs</tt>. This component38 assign a bug to a specific component such as <code>CSS</code> or <code>HTML Editing</code>. 39 <p>If, however, there is any doubt in your mind as to the cause of the bug, then file it under <code>New Bugs</code>. This component 40 40 is the place for any bugs whose cause has not yet been determined. Once someone has reduced the bug and knows the cause, then it 41 will be moved from the < tt>New Bugs</tt> component to the appropriate place.</p>41 will be moved from the <code>New Bugs</code> component to the appropriate place.</p> 42 42 </li> 43 43 … … 45 45 <b>Platform and OS</b> 46 46 <p>Please select the platform and the OS version that your bug occurred on. If you're running on Mac OS X this would often be platform 47 < tt>Macintosh</tt> and OS <tt>Mac OS X 10.5</tt> (Leopard). If you're running on Windows or Linux, please select <tt>PC</tt> for platform47 <code>Macintosh</code> and OS <code>Mac OS X 10.5</code> (Leopard). If you're running on Windows or Linux, please select <code>PC</code> for platform 48 48 and the appropriate entry from the OS field. If your exact system is not listed, please select the closest entry and provide further 49 49 details in the description of the bug report. … … 59 59 <li> 60 60 <b>Severity</b> 61 <p>In most cases you should leave this at < tt>normal</tt>, but if you are confident that your bug is <tt>trivial</tt> or an62 < tt>enhancement</tt>, it's helpful to specify that value. A QA person or developer will set this to some other value if61 <p>In most cases you should leave this at <code>normal</code>, but if you are confident that your bug is <code>trivial</code> or an 62 <code>enhancement</code>, it's helpful to specify that value. A QA person or developer will set this to some other value if 63 63 appropriate.</p> 64 64 </li> … … 80 80 <li>If you have tested and verified that this is a regression from a previous version of WebKit, prepend "REGRESSION: " to the summary 81 81 <li>If you know the range of revisions in which the regression occurred, add this to the summary after REGRESSION (i.e., "REGRESSION(r31201-r31211):") 82 </ul> 83 </li> <br>82 </ul><br> 83 </li> 84 84 85 85 <li><b>Description</b> … … 98 98 <li>Be as specific as possible. For instance, if you're describing a problem that occurs while scrolling, note in the bug whether you're scrolling with arrow 99 99 keys, arrow buttons, scroll thumb, clicking above or below the thumb, scroll-wheel mouse, etc.</li> 100 </ul>< /li><br>100 </ul><br></li> 101 101 102 102 <li><b>Keywords</b> -
trunk/WebKitSite/quality/crashlogs.html
r31078 r56300 21 21 </li> 22 22 <li> 23 <p>If the crash report dialog does not appear or the crash is hard to reproduce, crash logs can be retrieved from the < tt>~/Library/Logs/CrashReporter</tt> folder.</p>23 <p>If the crash report dialog does not appear or the crash is hard to reproduce, crash logs can be retrieved from the <code>~/Library/Logs/CrashReporter</code>> folder.</p> 24 24 <p>On Leopard (Mac OS X 10.5), crash logs are stored as individually dated and time stamped files. Despite having a “.crash” 25 25 extension, they are plain text files and can be attached directly to a bug report.</p> 26 <p>On Tiger (Mac OS X 10.4), all crashes are logged to < tt>Safari.crash.log</tt>. This is a plain text file and can26 <p>On Tiger (Mac OS X 10.4), all crashes are logged to <code>Safari.crash.log</code>>. This is a plain text file and can 27 27 be viewed in the default Console.app or your favorite text editor. <strong>All</strong> of Safari's crashes are logged 28 28 to this file so please only attach the last crash in it. Crashes are separated by a series of asterisks … … 38 38 <ol> 39 39 <li> 40 <p>In the Start menu's Run box or from a DOS or Cygwin prompt, enter the command < tt>drwtsn32 -i</tt>.</p>40 <p>In the Start menu's Run box or from a DOS or Cygwin prompt, enter the command <code>drwtsn32 -i</code>>.</p> 41 41 <img src="win_installwatson.jpg" alt="Dr Watson install command"> 42 42 </li> … … 46 46 </li> 47 47 <li> 48 <p>Crash information will now be logged to the < tt>user.dmp</tt> file in49 < tt>C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\</tt>.</p>48 <p>Crash information will now be logged to the <code>user.dmp</code>> file in 49 <code>C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\</code>>.</p> 50 50 51 <p>Dr. Watson will create a < tt>user.dmp</tt> file that records what WebKit was doing when it crashed.51 <p>Dr. Watson will create a <code>user.dmp</code>> file that records what WebKit was doing when it crashed. 52 52 Be careful as it is overwritten with every crash.</p> 53 53 54 <p>When reporting a WebKit bug, please upload the < tt>user.dmp</tt> file if possible.</p>54 <p>When reporting a WebKit bug, please upload the <code>user.dmp</code>> file if possible.</p> 55 55 </li> 56 56 <li> 57 <p>Running < tt>drwtsn32</tt> without any options or switches will bring up a window that allows you to change various57 <p>Running <code>drwtsn32</code>> without any options or switches will bring up a window that allows you to change various 58 58 setting such as moving the log folder to a more easily accessible location or throwing a visual alert letting 59 59 you know it caught the crash.</p> … … 66 66 <ol> 67 67 <li> 68 <p>Save the following text to a file named < tt>wer.reg</tt>:</p><tt style="white-space:pre">Windows Registry Editor Version 5.0068 <p>Save the following text to a file named <code>wer.reg</code>>:</p><tt style="white-space:pre">Windows Registry Editor Version 5.00 69 69 70 70 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting] 71 71 "ForceQueue"=dword:00000001 72 </ tt>72 </code>> 73 73 </li> 74 74 <li><p>Double-click the file from Windows Explorer and respond affirmatively to any prompts.</p></li> … … 76 76 </ol> 77 77 <p> 78 The next time Safari (or any other application) crashes, the crash information will be written into a folder located inside < tt>%LOCALAPPDATA%\Microsoft\Windows\WER\ReportQueue</tt>.78 The next time Safari (or any other application) crashes, the crash information will be written into a folder located inside <code>%LOCALAPPDATA%\Microsoft\Windows\WER\ReportQueue</code>>. 79 79 Check the modification date to make sure you are using the correct file. 80 80 </p> 81 81 <p>Be sure to include the following files in your bug report:</p> 82 82 <dl style="margin-left:2em"> 83 <dt>< tt>WER<em>xxxx</em>.tmp.mdmp</tt></dt>83 <dt><code>WER<em>xxxx</em>.tmp.mdmp</code>></dt> 84 84 <dd>This is the most important file. It contains the crash dump that can be opened inside Visual Studio or other Windows debuggers.</dd> 85 <dt>< tt>WER<em>xxxx</em>.tmp.version.txt</tt></dt>85 <dt><code>WER<em>xxxx</em>.tmp.version.txt</code>></dt> 86 86 <dd>Contains the operating system version and other hardware information.</dd> 87 <dt>< tt>WER<em>xxxx</em>.tmp.appcompat.txt</tt></dt>87 <dt><code>WER<em>xxxx</em>.tmp.appcompat.txt</code>></dt> 88 88 <dd>Lists all of the DLLs loaded at the time of the crash with their version information.</dd> 89 89 </dl> -
trunk/WebKitSite/quality/lifecycle.html
r52433 r56300 14 14 <h3>Fresh, Unconfirmed Bugs</h3> 15 15 16 <p>A freshly-created bug starts out in state < tt>UNCONFIRMED</tt>. Often it is in component <tt>New Bugs</tt>, but16 <p>A freshly-created bug starts out in state <code>UNCONFIRMED</code>. Often it is in component <code>New Bugs</code>, but 17 17 some bugs will be given an initial component in the initial <a href="reporting.html">bug-reporting step</a>.</p> 18 18 19 19 20 <h3><a name="confirming"></a>Confirming Bugs</h3>20 <h3><a id="confirming"></a>Confirming Bugs</h3> 21 21 22 <p>The next step is for someone with Bugzilla < tt>canConfirm</tt> privileges to review the unconfirmed bug and22 <p>The next step is for someone with Bugzilla <code>canConfirm</code> privileges to review the unconfirmed bug and 23 23 decide whether it has enough useful information to move forward. The possible changes to the bug at this step include the following:</p> 24 24 25 25 <ul> 26 <li>Resolution changed to < tt>DUPLICATE</tt> if the bug is determined to have the same cause as a bug reported earlier.</li>27 <li>Resolution changed to < tt>WORKSFORME</tt> if the bug seems to not be present in the latest sources.</li>28 <li>Resolution changed to < tt>INVALID</tt> if the bug does not describe a problem with WebKit.</li>29 <li>Resolution changed to < tt>WONTFIX</tt> in the rare case that the bug seems valid but there's a specific reason why it26 <li>Resolution changed to <code>DUPLICATE</code> if the bug is determined to have the same cause as a bug reported earlier.</li> 27 <li>Resolution changed to <code>WORKSFORME</code> if the bug seems to not be present in the latest sources.</li> 28 <li>Resolution changed to <code>INVALID</code> if the bug does not describe a problem with WebKit.</li> 29 <li>Resolution changed to <code>WONTFIX</code> in the rare case that the bug seems valid but there's a specific reason why it 30 30 should not be fixed in WebKit (usually this would be a cross-browser compatibility issue).</li> 31 31 <li>Comments/questions added if the bug does not have enough information to move forward.</li> 32 <li>Status changed to < tt>NEW</tt> if the bug is reproducible with the latest sources on Mac OS X or otherwise has enough information to move forward.32 <li>Status changed to <code>NEW</code> if the bug is reproducible with the latest sources on Mac OS X or otherwise has enough information to move forward. 33 33 If the bug is not reproducible with the latest sources, but appears to occur only on the platform stated in the platform field, 34 the < tt>PlatformOnly</tt> keyword is added as well as setting the status to <tt>NEW</tt>.35 Along with changing the status, the component should also be set to an appropriate one more specific than < tt>New Bugs</tt> if necessary.</li>34 the <code>PlatformOnly</code> keyword is added as well as setting the status to <code>NEW</code>. 35 Along with changing the status, the component should also be set to an appropriate one more specific than <code>New Bugs</code> if necessary.</li> 36 36 </ul> 37 37 … … 39 39 40 40 <p>Each bug is initially assigned to the person designated as owner of the component. The assignee should move the bug from status 41 < tt>NEW</tt> to status <tt>ASSIGNED</tt> after they have read the bug and are satisfied that it represents a real problem in WebKit.41 <code>NEW</code> to status <code>ASSIGNED</code> after they have read the bug and are satisfied that it represents a real problem in WebKit. 42 42 If they are not satisfied about this, they should perform one of the actions mentioned in the <a href="#confirming">Confirming Bugs</a> section above. 43 The same procedure is followed for bugs with status < tt>REOPENED</tt> (see <a href="#verifying">Verifying Fixes</a> below).</p>43 The same procedure is followed for bugs with status <code>REOPENED</code> (see <a href="#verifying">Verifying Fixes</a> below).</p> 44 44 45 45 <p>The assignee represents the person who is expected to take the next step in investigating or fixing a bug. If someone other than the assignee is … … 49 49 <h3>Proposing Fixes</h3> 50 50 51 <p>A proposed patch should be added as a new attachment. The attachment should have the < tt>patch</tt> checkbox checked, and the <tt>review</tt> flag set to <tt>?</tt>. This51 <p>A proposed patch should be added as a new attachment. The attachment should have the <code>patch</code> checkbox checked, and the <code>review</code> flag set to <code>?</code>. This 52 52 marks the patch as awaiting review. If the patch requires the specialized knowledge of a particular reviewer, the submitter or another reviewer should put 53 the requested reviewer's email address in the < tt>Requestee</tt> field. Otherwise this field should be left empty. The state is left at <tt>ASSIGNED</tt> at54 this point; it isn't changed to < tt>FIXED</tt> until a fix has been checked into the source tree.</p>53 the requested reviewer's email address in the <code>Requestee</code> field. Otherwise this field should be left empty. The state is left at <code>ASSIGNED</code> at 54 this point; it isn't changed to <code>FIXED</code> until a fix has been checked into the source tree.</p> 55 55 56 56 <p>When the review flag's state is changed, or when a comment is made in the Edit form for an attachment, email is automatically sent to … … 58 58 this list, and anyone else is free to do so as well.</p> 59 59 60 <p>If the submitter of a patch changes their mind about wanting a review, they should clear the < tt>review</tt> flag by choosing the60 <p>If the submitter of a patch changes their mind about wanting a review, they should clear the <code>review</code> flag by choosing the 61 61 blank choice in the review pop-menu.</p> 62 62 … … 65 65 <h3>Reviewing Proposed Fixes</h3> 66 66 67 <p>A reviewer will read through each proposed patch. If the patch is ready to commit, the reviewer will change the < tt>review</tt> flag to <tt>+</tt>.67 <p>A reviewer will read through each proposed patch. If the patch is ready to commit, the reviewer will change the <code>review</code> flag to <code>+</code>. 68 68 For clarity, it's helpful for the reviewer to add a comment when approving a patch. Often this comment is just "r=me", which is simply shorthand for 69 69 "I have reviewed this patch and it's ready to commit".</p> … … 73 73 explain in detail why a patch is not ready to commit, so the submitter or someone else can revise the patch.</p> 74 74 75 <p>When a submitter proposes an updated patch, they should check the < tt>obsolete</tt> checkbox on the previous version of the patch. This causes it76 to appear crossed-out in the list of attachments on the bug's main page. At the same time as marking the old patch < tt>obsolete</tt>, the77 submitter should also clear the < tt>review</tt> flag. This would happen automatically in a perfect world, but doesn't currently in this one.</p>75 <p>When a submitter proposes an updated patch, they should check the <code>obsolete</code> checkbox on the previous version of the patch. This causes it 76 to appear crossed-out in the list of attachments on the bug's main page. At the same time as marking the old patch <code>obsolete</code>, the 77 submitter should also clear the <code>review</code> flag. This would happen automatically in a perfect world, but doesn't currently in this one.</p> 78 78 79 79 <h3>Committing Patches</h3> 80 80 81 81 <p>After a patch has been approved, someone with commit privileges in the WebKit source repository will commit the patch into the source code repository. The committer 82 should change the state of the bug to < tt>FIXED</tt>; generally the assignee is left unchanged at this point.</p>82 should change the state of the bug to <code>FIXED</code>; generally the assignee is left unchanged at this point.</p> 83 83 84 84 <p>All of the … … 92 92 Software Changed/Integrate.</p> 93 93 94 <h3><a name="verifying"></a>Verifying Fixes</h3>94 <h3><a id="verifying"></a>Verifying Fixes</h3> 95 95 96 96 <p>After the patch for a bug has been committed, the fix still needs to be verified. Typically this step is done by the person who originally submitted the 97 97 bug report. If the submitter is not available or does not feel that they can verify the fix, the verification step can be done by anyone with bug editing 98 98 privileges who is familiar enough with the originally reported problem to be confident about 99 testing it. Note that once a bug is in the < tt>FIXED</tt> state, the assignee can no longer be changed. This means that a bug that needs99 testing it. Note that once a bug is in the <code>FIXED</code> state, the assignee can no longer be changed. This means that a bug that needs 100 100 to be verified will not usually be assigned to the person expected to verify the bug.</p> 101 101 102 102 <p>To verify a bug fix, build and run the sources that include the fix, and check whether 103 the originally reported problem still occurs. If the problem no longer occurs, change the resolution to < tt>VERIFIED</tt>. If the problem does still occur,104 change the resolution to < tt>REOPENED</tt> and assign it to the person who submitted the patch.</p>103 the originally reported problem still occurs. If the problem no longer occurs, change the resolution to <code>VERIFIED</code>. If the problem does still occur, 104 change the resolution to <code>REOPENED</code> and assign it to the person who submitted the patch.</p> 105 105 106 106 107 107 <h3>Closing Bugs</h3> 108 108 109 <p>Fixed bugs have the < tt>VERIFIED</tt> resolution until a version of WebKit that includes the fix has been publicly released. At this point,110 the resolution is changed to < tt>CLOSED</tt>.109 <p>Fixed bugs have the <code>VERIFIED</code> resolution until a version of WebKit that includes the fix has been publicly released. At this point, 110 the resolution is changed to <code>CLOSED</code>. 111 111 112 112 <?php -
trunk/WebKitSite/quality/testing.html
r51733 r56300 9 9 <p>Before patches can land in any of the frameworks in the repository, the 10 10 layout regression tests must pass. To run these tests, execute the 11 < tt>run-webkit-tests</tt> <a href="/coding/scripts.html">script</a>.</p>11 <code>run-webkit-tests</code> <a href="/coding/scripts.html">script</a>.</p> 12 12 13 13 <p>The script will dump the render trees for all of the pages and diff the results against the expected correct results. If no … … 30 30 <table> 31 31 <tr> 32 <td valign="top">32 <td style="vertical-align: top"> 33 33 <ul> 34 34 <li>Arrays</li> … … 38 38 </ul> 39 39 </td> 40 <td valign="top">40 <td style="vertical-align: top"> 41 41 <ul> 42 42 <li>Global Object</li> … … 46 46 </ul> 47 47 </td> 48 <td valign="top">48 <td style="vertical-align: top"> 49 49 <ul> 50 50 <li>Regular Expressions</li> … … 61 61 <h3>How to run the tests</h3> 62 62 63 <p>Execute the < tt>run-javascriptcore-tests</tt> <a href="/coding/scripts.html">script</a>.63 <p>Execute the <code>run-javascriptcore-tests</code> <a href="/coding/scripts.html">script</a>. 64 64 The script will run all the tests and summarize how the results differ 65 65 from what is currently expected.</p> … … 67 67 <h3>What just happened</h3> 68 68 <p> 69 After all the test runs have finished the results of tests are saved to < tt>actual.html</tt>.69 After all the test runs have finished the results of tests are saved to <code>actual.html</code>. 70 70 The script the compares these results from your local tree against what is expected to pass/fail from the tip of tree. 71 71 If there are any regressions caused by your changes you'll be made aware of them. … … 82 82 83 83 <p>It's not the end of the world. Go back and fix your bug and rerun 84 < tt>run-javascriptcore-tests</tt> as many times as necessary.</p>84 <code>run-javascriptcore-tests</code> as many times as necessary.</p> 85 85 86 86 <?php -
trunk/WebKitSite/quality/testwriting.html
r44604 r56300 21 21 </ol> 22 22 23 <p>An example of a layout test that follows these guidelines is < tt>fast/events/event-creation.html</tt>.</p>23 <p>An example of a layout test that follows these guidelines is <code>fast/events/event-creation.html</code>.</p> 24 24 25 25 26 26 <p>A layout test should work both in the browser itself, and in the layout test tool. The layout test tool provides an 27 27 additional object on the window object called the layout test controller with some methods that control test output. 28 One you should know about is the < tt>layoutTestController.dumpAsText</tt> method. Calling this from JavaScript within a test arranges28 One you should know about is the <code>layoutTestController.dumpAsText</code> method. Calling this from JavaScript within a test arranges 29 29 for the output to be written out as plain text rather than as a render tree dump. 30 30 This is useful for tests that are testing something other than layout. The event creation test mentioned above is a good example of … … 33 33 <p>Some tests require pixel-level comparisons. For these tests, you must generate expected output for a specific 34 34 machine type, operating system, and color profile. When you add such a test, you can generate new expected output 35 automatically using the < tt>run-webkit-tests --pixel</tt> command. This will automatically35 automatically using the <code>run-webkit-tests --pixel</code> command. This will automatically 36 36 configure the color profile, and place the resulting rendered image (and checksum) in the appropriate platform 37 37 directory for checkin.</p>
Note: See TracChangeset
for help on using the changeset viewer.