Bookmarklet/Favelet that gives info about moused over DOM element

First, you must review the "Mouseover DOM Inspector" bookmarklet at: [login to view URL] This bookmarklet will be similar to that, but will have slightly different functionality: 1) Clicking the bookmarklet causes the bookmarklet to execute. 2) it does not need to display to the user the current attributes of the DOM element being moused over like the MODI above, but it does need to indicate to the user that it's turned "on". Maybe a tiny red box in the upper right corner or something? I'll leave that indicator to the coder. 3) Mousing over an object causes that object to be highlighted, just like MODI above. 4) when the user presses "ESC" button, the bookmarklet is no longer active and mousing over an object does not cause it to be highlighted. 5) when a DOM element is highlighted, and the user presses the "X" button, the bookmarklet sends the following information to our server: a) the DOM path to the highlighted element b) the innerHTML of the highlighted DOM element c) the URL the user is currently on (Note - I'll send successful bidder a bookmarklet and associated scripts that I used in the past to send info from a bookmarklet to a server. That should save time. You don't need to do ANYTHING on the server side by the way.) If an object is not highlighted when the user presses the "X" button, a JS alert warns the user that nothing is selected. ------------ The second part of the bookmarklet is to do sort of the same thing... in reverse: If you click "T", a dialog box appears and you can enter a string that represents a DOM path (using the same format, etc. generated earlier). When you enter the string and press enter, the bookmarklet highlights the DOM element that was entered into the dialog box. If you have any questions, let me know. Thanks. ## Deliverables 1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement). 2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment. b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project. ## Platform JS script