Loading ...
Sorry, an error occurred while loading the content.

Re: [svg-developers] Chrome freeze bug

Expand Messages
  • Raks A
    And the biggest problem is that the behaviour is just unpredictable Just yesterday I filed one bug 88224 https://bugs.webkit.org/show_bug.cgi?id=88224 Anyone
    Message 1 of 4 , Jun 4, 2012
    • 0 Attachment
      And the biggest problem is that the behaviour is just unpredictable
      Just yesterday I filed one bug 88224
      https://bugs.webkit.org/show_bug.cgi?id=88224

      Anyone in this list working on Webkit ? Is there a problem in the
      implementation of the timing model in Webkit ?
      Freeze is such a basic need

      - Rakesh

      On Tue, Jun 5, 2012 at 12:18 AM, Bob Hopgood <frahopgood@...> wrote:

      > **
      >
      >
      > Chrome has had freeze bugs for at least the last six months. I have put in
      > several bug reports but nothing gets done.
      >
      > Here is another example:
      >
      > <svg width="1024" height="768" xmlns:xlink="http://www.w3.org/1999/xlink"
      > xmlns="http://www.w3.org/2000/svg">
      > <style type="text/css">
      > .w18c1 {fill:red;stroke:cyan}
      > .w18c2 {fill:blue;stroke:cyan}
      > .w18c3 {fill:green;stroke:cyan}
      >
      > </style>
      > <g transform="translate(30,40)">
      > <rect id="r1" class="w18c1" x="0" y="0" width="100" height="40" />
      > <rect id="r2" class="w18c2" x="0" y="50" width="100" height="40" />
      > <rect id="r3" class="w18c3" x="0" y="100" width="100" height="40" />
      > <rect id="r4" class="w18c1" x="0" y="150" width="100" height="40" />
      > <rect id="r5" class="w18c2" x="0" y="200" width="100" height="40" />
      > <rect id="r6" class="w18c3" x="0" y="250" width="100" height="40" />
      > <rect id="r7" class="w18c1" x="0" y="300" width="100" height="40" />
      > <rect id="r8" class="w18c2" x="0" y="350" width="100" height="40" />
      > <rect id="r9" class="w18c3" x="0" y="400" width="100" height="40" />
      > </g>
      > <animate begin="start.begin+0.2s" dur="2s" attributeName="x" fill="freeze"
      > xlink:href="#r1" values="0;300"/>
      > <animate begin="start.begin+0.3s" dur="1.9s" attributeName="x"
      > fill="freeze" xlink:href="#r2" values="0;300"/>
      > <animate begin="start.begin+0.4s" dur="1.8s" attributeName="x"
      > fill="freeze" xlink:href="#r3" values="0;300"/>
      > <animate begin="start.begin+0.4s" dur="1.81s" attributeName="x"
      > fill="freeze" xlink:href="#r4" values="0;300"/>
      > <animate begin="start.begin+0.4s" dur="1.82s" attributeName="x"
      > fill="freeze" xlink:href="#r5" values="0;300"/>
      > <animate begin="start.begin+0.2s" dur="2s" attributeName="x" fill="freeze"
      > xlink:href="#r6" values="0;300"/>
      > <animate begin="start.begin+0.3s" dur="1.9s" attributeName="x"
      > fill="freeze" xlink:href="#r7" values="0;300"/>
      > <animate begin="start.begin+0.4s" dur="1.8s" attributeName="x"
      > fill="freeze" xlink:href="#r8" values="0;300"/>
      > <animate begin="start.begin+0.4s" dur="1.81s" attributeName="x"
      > fill="freeze" xlink:href="#r9" values="0;300"/>
      >
      > <g id="startbutton">
      > <path id="start_button" style="fill:red;" d="M1024,748l-40,-20l0,40z" >
      > <animateColor id='start' xlink:href="#start_button" attributeType="CSS"
      > attributeName="fill" values="red;pink" begin="start_button.click"
      > fill="freeze" dur="0.01s" />
      > </path>
      > </g>
      >
      > </svg>
      >
      > The rectangles should all move right to left and stay there. A random
      > number return to their original positions. It varies by run and machine
      > which ones !
      >
      > [Non-text portions of this message have been removed]
      >
      >
      >


      [Non-text portions of this message have been removed]
    • jamesd
      Bob Hopgood wrote: Chrome has had freeze bugs for at least the last six months. I have put in several bug reports but nothing gets done. Welcome to reality.
      Message 2 of 4 , Jun 5, 2012
      • 0 Attachment
        Bob Hopgood wrote:

        Chrome has had freeze bugs for at least the last six months. I have put in several bug reports but nothing gets done.

        Welcome to reality. Webkit is trying hard to be the IE6 of the 21st century. I too have had issues with Webkit and gave up trying to get them resolved.

        James
      • Raks A
        I filed two bugs one for freeze and another one for something else. There was no response for the freeze bug but I have been getting responses for the other
        Message 3 of 4 , Jun 6, 2012
        • 0 Attachment
          I filed two bugs one for freeze and another one for something else.
          There was no response for the freeze bug but I have been getting responses
          for the other bug

          There is something about freeze because of which people do not want to even
          attend to the bug and ithe freeze bugs has been there for atleast 2 years
          now

          - Raks

          On Wed, Jun 6, 2012 at 7:04 AM, jamesd <jcdeering1@...> wrote:

          > **
          >
          >
          > Bob Hopgood wrote:
          >
          > Chrome has had freeze bugs for at least the last six months. I have put in
          > several bug reports but nothing gets done.
          >
          > Welcome to reality. Webkit is trying hard to be the IE6 of the 21st
          > century. I too have had issues with Webkit and gave up trying to get them
          > resolved.
          >
          > James
          >
          >
          >


          [Non-text portions of this message have been removed]
        Your message has been successfully submitted and would be delivered to recipients shortly.