Changes between Version 6 and Version 7 of QtWebKitBugs


Ignore:
Timestamp:
Mar 4, 2010 2:44:20 PM (11 years ago)
Author:
jocelyn.turcotte@nokia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitBugs

    v6 v7  
    44
    55== Where to report bugs ==
    6 Bugs are reported together with other ports on WebKit Bugzilla. Please use the template shortcut [http://webkit.org/new-qtwebkit-bug] to make sure your bug report appear in the appropriate filters. For more detailed information see the [#Bugfieldsdescription bug fields description].
     6Bugs are reported together with other ports on WebKit Bugzilla. Please use the template shortcut [http://webkit.org/new-qtwebkit-bug] to make sure that your bug report appear in the appropriate filters. For more detailed information see the [#Bugfieldsdescription bug fields description].
    77
    88== Properties of a good bug report ==
     
    1717 * 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
    1818
    19 === Extra information for crashes ===
    20 If you unfortunately encounter a crash using !QtWebKit, the most important step to allow it being fixed is to reproduce it.
     19=== Steps to reproduce a crash ===
     20Because crashes are often caused by complex conditions, it is usually difficult to provide a test case reproducing them. In that case:
    2121 * Try to reproduce the crash more than once. Describe as best as you can the steps required to reproduce it.
    2222 * 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 from trunk or a nightly package of !QtWebKit is currently required to extract reliable stack traces.