Dom explorer upgrade fixes most problems

Dom explorer, the IE Plug-in used to view the DOM structure of DHTML documents, has been plagued by many minor bugs and deficiencies due to the beta1 version. Although the problem is not fatal in comparison with its advantages, it still makes people feel like they are in the throat. Today, I browsed Microsoft's download site and found a new version of Dom explorer. So I downloaded it and updated it immediately!

This beta 2 version of the Toolbar contains functionality and stability enhancements over previous versions and includes des the following improvements.

-- You can now selectively enable and disable CSS parsing.
-- The MISC menu contains a color picker.
-- Several link reports are available.
-- When you select an element in the DOM element tree list, the selected element scrolls into view if it is not already visible in the browser window.

Four major corrections mentioned by Microsoft in beta2 are the ones I mentioned earlier. The only one that I did not care about was meaningful. In addition, Dom Explorer also has a major correction, that is, the outline function is greatly improved, and basically no IE crashes.

However, unfortunately, there are still many difficult problems that have not been solved, including the one mentioned last time:
3. You cannot view the DOM structure in the modal window. Although the 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;

In addition, the context menu is not supported on the DOM tree node, which is inferior to the DOM inspector of Firefox. However, there are weak signs that the DOM tree in beta2 has traces of reference inspector, as shown in the # text node display support.

Download: iedevtoolbar.beta2.rar
RelatedArticle: Functions and problems of the DOM Explorer plug-in