Changes between Version 20 and Version 21 of QtWebKitBugs


Ignore:
Timestamp:
Mar 23, 2010, 7:19:40 AM (15 years ago)
Author:
jocelyn.turcotte@nokia.com
Comment:

minor

Legend:

Unmodified
Added
Removed
Modified

  • QtWebKitBugs

    v20 v21  
    66Bugs are reported together with other ports on WebKit Bugzilla.[[BR]]Please create your bug report using the following link to make sure that it appears in the appropriate filters:
    77 * Template shortcut: [http://webkit.org/new-qtwebkit-bug]
    8 The most important is to set the 'Qt' keyword on the bug report. Look at the [#Bugfieldsdescription bug fields description] for more information.
    98
    109== Properties of a good bug report ==
    … …  
    1413Serious bug reporters might also want to have a look at the [http://webkit.org/quality/reporting.html steps to report a bug] and the [http://webkit.org/quality/bugwriting.html reporting guidelines] applying to the whole WebKit project.
    1514
    16 === Attached test case ===
     15=== Contains an attached test case ===
    1716Test cases are favored to external web site links since they are not vulnerable to external updates.
    1817 * For a page rendering bug, a minimal HTML file is usualy efficient.
    19  * For bugs of more platform-related features, a zip file containing a C++ source file and a .pro file compilable by typing {{{qmake && make}}} might be required
     18 * For bugs of more platform-related features, a zip file containing a C++ source file and a .pro file compilable by typing {{{qmake && make}}} might be required.
    2019
    21 === Steps to reproduce a crash ===
    22 Because crashes are often caused by complex conditions, it is usually difficult to provide a test case reproducing them. In that case:
     20=== Lists the steps to reproduce a crash ===
     21Because crashes are often caused by complex conditions, it might be difficult to provide a test case to attach reproducing them 100% of the time. In that case:
    2322 * Try to reproduce the crash more than once. Describe as best as you can the steps required to reproduce it.
    2423 * If your can run a debug build of !QtWebKit and attach a stack trace of the crash to the bug report, this would further help the investigation.[[BR]]'''Note: ''' The debug builds of Qt do not include debugging information for !QtWebKit by default to prevent linking problems. A debug build of WebKit trunk or a nightly package of !QtWebKit is currently required to extract reliable stack traces.