-
-
Save nitriques/5541938 to your computer and use it in GitHub Desktop.
| Starting from version 26, Chrome as been making angry a lot... | |
| Chrome | |
| 1. CSS3 animation are not as fluid as they used to be. IE10 is not more fluid than Chrome! | |
| 2. CSS3 gradiants are making the render glitchy: sometimes going under 5 FPS. | |
| 3. It seems like there is a problem with images cache: On the canvas, if you do not paint a image for one frame, then its cache gets deleted, which cause a performance problem (renders usually took 1 to 2 ms, but it jumps to 200 ms sometimes, and there's a blank in the devtools timeline. In the profile view, we only get (system) as feedback) | |
| 4. The video API throws errors when everything should be working fine. It plays the video only 50% of the time (even though it's the same video all the times) | |
| 5. Decoding images (especially base64 ones) is sometimes really slow, especially if the image is going in and out of the viewport (again, a image cache problem) ?? | |
| DevTools | |
| 1. Breakpoints moves from one line to another between refresh, even though the code does not change. | |
| 2. Removing a break point by clicking on it does not work most of the time (the UI says that the break point is not there, but the debugger stills stop on it. | |
| 3. Using only one var block seems to upset the debugger too... But this is a js best pratice... | |
| 4. Editing the CSS in the devtools is a pain. I often loose what I type in... | |
| 5. Saving local modifications (from js, css) works 50%, so we can't use it... | |
| BTW, All those bugs are still present in the Canary version (which I use daily) | |
| I must say that I am a bit afraid, since Webkit is the most used engine on the web and since Opera made the decision to use it now. I don't want to develop in Firefox, but right now, I do not have the choice. | |
| I will continue to edit this when I found anything else I hate, or when thing get fixed. |
paulirish
commented
May 8, 2013
H.264 support in
devtools #3. any debugger will get pretty unhappy with single var declaration. JS best practice has shifted to multiple var, from what i've seen.
devtools #4 i'd like to understand this flow better. what are you typing and what keys do you hit?
devtools #5. this is about to be revolutionized with workspaces.
for chrome issues 1-5, i think filing them at crbug.com would be ideal. i can cc in the experts for each. and test cases for any of these are SUPER HELPFUL. :)
devtools #1-2 i'd love bugs filed at crbug.com for them. can you add those?
Hi @paulirish,
Sorry I missed those posts.
JS best practice has shifted to multiple var, from what i've seen.
From my experience, the code will get more compressed (at least with uglify.js) if you code with a single var. I would really apreciate to have more support on that, since I sometimes have to debug compressed code.
devtools #4 i'd like to understand this flow better. what are you typing and what keys do you hit?
Let's say a double click in order to add a style property in the right pane. Type in "posision: relative" and than ENTER. ENTER is the problem, it looses everything. You have to "click elsewhere" in order to get it right. The same is true when you are adding an attribute to a DOM Element. But I use ENTER to confirm my selection since 1995...
devtools #5. this is about to be revolutionized with workspaces.
Can't wait to see that. Is it already in Canary ?
I am, most of the time, shy about opening new crbugs... But since you told me so, I will reference this gist :) I may also add a screenr capture. Thanks for your time, I really apreciate it.
devtools #3. any debugger will get pretty unhappy with single var declaration.
I just tested firebug, and it handles single var nicely: the comma is treated like a semi-colon and not a single line, as Chrome's devtools does.