And about Dragonfly, will see soon how good are those strong foundations. It doesn’t have new features, but I guess you can agree that its fast, and stable.

display problems, dom properties (browsers differ i.e.: in what are the default values of certain properties), event handling ( look at quirksmode.org event compatibility table.. there are almost no events handled identicaly. and there is the whole topic of javascript, that is the sole reason why dev tools are so important. you simply cannot debug js problems in browser A using engine B. it simply doesnt work that way.

final reason why not to use dragonfly at all, is that this is very very stopgap solution, that doesnt offer really any functionality, even the basic one. problem is, that it is almost 3 years old now, and still is nowhere..

Dragonfly is way faster then firebug. Besides I simply would like to have same set of features, while debugging in all browsers.

“there is no single feature dragonfly has, that firebug or visualStudio+ieDEVtoolbar do not have.”
Yep, I know – I simply find dragonfly faster (as mentioned), and I like the way new dragonfly highlights elements.

“and no, it isnt possible, because DF uses scope protocol, that both FF and IE are completly ignoring and will never look at it.”
Well, who knows, they might – if it could be really useful. I don’t know to much about it yet, so I cannot make such statements.

“unless all the engines start interpreting standards in the same way.”
Why? What would happen if I would run Dragonfly in firebug? I would see DOM structure, each element css, http headers, all other stuff, where is the problem here? And I could change it. If you are referring to some display problems, caused by wrong understanding something why not prepare simple javascript to overcome those problems?
I don’t see why interpreting standards would be a problem here?

there is no single feature dragonfly has (except for remote debugging, that does not work in most cases anyway) that firebug or visualStudio+ieDEVtoolbar do not have.

and no, it isnt possible, because DF uses scope protocol, that both FF and IE are completly ignoring and will never look at it.

and as a final touch – debugging FF with Opera’ tool, or IE with FF tool is completly impossible, unless all the engines start interpreting standards in the same way. that wont ever happen.

Then I would like to see Dragonfly both in FF and IE – AFAIK it should be possible, since its mostly JavaScript anyway. Am I right?