Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 07 Aug 2013 06:56 by ADMIN
ADMIN
Velin Koychev
Created on: 04 Jul 2013 11:19
Type: Bug Report
1
Wrong recognintion of grid elements by telerik DOM explorer
The issue is arising when we try to highlight a cell in a table by using the Telerik Dom Explorer. On selecting a <tr> element, it highlights the correct row, but when we select the <td>'s under the <tr>, it marks wrong elements on the page.
Steps to reproduce are available in the internal description.
7 comments
ADMIN
Konstantin Petkov
Posted on: 07 Aug 2013 06:55 
It seems the issue is obsolete with the latest application changes.
ADMIN
Konstantin Petkov
Posted on: 16 Jul 2013 07:38 
Hello,

OK, so it seems the support ticket has been reopened, however we are unable to investigate this particular problem yet due to a bug in the DOM Explorer in the latest 2013.1 you can find that explained here:
http://feedback.telerik.com/Project/117/Feedback/Details/53366-dom-explorer-may-crash-ie-with-complex-applications

We highly recommend using the Firefox/Chrome DOM explorer instead where:
- we get no crash browser your application DOM
- the highlighting works just fine.

It will be great to get your feedback on the new recording experience in Chrome/Firefox!

Also as soon as the IE DOM crash problem is solved we will look again into this specific issue.

Thanks!
ADMIN
Konstantin Petkov
Posted on: 12 Jul 2013 05:36 
Hi David,

I'm glad to find this one is gone along with the other issue after fixing the invalid HTML!

We hear your requests! I really hope we can identify mailformed HTML and warn the user in advance - that will be great to have! I also agree those kind of issues are hard to identify so we definitely need that ability built-in to the product.

Thank you!
David
Posted on: 11 Jul 2013 18:02 
The system is back up and running and the application is reinstalled on top.  I took a quick look and was NOT able to reproduce the issue.

See Ticket #712930, which has similar symptoms.

The system was updated with a later build - a build which had a fix for some malformed html on our end for #712930, it seemed to also fix the issue that was reported here.  (double check me, but I was not able to reproduce)

The problem here is that the malformed HTML works fine in the browser - certainly a bug on our part, but there are no symptoms that you can point to as an end user (at least not in the place where the test fails).  Since there are no symptoms in our application it makes this look like a Telerik bug.  We have hit this type of situation several times and in the end it has always been malformed HTML on our side, but the issues are *very* difficult to nail down, there don't seem to be any good tools on the market.

What I have been pushing for is a way for Telerik to help us identify the malformed HTML that is tripping up the test - this would turn a really negative situation into a huge positive for Telerik - "Telerik helped me fix my junk html".  Even something simple like a Fiddler plugin that can highlight malformed HTML would be awesome.
David
Posted on: 11 Jul 2013 13:40 
Sorry about that - the system was refreshed (a dev system) and I don't think the steps to reproduce are going to match.  System should be back online now and I'll have the originators reinstall the application then respond here...
ADMIN
Konstantin Petkov
Posted on: 11 Jul 2013 13:09 
Hi David,

We'd like to find out but we cannot access the provided URL internally. Can you please take a look?

Thanks!
David
Posted on: 04 Jul 2013 13:09 
This seems pretty serious - is there no work around?
Create an account Log In
View
Type
Status