Functions and problems of the DOM Explorer plug-in

I don't know when to start, Microsoft is always slower than others, and often needs others to push him. From Google's search to MSN's search, from Google's map to MSN's map, and then from Firefox to IE7's "forced" startup; in fact, for Microsoft, it is not a one-stop task, but Microsoft is just a little slower than others. This is not the case. When we all say that Firefox can easily view the Dom on the web page, Microsoft immediately packed up a DOM Explorer for us.

Check the DOM structure of the web page in Firefox. We use a plug-in named Dom inspector, such:

The Internet Explorer plug-in that Microsoft developed for us is called Dom explorer. Its running effect is as follows (pinned view ):

Although Microsoft was a slow player, I had to admit that Dom explorer was actually better than dom inspector. There is no essential difference between the two plug-ins in terms of main functions. There are only differences in details, but Dom Explorer does not provide the JavaScript Object browsing function supported by Dom inspector.

Dom explorer provides the following functions:
Using e and modify the Document Object Model (DOM) of a Web page.
Locate and select specific elements on a web page through a variety of techniques.
Selectively disable Internet Explorer settings.
View HTML object class names, ID's, and details such as link paths, Tab index values, and access keys.
Outline tables, table cells, images, or selected tags.
Validate HTML, CSS, Wai, and RSS web feed links.
Display image dimensions, file sizes, path information, and alternate (ALT) text.
Immediately resize the browser window to a new resolution.
Selectively clear the browser cache and saved cookies. Choose from all objects or those associated with a given domain.
Choose direct links to W3C specification references, the Internet Explorer team weblog (blog), and other resources.
Display a fully Featured Design r0000to help accurately align objects on your pages.

From the perspective of my use, Dom explorer mainly has the following shortcomings and problems (of course, this plug-in is still in beta version ):
1. When using the outline function, you cannot record the custom tag and color ing settings. Close the browser and enable the settings the next time;
2. The outline function is inefficient, especially when the cell border of the highlight table is displayed, if there are more cells in the page, there will be a long waiting time for IE to crash;
3. You cannot view the DOM structure in the modal window. Although Dom explorer is pinned in IE by default (for example), even after unpin the DOM Explorer window, still cannot view the DOM in the modal window;
4. When you use the outline function to display the element border on a page with a frame, it may cause inexplicable confusion;
5. Dom Explorer cannot browse the DOM structure on the Cross-Domain IFRAME page. Similar scripts cannot access the page content, but it is somewhat inexplicable to access the page content, because security is not a problem at this moment;
6. There is no shortcut key for the find next entry in the find menu. In this way, when the content to be found is large, you need to select the find next entry from the menu each time, which greatly reduces the availability of this function;
7. The R/o attributes in the intermediate element Property Window cannot be copied. For example, the innerhtml and outerhtml attributes of span can only be copied. If you want to copy them out, you can only get a dry eye;
8. You cannot select encoding for image Report & view cookies. If there is Chinese content on the page, Chinese characters on the two pages are garbled.

In one breath, I listed eight problems and deficiencies for this small plug-in, but don't be intimidated by me. It makes you feel like a spam. In fact, Dom explorer makes debugging web pages very convenient and worth using.