I wonder if we could deal with animating parts of the browser (like find window, bookmark bar, etc) just in one way: wait for a specified number of animations to finish. The alternative is to add notification for each thing: find window stopped animating, bookmark bar stopped animating, and so on. We have separate implementations of these for each GUI toolkit, so that seems repetitive and error-prone. Just putting a notification in Animation seems to be much simpler. What do you think? Are there any dangerous drawbacks of that approach?
I'm going to use that in ui_tests and automated_ui_tests, which are supposed to be end-to-end and as realistic as possible. Disabling the animation is not an option in this case. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
