Just a quick update on the inspect issue. I now have the new inspect implementation working for the frame highlighter (normal element inspector), and the box model highlighter (with rulers etc.)
There are still a few issues to overcome: o Keyboard navigation within the inspector does not work (we need this for accessibility) o Image map areas can only be highlighted by hovering over them in the HTML tree o It is necessary to click to hide the overlay after hovering on the HTML tree o Framesets cause multiple issues On the positive side it is: o much more responsive o not affected by the target pages javascript or css (you will be able to inspect any page) o now possible to inspect disabled elements o also possible to draw anything on the transparent layer because we stretch a canvas element accross the viewport Assuming that there are no serious issues come up it should not be long now. -Mike Ratcliffe On May 20, 5:46 am, johnjbarton <[email protected]> wrote: > Yes we know about some problems in inspect after 1.4a24. > > Mike Radcliffe fixed a long standing bug in inspect for 1.4a24. But it > created a different set of bugs. Unfortunately we have no way of > knowing which pile of bugs affect more users. > > He is working on a third solution. The original Joe Hewitt > implementation computes positions from offsets with many special cases > and it injects elements to draw the boxes on the screen. Radcliffe's > solution corrects the positions but still injects. The added elements > interfere with inspection. He is working on a solution that does not > inject but overlays a transparent window. Or at least this is the > story as I understand it. > > jjb > > On May 19, 8:04 pm, niver <[email protected]> wrote: > > > Something changed in the Inspect Element function between 1.4.0a23 and > > 1.4.0a24, because I'm unable to inspect some complex javascript- > > generated webpage since then. Using .24 and further versions, when I > > click on the flashlight (inspect) button, the selection rectangle > > stops only on a very few, simple elements of the page, but refuses to > > follow the mouse in certain areas. > > > I'm trying to create a simple testcase or to identify what in the page > > Firebug don't like, but I didn't succeed. While I'm trying, is it > > something someone else has been facing? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
