Issue with "Objects" whit chrome 34
On April 8 2014 Google chrome was updated to: 34.0.1847.116 m Since then im having issue with recording/executing test with TC. The object in the web page can not be reconized. This makes th...
Forum Discussion
Ryan (and others),
> [...] it's a simple version check preventing forward compatibility).
First of all, I agree with you (http://smartbear.com/forums/f75/t88487/addons-for-chrome/#88498) that there are customers updating constantly. But on the other hand, I am sure that they *must* understand that these updates their sole risk. I am pretty sure that for the commercial software no one legal department will include in the EULA the statement that the given web application supports all browsers (or even all Chrome versions starting from, say, version 29).
For non-commercial web applications there may be some business considerations to support as much latest browsers as possible, but I still think that this is Google's fault that almost all versions of their browser is internally incompatible one with another.
Definitely, it would be nice to hear from SmartBear about the real reason of this problem, but what I can say is that Chrome patch for version 30 (the latest one for TC 9.x) works fine for me with Chrome 31. This makes me think that the problem is not in simple version check (otherwise, I am sure that TC issued some info message), but in the fact that Chrome constantly changes something internally. As I said, for me this looks like Chrome's design flaw as it breaks internal compatibility. It's a good tradition to blame Microsoft, but what if every their update broke functionality of, say, all third-party debuggers (like Java, Borland, etc.)?
Just my current opinion...
> [...] it's a simple version check preventing forward compatibility).
First of all, I agree with you (http://smartbear.com/forums/f75/t88487/addons-for-chrome/#88498) that there are customers updating constantly. But on the other hand, I am sure that they *must* understand that these updates their sole risk. I am pretty sure that for the commercial software no one legal department will include in the EULA the statement that the given web application supports all browsers (or even all Chrome versions starting from, say, version 29).
For non-commercial web applications there may be some business considerations to support as much latest browsers as possible, but I still think that this is Google's fault that almost all versions of their browser is internally incompatible one with another.
Definitely, it would be nice to hear from SmartBear about the real reason of this problem, but what I can say is that Chrome patch for version 30 (the latest one for TC 9.x) works fine for me with Chrome 31. This makes me think that the problem is not in simple version check (otherwise, I am sure that TC issued some info message), but in the fact that Chrome constantly changes something internally. As I said, for me this looks like Chrome's design flaw as it breaks internal compatibility. It's a good tradition to blame Microsoft, but what if every their update broke functionality of, say, all third-party debuggers (like Java, Borland, etc.)?
Just my current opinion...