Page 1 of 1

Comparing the eValid PageMap displays to what Chrome shows

PostPosted: Mon Jun 21, 2021 12:03 pm
by ChuckP
Good afternoon.

Why does the PageMap feature display some compact details comapred to the explanation you get from the Chrome browser?

Thanks

Re: Comparing the eValid PageMap displays to what Chrome sho

PostPosted: Tue Jun 22, 2021 8:30 am
by eValid
ChuckP wrote:Good afternoon.

Why does the PageMap feature display some compact details comapred to the explanation you get from the Chrome browser?

Thanks


You're right ChuckP.

Modern browser do have a great deal of information on their "show me the DOM" display.

On Chrome, just type Ctrl-Shift-C and see what happens.

eValid's PageMap feature simplifies things as much as possible but still has all the needed information present.

See this manual page:

http://e-valid.com/Products/Documentati ... usage.html

The view take in developing the eValid PageMap display was to provide the user -- a website tester, remember, not necessarliy a website deigner or developer -- what was needed for that role.

Consequently, what is left out is any information that affects format, typefont, display processing, "style sheet" details, internals of JavaScript.

What is included is the type of the element and the details you might need to implement an eValid command that pivots on or relies upon data in some particular DOM element.

So, no more information in the PageMap than is needed to support an eValid command the uses DOM details.

We hope this answers your question.

If you like more details, please contact us.


-- eValid Support