Canvas doesn't work properly

[macrojd]

Hi guys. I tried to report a bug but I'm not sure if I did it right or not because I can't find my message anymore, so I explain whats going on here.

The Canvas API doesn't draw paths properly in Chrome 23 and Chrome dev 25 for Mac. I have a Mac Mini with Snow Leopard 10.6.8

Here is an example: www.minkbooks.com/test/test.html

The code draws a line and a circle when the button is clicked. Sometimes only the line is drawn and sometimes nothing. But if you invert the code and draw the arc fist, then everything is drawn (unless you add something else later and things get messy again).

I couldn't try on Windows, but the code works as expected on Firefox.

JD

www.jdgauchat.com

[Jared Williams]

Works fine on Windows 7 for me using Chrome 23. Just fyi.

[macrojd]

Hi Jared. Yes, yesterday I tried on Windows 7 and it worked.  So, it's only on Macs in both the 23 and Chrome dev. Maybe it has to do with the video card of my old Mac Mini,  I don't  know, but there is an ugly  bug there :-)

Also, Peter sent me a message commenting that it worked for him in Chrome 24. I'm not sure how to get the 24 version because the stable version is 23 and the dev version is 25 already. For 23 and 25 the example doesn't work. He propose to add a moveTo method but that's not the problem. There is a bug there that makes the drawing unstable, some times works in part and some times doesn't work at all. And it is not just with that example, I can't work with Canvas at all in Chrome.

I think the reason why it worked for Peter and not for me is not only the Chrome's version but our different video cards. But I'm not sure about that. Anyways, there is a bug that someone has to pay attention to. 

Thanks

JD

[PhistucK]

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page. If you do file a new issue, make sure you include a reduced test case (an HTML with a few lines of code/operations as possible), screenshots and data from about:gpu.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

Thank you.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-html5/-/zC62BUCtz74J.

To post to this group, send email to chromiu...@chromium.org.
To unsubscribe from this group, send email to chromium-html...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-html5/?hl=en.

[Jared Williams]

Have you tried testing it by running chrome with the --disable-accelerated-2d-canvas flag at all? It's worth a shot. There was a bug with that before I know that had to do with drawing paths and arcs. It's likely not to blame here just a thought.

http://code.google.com/p/chromium/issues/detail?id=71644

On Friday, December 21, 2012 5:16:12 PM UTC-5, macrojd wrote:

[macrojd]

Hi guys. Thanks for the information. I'll see what happen with the flag and then report the bug as soon as I get back to the office.

I'll let you know if I have news on this issue.

JD

www.jdgauchat.com