[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 278618] Obviously the canvas 2D rendering context method
From:       Gérard Talbot  <browserbugs () gtalbot ! org>
Date:       2011-07-31 20:50:47
Message-ID: E1QncyF-0006ch-4f () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=278618





--- Comment #6 from Gérard Talbot <browserbugs gtalbot org>  2011-07-31 20:50:46 ---
Paul,

1-

> if you visit my - simple - page

> http://www.ps-take2.de/index.html

Your webpage is not a simple page and is not a reduced testcase.

   <link rel = "stylesheet" type = "text/css" href = "styles/site.css" />
   <link rel = "stylesheet" type = "text/css" href = "styles/index.css" />

   <script type = "text/javascript" src = "scripts/globals.js" ></script>
   <script type = "text/javascript" src = "scripts/imagesIndex.js" ></script>
   <script type = "text/javascript" src = "scripts/pageSetup.js" ></script>
   <script type = "text/javascript" src = "scripts/fnctIndex.js" ></script>
   <script type = "text/javascript" src = "scripts/initIndex.js" ></script>

and you're even mentioning a fetched xml-file on top of all this.


2- 
By giving clear and explicit actual and expected results, QA people and
developers would easily and quickly see and confirm if the bug you see still
exist or not. When creating a bug report, you should try to be more formal and
terse.
I asked you what were the texts?
I told you that when visiting with Firefox 5.0, I saw no newsticker.

You changed your code since yesterday because now I see what appears to be a
large text area after clicking the Chinese Symbol. And now I see a newsticker
in Firefox 5.0, Opera 11.50 and Chrome 12.0.742.124.

3- 
> I reported a single bug -- and mentioned (in my reply to Mr.
> Koller) a second one.

You may have reported a single bug but you are mentioning many other issues,
errors and many other details which may not be relevant to your bug report,
which have nothing to do with the fillText() and <canvas> support. 
By increasing verbose, you are not helping: people (developers, QA people) have
to read all this, you know, in order to understand and reproduce the bug and
then they have to examine all of the involved code (and 8 linked files) at
http://www.ps-take2.de/index.html .

4-
> Having a simple test case would be fine. I chose not to 
> construct one

I quoted a relevant chunk of Investigating Konqueror Bugs (
http://www.konqueror.org/investigatebug/ ) in this bug report.

5- 
> look forward getting a fixed version of Konqueror.

To be sure you're not filing a bug report on a bug already fixed, it's
preferable, you see, to try the testcase with the latest stable version. In
that sense, testing with Konqueror 4.7.0 instead of 4.6.0 was and is
recommendable.

Note that your own code forks URL location based on user agent string:

http://www.ps-take2.de/scripts/initIndex.js

function initPage ()
{
   var s = navigator.userAgent; // "*** MSIE 8.0; ***"; // navigator.userAgent;

   var knqPtrn = /Konqueror\x2f\d\x2e\d/;
   var konqueror = s.match (knqPtrn);
   if (konqueror < "Konqueror/4.6") // has to be "<" !!! 31.07.2011
   {  //Obviously Konqueror/4.4 doesn't know HTML 5-Tags either
      document.location.href = "pagesIE/index.html"
   }


Paul,

I have provided a link to a 32 lines testcase for your bug report. It could be
furthermore reduced to only test fillText().

If you want a newsticker to work, to display accordingly within Konqueror 4.5+,
then you can adapt the code of
https://developer.mozilla.org/samples/StockTicker/ 
into your webpage. I know you can.

Gérard

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]