+2006-09-21 Mark Rowe <opendarwin.org@bdash.net.nz>
+
+ Reviewed by TimH.
+
+ Updates to make static pages validate as HTML 4.01 Strict.
+
+ * building/build.html:
+ * coding/coding-style.html:
+ * header.inc:
+ * index.html: Move <style> tag into the document head.
+ * projects/cleanup/index.html:
+ * projects/compat/index.html:
+ * projects/css/index.html:
+ * projects/documentation/index.html:
+ * projects/editing/index.html:
+ * projects/forms/index.html: Remove note about <label> not being implemented correctly.
+ * projects/html/index.html:
+ * projects/javascript/index.html:
+ * projects/performance/index.html:
+ * projects/portability/index.html: Change mention of Windows port to note that it is in progress rather than non-existant.
+ * projects/printing/index.html:
+ * projects/svg/index.html:
+ * projects/xslt/index.html:
+ * quality/bugwriting.html: Update WebKit version numbers to be accurate. Move JS away from using innerHTML as W3C validator doesn't like it.
+ * quality/reduction.html:
+ * quality/reporting.html: Rename element IDs that start with numbers. Update WebKit and Mac OS X version numbers to be accurate.
+ * quality/testing.html:
+
2006-09-19 Brady Eidson <beidson@apple.com>
http://bugzilla.opendarwin.org/show_bug.cgi?id=8220
<?php
- $title = "Building WebKit";
- include("../header.inc");
+ $title = "Building WebKit";
+ include("../header.inc");
?>
<h2>Building WebKit</h2>
<ol>
<li><p>Type this command to run Safari with the WebKit you built:</p>
<p class="code">WebKit/WebKitTools/Scripts/run-safari</p>
-</li>
<p>Use the <tt>--debug</tt> option for a debug build:</p>
<p class="code">WebKit/WebKitTools/Scripts/run-safari --debug</p>
+</li>
</ol>
<p>The <tt>run-safari</tt> script sets the <tt>DYLD_FRAMEWORK_PATH</tt> environment variable to point to your build products,
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>
</li>
<li><p>Set the project's build products location</p>
<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>
-<img src="info-tab.png"></img>
+<img src="info-tab.png">
</li>
<li><p>Set the project's active build configuration</p>
<p>Xcode also needs to know the build configuration you used. You can set the active build configuration from the project's Build window.</p>
-<img src="build-window.png"></img>
+<img src="build-window.png">
</li>
<li><p>Add a custom executable to the project</p>
<p>Choose any WebKit application you want to use for debugging. To use Safari, select /Applications/Safari.app.</p>
-<img src="custom-executable.png"></img>
+<img src="custom-executable.png">
</li>
<li><p>Set the project's active executable</p>
<p>You can set the active executable from the project's Build window. Choose the executable you just added.</p>
</li>
<li><p>Launch the debugger</p>
<p>In the Debugger window, click the "Debug" button.</p>
-<img src="debug.png"></img>
+<img src="debug.png">
</li>
</ol>
<?php
- include("../footer.inc");
+ include("../footer.inc");
?>
</pre>
<h4 style="color: #ff0000 !important">Wrong:</h4>
-</pre>
<pre style="background-color: #F2F2F2">
for (int i = 0; i < 10; i++)
{
if (timeToGoHome)
outtaHere = true;
- </pre>
-</li>
</pre>
</li>
</ol>
<h3>Names</h3>
<ol>
-<li>General Rule: With very few exceptions, prefer embedded capitals instead of underscores for class, function and variable names.</p></li>
+<li>General Rule: With very few exceptions, prefer embedded capitals instead of underscores for class, function and variable names.</li>
<li>C++ and Objective-C classes, interfaces and protocols, and other type names — these names should start with a capital letter and use InterCaps.<br />
<h4 style="color: #008000 !important">Right:</h4>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
<head>
- <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
- <title>The WebKit Open Source Project<?php if (isset($title)) { echo " - " . $title; } ?></title>
+ <title>The WebKit Open Source Project<?php if (isset($title)) { echo " - " . $title; } ?></title>
- <link rel="stylesheet" type="text/css" href="/css/main.css" />
- <link rel="stylesheet" type="text/css" href="/css/green.css" title="green" />
+ <link rel="stylesheet" type="text/css" href="/css/main.css">
+ <link rel="stylesheet" type="text/css" href="/css/green.css" title="green">
<?php
$msie = '/msie\s(5\.[5-9]|[6]\.[0-9]*).*(win)/i';
$agent = $_SERVER['HTTP_USER_AGENT'];
if( isset($agent) && preg_match($msie, $agent) && ! preg_match('/opera/i', $agent)) {
?>
- <link rel="stylesheet" type="text/css" href="/css/ie.css" />
+ <link rel="stylesheet" type="text/css" href="/css/ie.css">
<?php } else { ?>
- <link rel="alternate stylesheet" type="text/css" href="/css/blue.css" title="blue" />
- <link rel="alternate stylesheet" type="text/css" href="/css/yellow.css" title="yellow" />
- <link rel="alternate stylesheet" type="text/css" href="/css/pink.css" title="pink" />
- <link rel="alternate stylesheet" type="text/css" href="/css/purple.css" title="purple" />
- <link rel="alternate stylesheet" type="text/css" href="/css/gray.css" title="gray" />
+ <link rel="alternate stylesheet" type="text/css" href="/css/blue.css" title="blue">
+ <link rel="alternate stylesheet" type="text/css" href="/css/yellow.css" title="yellow">
+ <link rel="alternate stylesheet" type="text/css" href="/css/pink.css" title="pink">
+ <link rel="alternate stylesheet" type="text/css" href="/css/purple.css" title="purple">
+ <link rel="alternate stylesheet" type="text/css" href="/css/gray.css" title="gray">
<?php } ?>
- <script type="text/javascript">
- pic1 = new Image(8,9);
- pic1.src="/images/green-bullet.png";
- pic2 = new Image(8,9);
- pic2.src="/images/blue-bullet.png";
- pic3 = new Image(8,9);
- pic3.src="/images/yellow-bullet.png";
- pic4 = new Image(8,9);
- pic4.src="/images/pink-bullet.png";
- pic5 = new Image(8,9);
- pic5.src="/images/purple-bullet.png";
- </script>
-
+ <script type="text/javascript">
+ pic1 = new Image(8,9);
+ pic1.src="/images/green-bullet.png";
+ pic2 = new Image(8,9);
+ pic2.src="/images/blue-bullet.png";
+ pic3 = new Image(8,9);
+ pic3.src="/images/yellow-bullet.png";
+ pic4 = new Image(8,9);
+ pic4.src="/images/pink-bullet.png";
+ pic5 = new Image(8,9);
+ pic5.src="/images/purple-bullet.png";
+ </script>
+
<?php
if (isset($extra_head_content)) {
echo $extra_head_content;
-<?php include("header.inc"); ?>
-
+<?php
+$extra_head_content = <<<EOF
<style type="text/css">
p { margin: 0px 0px 4px 0px; }
</style>
+EOF;
+include("header.inc");
+?>
<h2>Welcome to the website for the WebKit Open Source Project!</h2>
<p>WebKit is an open source web browser engine.
<a href="http://nightly.webkit.org/"><img src="images/download.png" id="download" alt="download nightly" width="189" height="65" /></a>
<p>There are many ways in which you can get involved with the project. You can:</p>
<ul>
-
<li><a href="building/checkout.html">check out</a> and <a href="building/build.html">build the source code</a></li>
-
<li><a href="http://nightly.webkit.org/">download the latest nightly build</a></li>
-</ul>
+ <li><a href="building/checkout.html">check out</a> and <a href="building/build.html">build the source code</a></li>
+ <li><a href="http://nightly.webkit.org/">download the latest nightly build</a></li>
+</ul>
<p>Once you have either of these, you can help by:</p>
<ul>
-
<li><a href="quality/reporting.html">reporting bugs</a> you find in the software</li>
-
<li>providing <a href="quality/reduction.html">reductions</a> to bugs</li>
-
<li>submitting <a href="coding/contributing.html">patches for review</a></li>
+ <li><a href="quality/reporting.html">reporting bugs</a> you find in the software</li>
+ <li>providing <a href="quality/reduction.html">reductions</a> to bugs</li>
+ <li>submitting <a href="coding/contributing.html">patches for review</a></li>
</ul>
<h2>More info</h2>
<h2>Projects</h2>
<p>There are many exciting (new) <a href="projects/index.html">projects</a> that you can contribute to:</p>
<ul>
-
<li>help us improve <a href="projects/compat/index.html">Website compatibility</a></li>
-
<li>write <a href="projects/documentation/index.html">documentation</a></li>
-
<li><a href="projects/svg/index.html">SVG</a></li>
-
<li><a href="projects/mathml/index.html">MathML</a></li>
-
<li><a href="projects/css/index.html">CSS</a></li>
-
<li><a href="projects/dom/index.html">DOM</a></li>
+ <li>help us improve <a href="projects/compat/index.html">Website compatibility</a></li>
+ <li>write <a href="projects/documentation/index.html">documentation</a></li>
+ <li><a href="projects/svg/index.html">SVG</a></li>
+ <li><a href="projects/mathml/index.html">MathML</a></li>
+ <li><a href="projects/css/index.html">CSS</a></li>
+ <li><a href="projects/dom/index.html">DOM</a></li>
</ul>
-<?php include("footer.inc"); ?>
\ No newline at end of file
+<?php include("footer.inc"); ?>
<?php
- $title = "Code Cleanup";
- include("../../header.inc");
+ $title = "Code Cleanup";
+ include("../../header.inc");
?>
<h2>Code Cleanup</h2>
<h3>Get Involved!</h3>
+<dl>
<dt>Follow the Coding Style Guidelines</dt>
<dd>We welcome patches that clean up code to follow our coding style guidelines.
WebCore and WebKit know about loading subresources and have their own frame trees).</dd>
<dt>[TODO: ADD MORE TASKS]</dt>
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
\ No newline at end of file
<?php
- $title = "Web Site Compatibility";
- include("../../header.inc");
+ $title = "Web Site Compatibility";
+ include("../../header.inc");
?>
<h2>Web Site Compatibility</h2>
<h3>Get Involved!</h3>
<p>How can you help us improve web site compatibility in Safari?</p>
+
+<dl>
<dt>Test Test Test!</dt>
<dd>Build the latest WebKit and use it day to day. Visit all of your favorite Web sites and scrutinize them all closely. Make sure
they all work as expected, and if they don't then report problems to us.
<dt>Create New Tests</dt>
<dd>To help avoid regressions you can make new tests, even for features that WebKit already handles correctly. The more regression tests
we have covering a specific feature, the less likely it is that the feature will break when we make changes.
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
\ No newline at end of file
<?php
- $title = "CSS (Cascading Style Sheets)";
- include("../../header.inc");
+ $title = "CSS (Cascading Style Sheets)";
+ include("../../header.inc");
?>
<h2>CSS (Cascading Style Sheets)</h2>
<h3>Get Involved!</h3>
-<a href="http://bugs.webkit.org/buglist.cgi?component=CSS&resolution=---">
+<a href="http://bugs.webkit.org/buglist.cgi?component=CSS&resolution=---">
View bugs in the CSS component on OpenDarwin.
</a>
<p>Here are some of the tasks that you can get involved with in CSS.</p>
+<dl>
<dt>Complete CSS1 Support</dt>
<dd>Only a handful of CSS1 bugs remain, primarily with text-transform capitalize. Look for bugs that have been prefaced with "CSS1:" in the title.
Complete support is measured by passing the CSS1 test suite.
<dd>Check out the <a href="http://www.w3.org/Style/CSS/Test/CSS2.1/current/">CSS2.1 test suite</a>
and file compliance bugs so that we can track open issues with our CSS2.1 compliance.
+</dl>
+
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
\ No newline at end of file
<?php
- $title = "Documentation";
- include("../../header.inc");
+ $title = "Documentation";
+ include("../../header.inc");
?>
<h2>Documentation</h2>
<h3>Get Involved!</h3>
Here are some tasks that you can help with.
+<dl>
<dt>Developer Documentation</dt>
<dd>We would like to build up a web site that describes in detail the DOM methods, CSS properties and APIs that are supported by the different versions of
Safari and WebKit, so that people have a place to go to where they can find out what we support.</dd>
within the project pages themselves.
<dt>[TODO: Add links to existing Apple docs]</dt>
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
\ No newline at end of file
<?php
- $title = "HTML Editing";
- include("../../header.inc");
+ $title = "HTML Editing";
+ include("../../header.inc");
?>
<h2>HTML Editing</h2>
<h3>Get Involved!</h3>
-<a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=HTML+Editing&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---">
+<a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=HTML+Editing&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---">
View bugs in the HTML editing component on OpenDarwin.</a>
-</p>
-Below are some of the tasks that need work in HTML editing.
+<p>Below are some of the tasks that need work in HTML editing.</p>
+<dl>
<dt>Improve contentEditable divs</dt>
<dd>Right now there are a number of issues with editable divs in a Web page. The selection highlighting is not confined to the div,
and extending the selection across editable and non-editable content should not be possible. In addition WebKit always clears
<dt>Support more of WinIE's APIs</dt>
<dd>We want to support more of WinIE's editing APIs, including more commands and text ranges. We welcome any WinIE-compatible patches that
improve editing support to match WinIE.
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "HTML Forms";
- include("../../header.inc");
+ $title = "HTML Forms";
+ include("../../header.inc");
?>
<h2>HTML Forms</h2>
<h3>Get Involved!</h3>
-<a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=HTML+Forms&resolution=---">
+<a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=HTML+Forms&resolution=---">
View bugs in the HTML Forms component on OpenDarwin.
</a>
</p>
<dl>
-
-<dt><a href="http://bugs.webkit.org/show_bug.cgi?id=3244">Support the <tt>label</tt> element</a>
-<dd>WebKit does not properly support the <tt>label</tt> element.
-
<dt>Use WebKit to implement the controls</dt>
-<dd>The HTML form controls are currently implemented without using the WebKit engine. Right now WebKit talks to Qt interfaces that represent the controls.
+<dd>
+<p>The HTML form controls are currently implemented without using the WebKit engine. Right now WebKit talks to Qt interfaces that represent the controls.
On OS X our implementation of these Qt interfaces uses App Kit. The major architectural change that we are planning for form controls in the coming year
is to re-implement the form controls using the WebKit engine itself to render. This will allow us to support more CSS properties for form controls, make
-our code more portable to other platforms, and - most importantly - will improve our performance significantly on pages with a large number of controls.</p>
+our code more portable to other platforms, and - most importantly - will improve our performance significantly on pages with a large number of controls.
<p>For input fields and text areas, we plan to use <a href="../editing/index.html">HTML editing</a> to implement these controls, and for the other controls custom
renderers will be made. A new theme abstraction will be used to encapsulate the rendering of a native look on the platform with <tt>NSCells</tt> being used to
<dd>The <a href="http://whatwg.org">WhatWG</a> has outlined extensions to existing HTML forms. We are interested in supporting these extensions (along with Opera
and Mozilla). The <a href="http://whatwg.org/specs/web-forms/current-work/">specification</a> details all of these enhancements. We welcome bugs, contributions and
testers to help us implement these improvements.
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
\ No newline at end of file
<?php
- $title = "HTML and XHTML (HyperText Markup Language)";
- include("../../header.inc");
+ $title = "HTML and XHTML (HyperText Markup Language)";
+ include("../../header.inc");
?>
<h2>HTML and XHTML (HyperText Markup Language)</h2>
</p>
<h3>Get Involved!</h3>
-<a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=HTML+DOM&resolution=---">
+<a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=HTML+DOM&resolution=---">
View bugs in the HTML component on OpenDarwin.</a>
-</p>
+<dl>
<dt>Complete HTML4 Support</dt>
<dd>There are a handful of HTML4 issues remaining, including implementing the LABEL element, adding support for a few more attributes for legacy HTML
to APPLET and OBJECT, implementing the BDO element, and implementing alignment inheritance in table columns.</dd>
<dd>We want to improve our XHTML rendering, making it as incremental as HTML and making sure entity support and scripts work properly.
<dt>Extend HTML</dt>
<dd>We are interested in the WhatWG work to extend HTML to have functionality that has not been covered in any other HTML specifications.
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "JavaScript";
- include("../../header.inc");
+ $title = "JavaScript";
+ include("../../header.inc");
?>
<h2>JavaScript</h2>
<h3>Get Involved!</h3>
-<a href="http://bugs.webkit.org/buglist.cgi?component=JavaScript&resolution=---">
+<a href="http://bugs.webkit.org/buglist.cgi?component=JavaScript&resolution=---">
View bugs in the JavaScript component on OpenDarwin.
</a>
<p>Here are some of the tasks that you can get involved with in JavaScript.</p>
+<dl>
<dt>Bytecode Interpreter</dt>
<dd>JavaScriptCore currently creates a syntax tree and then uses that syntax tree when executing JavaScript.
We'd like to use a bytecode interpreter instead, and if it's done right it will make JavaScript run faster and use less memory.</dd>
<dd>JavaScriptCore currently has the original C++ method of binding native code to JavaScript, an Objective-C binding that's exported from WebKit
as WebScriptObject, and a browser plug-in oriented C binding. We'd like to create a generic C language binding suitable for use by
any project that wants to take advantage of the JavaScript engine, but which is easier to maintain compatibly than a C++ binding.</dd>
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "Performance";
- include("../../header.inc");
+ $title = "Performance";
+ include("../../header.inc");
?>
<h2>Performance</h2>
<p>How can you help improve WebKit's performance?</p>
+<dl>
<dt>Test for Regressions</dt>
<dd>If you have your own performance tests, run WebKit through them daily. Make sure that the performance of the sites you care about
does not regress. Test the above benchmarks on your hardware to help double-check that there have not been any regressions. Remember, the best
performance problems and file bugs with that information. <a href="http://developer.apple.com/tools/shark_optimize.html">Here is a link</a> to get you
started using Shark.
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "Portability";
- include("../../header.inc");
+ $title = "Portability";
+ include("../../header.inc");
?>
<h2>Portability</h2>
<h3>Get Involved!</h3>
+<dl>
<dt>Move WebKit code into WebCore</dt>
<dd>Over time the WebKit framework has grown to contain a lot of code written in Objective-C that has no real business being in this framework. Now that both
frameworks are open source, we would like to move as much of this code as possible from WebKit into WebCore. This means rewriting the code to be C++ instead of
<dd>One port of WebCore already exists, the GTK+ port. We are interested in integrating this into our source tree, and believe that doing so will help us to
refactor our code to make future ports easier.
-<dt>Start Porting!</dt>
-<dd>Want to start porting to Windows or some other platform? <a href="../../contact.html">Contact us</a> and start submitting patches!
+<dt>Help Porting!</dt>
+<dd>Want to help with porting to Windows or some other platform? <a href="../../contact.html">Contact us</a> and start submitting patches!
+
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "Printing";
- include("../../header.inc");
+ $title = "Printing";
+ include("../../header.inc");
?>
<h2>Printing</h2>
<h3>Get Involved</h3>
+<dl>
<dt>Rework Printing</dt>
<dd>Printing needs to be reworked so that render objects know how to split themselves across breaks. This allows two separate formatting contexts (like two adjacent table
cells) to still have their contents both break cleanly across a page. This work is also important for future technology like CSS3 multi-column support. The code
that splits render objects across pages could obviously be leveraged to also split render objects across column breaks as well.
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "SVG (Scalable Vector Graphics)";
- include("../../header.inc");
+ $title = "SVG (Scalable Vector Graphics)";
+ include("../../header.inc");
?>
<h2>SVG (Scalable Vector Graphics)</h2>
<ul>
<li>
-<a href="http://bugs.webkit.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=WebKit&component=SVG&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
+<a href="http://bugs.webkit.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=WebKit&component=SVG&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
View bugs in the SVG component on OpenDarwin.</a></li>
<li><a href="http://wiki.opendarwin.org/index.php/WebKit_plus_SVG">The WebCore+SVG Wiki page</a></li>
<li><a href="status.xml">WebKit+SVG official status page</a></li>
</ul>
+<dl>
<dt>Get on IRC</dt>
<dd>There is still much work to be done to complete our implementation of <a href="http://www.w3.org/TR/SVG/">SVG 1.1 FULL</a>.
Development discussions take place on Freenode in <tt>#ksvg</tt> and <tt>#webkit</tt>.
<dd>SVG Support is enabled in the <a href="http://nightly.webkit.org/">latest nightly builds</a>.
Give it a whirl; try to break it!
If WebKit doesn't render your favorite SVG perfectly, please <a href="../../quality/reporting.html">file a bug</a>.</dd>
+</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "XSLT";
- include("../../header.inc");
+ $title = "XSLT";
+ include("../../header.inc");
?>
<h2>XSLT</h2>
<h3>Get Involved!</h3>
-<p><a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=XSLT&resolution=---">
+<p><a href="http://bugs.webkit.org/buglist.cgi?product=WebKit&component=XSLT&resolution=---">
View bugs in the XSLT component on OpenDarwin.</a>
</p>
</dl>
<?php
- include("../../footer.inc");
+ include("../../footer.inc");
?>
<?php
- $title = "Bug Report Guidelines";
- include("../header.inc");
+ $title = "Bug Report Guidelines";
+ include("../header.inc");
?>
<h2>Bug Report Guidelines</h2>
you can provide, the better.</p>
<ol>
- <li><b>Version</b>
- Please select the WebKit version you were using when the bug occurred, or the closest match. <tt>312</tt> is the WebKit version
- that shipped with Mac OS X 10.3.9. <tt>412</tt> up to <tt>417.9</tt> are the WebKit versions that shipped with Mac OS X 10.4 (Tiger)
- and it's updates.
- </p>
- Locally-built versions of WebKit have a <tt>+</tt> after the build number, and their build number is generally higher
- then the latest release version. So, for example, <tt>420+</tt> is a
- locally-built version of WebKit that's newer than the <tt>417.9</tt> version that shipped with the latest update of Tiger.
- </p>
- <div style="display: none; text-align: center;" id="webkit_version"></div>
- <script type="text/javascript">
- var regex;
- var matches;
+ <li><b>Version</b>
+ <p>
+ Please select the WebKit version you were using when the bug occurred, or the closest match. <tt>312</tt> is the WebKit version
+ that shipped with Mac OS X 10.3.9. <tt>412</tt> up to <tt>418.8</tt> are the WebKit versions that shipped with Mac OS X 10.4 (Tiger)
+ and it's updates.
+ </p>
+ <p>
+ Locally-built versions of WebKit have a <tt>+</tt> after the build number, and their build number is generally higher
+ then the latest release version. So, for example, <tt>420+</tt> is a
+ locally-built version of WebKit that's newer than the <tt>418.8</tt> version that shipped with the latest update of Tiger.
+ </p>
+ <div style="display: none; text-align: center; font-weight: bold;" id="webkit_version"></div>
+ <script type="text/javascript">
+ var regex;
+ var matches;
- regex = new RegExp("Mozilla/5.0 \\(.*\\) AppleWebKit/(.*) \\(KHTML, like Gecko\\) Safari/(.*)");
- matches = regex.exec(navigator.userAgent);
- if (matches)
- {
- document.getElementById('webkit_version').innerHTML = "<strong>You are currently using: <tt>" + matches[1] + ".</tt></strong><br><br>";
- document.getElementById('webkit_version').style.display = "block";
- webKitVersion = parseInt(matches[1]);
- }
- </script>
+ regex = new RegExp("Mozilla/5.0 \\(.*\\) AppleWebKit/(.*) \\(KHTML, like Gecko\\) Safari/(.*)");
+ matches = regex.exec(navigator.userAgent);
+ if (matches)
+ {
+ var webKitVersion = document.getElementById('webkit_version');
+ webKitVersion.appendChild(document.createTextNode("You are currently using: "));
+ var versionNumber = document.createElement("tt");
+ versionNumber.appendChild(document.createTextNode(matches[1]));
+ webKitVersion.appendChild(versionNumber);
+ webKitVersion.style.display = "block";
- <li><b>Component</b>
- <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
- assign a bug to a specific component such as <tt>CSS</tt> or <tt>HTML Editing</tt>.
- <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 component
- 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
- will be moved from the <tt>New Bugs</tt> component to the appropriate place.</p>
- </li>
+ webKitVersion = parseInt(matches[1]);
+ }
+ </script>
- <li>
- <b>Platform and OS</b>
- <p>Please select the platform and the OS version that your bug occurred on. Typically this would be platform <tt>Macintosh</tt>
- and OS <tt>Mac OS X 10.3</tt> (Panther) or <tt>Mac OS X 10.4</tt> (Tiger). </p>
- </li>
+ <li><b>Component</b>
+ <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
+ assign a bug to a specific component such as <tt>CSS</tt> or <tt>HTML Editing</tt>.
+ <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 component
+ 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
+ will be moved from the <tt>New Bugs</tt> component to the appropriate place.</p>
+ </li>
- <li>
- <b>Priority</b>
- <p>Normally a QA person or developer will set this, so the bug submitter can leave this at the default value. A number of
- <a href="bugpriorities.html">guidelines</a> and some individual judgment are involved in setting the priority. If you know the
- bug is a regression, ie. something is wrong which wasn't wrong in previous versions of WebKit, you can set this to P1.</p>
- </li>
+ <li>
+ <b>Platform and OS</b>
+ <p>Please select the platform and the OS version that your bug occurred on. Typically this would be platform <tt>Macintosh</tt>
+ and OS <tt>Mac OS X 10.3</tt> (Panther) or <tt>Mac OS X 10.4</tt> (Tiger). </p>
+ </li>
- <li>
- <b>Severity</b>
- <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 an
- <tt>enhancement</tt>, it's helpful to specify that value. A QA person or developer will set this to some other value if
- appropriate.</p>
- </li>
-
- <li><b>URL</b>
- <p>Fill in this field with the URL of a page that shows the bug, when possible. If you have created a <a href="reduction.html">test case reduction</a> for the bug,
- please add it to the bug report as an attachment rather than putting it on a web server and listing its URL here. Doing so
- makes it easier to work on the bug, and can be a first step towards checking in the test case along with the bug fix.</p>
- </li>
+ <li>
+ <b>Priority</b>
+ <p>Normally a QA person or developer will set this, so the bug submitter can leave this at the default value. A number of
+ <a href="bugpriorities.html">guidelines</a> and some individual judgment are involved in setting the priority. If you know the
+ bug is a regression, ie. something is wrong which wasn't wrong in previous versions of WebKit, you can set this to P1.</p>
+ </li>
- <li><b>Summary</b>
- <p>A good summary explains the problem in clear and specific terms, but is often concise enough to fit within the default summary space in Bugzilla.
+ <li>
+ <b>Severity</b>
+ <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 an
+ <tt>enhancement</tt>, it's helpful to specify that value. A QA person or developer will set this to some other value if
+ appropriate.</p>
+ </li>
+
+ <li><b>URL</b>
+ <p>Fill in this field with the URL of a page that shows the bug, when possible. If you have created a <a href="reduction.html">test case reduction</a> for the bug,
+ please add it to the bug report as an attachment rather than putting it on a web server and listing its URL here. Doing so
+ makes it easier to work on the bug, and can be a first step towards checking in the test case along with the bug fix.</p>
+ </li>
+
+ <li><b>Summary</b>
+ <p>A good summary explains the problem in clear and specific terms, but is often concise enough to fit within the default summary space in Bugzilla.
One should be able to tell exactly what a bug is about just by reading the summary.</p>
-
- Tips for a good summary:
- <li>include the domain of the page that shows the bug (especially if it's an important site)
- <li>if the bug is a crash, note this and note whether or not the crash is reproducible
- <li>if you have tested and verified that this is a regression from a previous version of WebKit, prepend "REGRESSION" to the summary
- <li>if you know between which versions of WebKit the regression occurred, add this to the summary after REGRESSION (i.e., "REGRESSION (125-408)")
- </ul>
- </li><br>
-
- <li><b>Description</b>
-
<p>In this field, write a more detailed explanation of the problem.</p>
-
- Tips for Descriptions:
-
<ul> <li> Please do not include more than one bug in one bug report. </li>
- <li> If you can only reproduce the problem on a version of WebKit that you built yourself, include the date that you checked out the source code. </li>
- <li> If there is no simple URL to a page that shows the bug (for instance, you have to click through multiple pages for the bug to occur), then describe the exact navigation required to reach the page where the bug occurs. Don't just say "go to the forums"; use detailed steps. </li>
- <li> Look at Console and include any messages that might be relevant in the bug. </li>
- <li> Include the backtrace if you get a crash, if possible. File the bug first and then add the backtrace as an attachment.</li>
- <li> Include a screenshot for visual bugs. If the problem isn't very obvious, include a single screenshot which shows both correct and
+
+ Tips for a good summary:
+ <ul>
+ <li>include the domain of the page that shows the bug (especially if it's an important site)
+ <li>if the bug is a crash, note this and note whether or not the crash is reproducible
+ <li>if you have tested and verified that this is a regression from a previous version of WebKit, prepend "REGRESSION" to the summary
+ <li>if you know between which versions of WebKit the regression occurred, add this to the summary after REGRESSION (i.e., "REGRESSION (125-408)")
+ </ul>
+ </li>
+
+ <li><b>Description</b>
+ <p>In this field, write a more detailed explanation of the problem.</p>
+
+ Tips for Descriptions:
+ <ul> <li> Please do not include more than one bug in one bug report. </li>
+ <li> If you can only reproduce the problem on a version of WebKit that you built yourself, include the date that you checked out the source code. </li>
+ <li> If there is no simple URL to a page that shows the bug (for instance, you have to click through multiple pages for the bug to occur), then describe the exact navigation required to reach the page where the bug occurs. Don't just say "go to the forums"; use detailed steps. </li>
+ <li> Look at Console and include any messages that might be relevant in the bug. </li>
+ <li> Include the backtrace if you get a crash, if possible. File the bug first and then add the backtrace as an attachment.</li>
+ <li> Include a screenshot for visual bugs. If the problem isn't very obvious, include a single screenshot which shows both correct and
incorrect renderings, for example Safari and another browser such as Firefox or Mac IE. Use Grab.app or cmd-shift-4 and grab as small an area as possible that demonstrates the problem. Then attach the screenshot to the bug. </li>
- <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 keys, arrow buttons, scroll thumb, clicking above or below the thumb, scroll-wheel mouse, etc. </li>
- </ul><br>
-
- <li>
- <b>Depends on</b>
-
<p>If the fix for this bug depends on another bug fix, put the other bug's number here. Otherwise, leave it empty.</p>
- </li>
+ <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 keys, arrow buttons, scroll thumb, clicking above or below the thumb, scroll-wheel mouse, etc. </li>
+ </ul><br>
+
+ <li>
+ <b>Depends on</b>
+ <p>If the fix for this bug depends on another bug fix, put the other bug's number here. Otherwise, leave it empty.</p>
+ </li>
- <li>
- <b>Blocks</b>
-
<p>If this bug blocks another bug from being fixed, put the other bug's number here. Otherwise, leave it empty.</p>
- </li>
+ <li>
+ <b>Blocks</b>
+ <p>If this bug blocks another bug from being fixed, put the other bug's number here. Otherwise, leave it empty.</p>
+ </li>
</ol>
-<?php
- include("../footer.inc");
-?>
\ No newline at end of file
+<?php include("../footer.inc"); ?>
<?php
- $title = "Test Case Reduction";
- include("../header.inc");
+ $title = "Test Case Reduction";
+ include("../header.inc");
?>
<h2>Test Case Reduction</h2>
<li>Is there a form button that fails to work?</li>
<li>Is there a portion of the page missing or misaligned?</li>
</ul>
- </p>
+
<p>
After you have made this determination, you need to create a local copy
of the page created from the page source window. After saving this
the component, read about how to get them in this <a href="bugzilla.html">document
about Bugzilla</a>.
</p>
-<?php
- include("../footer.inc");
-?>
\ No newline at end of file
+<?php include("../footer.inc"); ?>
<?php
- $title = "Reporting Bugs";
- include("../header.inc");
+ $title = "Reporting Bugs";
+ include("../header.inc");
?>
<h2>Reporting Bugs</h2>
if (webkit_version.major < 100) {
// Mac OS X 10.2
- display('10point2', 'block');
+ display('using_10point2', 'block');
} else if (webkit_version.major >= 100 && webkit_version.major < 400) {
// Mac OS X 10.3
- display('10point3', 'block');
+ display('using_10point3', 'block');
if (webkit_version.major < 312)
// Mac OS X 10.3.8 or lower
} else {
// Mac OS X 10.4
- display('10point4', 'block');
+ display('using_10point4', 'block');
if (webkit_version.major == 412 && webkit_version.is_nightly)
// Using an old nightly
// Using a recent nightly, not sure which
display('mightneednewnightly', 'block');
- else if (webkit_version.major < 417)
- // 10.4.3 or lower
- display('updateto10_4_5', 'block');
+ else if (webkit_version.major < 418)
+ // 10.4.6 or lower
+ display('updateto10_4_7', 'block');
else if (is_safari)
- // 10.4.4 or 10.4.5
- display('10_4_5_safari', 'block');
+ // 10.4.7
+ display('using_10_4_7_safari', 'block');
else if (is_shiira)
- // 10.4.4 or 10.4.5
- display('10_4_5_shiira', 'block');
+ // 10.4.7
+ display('using_10_4_7_shiira', 'block');
}
}
Mac OS X 10.4, you could also <a href="http://nightly.webkit.org">download the latest nightly</a> build to be sure you
have the latest version. If you've done this and you still experience the bug, go ahead to the next step.
</div>
-<div id="10point2" style="display: none;">
+<div id="using_10point2" style="display: none;">
We're sorry, we no longer accept bug reports about Safari under Mac OS X 10.2. To many bugs have been fixed since then. We advise
you to upgrade to Mac OS X 10.4.
</div>
-<div id="10point3" style="display: none;">
+<div id="using_10point3" style="display: none;">
<div id="updateto10_3_9" style="display: none;">
You are using Mac OS X 10.3.8 or lower, please before filing any bugs, upgrade to Mac OS X 10.3.9.
</div>
<div id="best10_3_9_safari">
You are using Mac OS X 10.3.9, and the latest version of Safari, go ahead and file your bug!
</div>
- <div id="best10_3_9_safari">
+ <div id="best10_3_9_shiira">
You are using Shiira on Mac OS X 10.3.9, go ahead and file your bug!
</div>
</div>
-<div id="10point4" style="display: none;">
+<div id="using_10point4" style="display: none;">
<div id="neednewnightly" style="display: none;">
You are already using a nightly build, which is very good! A large number of bugs has been fixed since you downloaded
this nightly build though, so please <a href="http://nightly.webkit.org/">get the latest nightly</a>.
You are already using a nightly build, which is very good! Unfortunately, we can't detect when you downloaded it, but
if that was more then a few days ago, please <a href="http://nightly.webkit.org/">get the latest nightly</a>.
</div>
- <div id="updateto10_4_5" style="display: none;">
- You are using Mac OS X 10.4.3 or lower, please before filing any bugs, do either of the following:
+ <div id="updateto10_4_7" style="display: none;">
+ You are using Mac OS X 10.4.6 or lower, please before filing any bugs, do either of the following:
<ul>
- <li>Upgrade to Mac OS X 10.4.5, or:</li>
+ <li>Upgrade to Mac OS X 10.4.7, or:</li>
<li><a href="http://nightly.webkit.org">Download the latest nightly</a>.</li>
</ul>
</div>
- <div id="10_4_5_safari" style="display: none;">
- You are using Safari on Mac OS X 10.4.
4 or 10.4.5, go ahead and file your bug, or if you want to <a href="http://nightly.webkit.org">
+ <div id="using_10_4_7_safari" style="display: none;">
+ You are using Safari on Mac OS X 10.4.
7, go ahead and file your bug, or if you want to <a href="http://nightly.webkit.org">
download the latest nightly</a> and see if your bug is already fixed.
</div>
- <div id="10_4_5_shiira" style="display: none;">
- You are using Shiira on Mac OS X 10.4.4 or 10.4.5, go ahead and file your bug.
+ <div id="using_10_4_7_shiira" style="display: none;">
+ You are using Shiira on Mac OS X 10.4.7, go ahead and file your bug.
</div>
</div>
</li>
For WebKit bugs that contain confidential information, please use
<a href="http://bugreporter.apple.com">http://bugreporter.apple.com/</a>.
</div>
-</div>
<script type="text/javascript">get_version();</script>
<?php
- $title = "Regression Testing";
- include("../header.inc");
+ $title = "Regression Testing";
+ include("../header.inc");
?>
<h2>Regression Testing</h2>
In addition, the JavaScript tests cover parsing, lexical conventions,
expressions, statements, type conversion, and exception handling.
- </p>
<h3>How to run the tests</h3>
-<pExecute the "run-javascriptcore-tests" script:</p>
+<p>Execute the "run-javascriptcore-tests" script:</p>
<p class="code">WebKitTools/Scripts/run-javascriptcore-tests</p>
<p>The script will run all the tests and summarize how the results differ from what is currently expected.</p>
<p>It's not the end of the world. Go back and fix your bug and re-run <tt>run-javascriptcore-tests</tt> as many times as necessary.</p>
<?php
- include("../footer.inc");
+ include("../footer.inc");
?>
git://git.webkit.org / WebKit-https.git / commitdiff