eValid's Pagemap vs Chrome's inspect element

Discussion of the technology underlying the eValid solution.

eValid's Pagemap vs Chrome's inspect element

Postby JerryM » Fri Jan 17, 2014 11:32 am

Hi,

eValid's has a DOM viewing device, I think you call it PageMap.
How does that differ from Chrome's "inspect element"? In what ways and why
is PageMap better?

Thanks
JerryM
 
Posts: 1
Joined: Thu Jan 16, 2014 12:05 pm

Re: eValid's Pagemap vs Chrome's inspect element

Postby eValid » Mon Jan 20, 2014 11:06 am

JerryM wrote:Hi,

eValid's has a DOM viewing device, I think you call it PageMap.
How does that differ from Chrome's "inspect element"? In what ways and why
is PageMap better?

Thanks


Hey JerryM. Welcome and thanks for posting on the forum.

The eValid PageMap directly access the content of the DOM
of the current page, as do the "inspect element" features
of several modern browsers.

The PageMap display is optimized for use in testing web applications
in that it focuses on what is present that is important, and
does not give you unnecessary detail.

Remember, eValid's goal is to make it possible to test (or
monitor) an application, not to build it. Excessive detail
would get in the way.

eValid's PageMap shows the hierarchical context of an element
in the HTML, so you can see what is where. And, the interaction
between the PabeMap and the page you are viewing is bi-directional
and based on a single command (right-click, when PageMap is active).

The PageMap is simpler, easier to use, better focused to the needs.

--eValid Support
eValid
 
Posts: 2392
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to Technology

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons