I am working on a very old legacy app. It uses a lot of javascript, XPath, and IFrames. I get that these are very old technologies, but I have found that selecting items in the DOM is still very relevant even now with JQuery, Javascript and more. I have used them all. My point is that I can look at the path in the bottom of the F12 tools shown graphically to me, but I can't get that path to use it in code. It is already known, why can't I grab it? We love paths in the world of both Xml and JS/DOM. This is to me a no brainer. If we want to focus on an element in debug mode to see what is going on, then we should be able to grab info to help us up and down the DOM efficiently and directly...no matter how poorly the DOM is designed. I know an XPath would be an antiquanted request, but being able to not only understand why our DOM selections don't make it down the tree, but to be able to correct it with a path from a MS provided menu would make DOM selection much easier. Please consider this to give MS an edge over FF, Chrome, and other competitors with browser tools. I know that you already have this info as you render it to us already, now I just ask for a way to have it written out from a context menu or accelerator key to help IE become the development environment of choice, not just the environment of the most popular OS. In my mind right after you rendered this for us this should have come immediately.
↧