DOMi and DOM events
Alexander Surkov
doesn't address DOM Events. I think it would helpful if DOMi will be
able to listen DOM events and show them for the certain element. User
should be able to specify events he'd like to listen, to see event's
properties, to see event listeners registered on the given element for
the certain event. It would be nice feature to learn in what order
events are fired, what event listeners are registered. There is
similar feature for firebug extension for firefox. I talked with Shawn
Wilsher. In general he likes the idea and he sugested to get some
public feedback. Does anybody consider this to be useful?
Alexander.
Sailfish
aid but also as an extension writing learning tool. Additionally, I
could also see where it could be very useful for building test cases to
be used when testing new releases.
fwiw
--
Sailfish - Netscape/Mozilla Champion
Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/
mozilla-based Themes: http://www.projectit.com/freestuff.html
Nickolay Ponomarev
> I think it would helpful if DOMi will be
> able to listen DOM events and show them for the certain element.
I agree that would be quite helpful. There was/is a DOMi extension
called EventSpy, which I haven't played with, but it seems relevant
(from its description).
Nickolay
Shawn Wilsher
Indeed, there is such an Add-on:
https://addons.mozilla.org/en-US/firefox/addon/1100
Perhaps someone should try contacting the others and seeing if they
would be willing to get their code checked into CVS? I suppose that
would actually be my job now that I think about it...
Cheers,
Shawn
jason...@gmail.com
> Indeed, there is such an Add-on:https://addons.mozilla.org/en-US/firefox/addon/1100
>
> Perhaps someone should try contacting the others and seeing if they
> would be willing to get their code checked into CVS? I suppose that
> would actually be my job now that I think about it...
Hi all, I maintain the Event Spy add-on Shawn mentioned, though I no
longer ever use it myself. :-)
Shawn, I'd love it if Event Spy became part of the DOM Inspector. How
much code merging work would be involved in getting it checked into
CVS? (You can view the extension's source at [1] if you are logged
into your addons account).
Also, Shawn, are you willing to do the work? If not, Sailfish,
Alexander, would you be willing to? I don't want to but I might do it
if nobody else would. :)
Please reply to group and CC me,
Jason
[1] https://addons.mozilla.org/en-US/firefox/files/browse/14052
Sailfish
> On Jul 11, 12:31 pm, Shawn Wilsher <sdw...@mozilla.com> wrote:
>
> Also, Shawn, are you willing to do the work? If not, Sailfish,
> Alexander, would you be willing to? I don't want to but I might do it
> if nobody else would. :)
>
an extension writer.
Shawn Wilsher
Unfortunately, I have too much to do already before Firefox 3. It might
be a bunch of work, but we have time to get it landed in CVS. If we do
get it in, I think a view pane would be better than a dialog.
Cheers,
Shawn
Alexander Surkov
<jasonspi...@gmail.com> wrote:
> On Jul 11, 12:31 pm, Shawn Wilsher <sdwi...@mozilla.com> wrote:
> Also, Shawn, are you willing to do the work? If not, Sailfish,
> Alexander, would you be willing to? I don't want to but I might do it
> if nobody else would. :)
I shouldn't be a problem to put your extension into DOMi as is. But
I'm not sure implementation way of the extension goes with DOMi.
Though the question should be addressed to Shawn :).
So, I'm not sure it's a good way to show an dialog to listen events.
I'd rather use right panel for this. I mean when DOM node is selected
then I can choose DOMEvents view and whatch views there. Also I'm not
a fun to keep together event object and events list in one tree
element. I would keep them in two tree elements. The top one shows
event list, the bottom one shows event properties for the selected
item from event list.
Alexander Surkov
> Also, Shawn, are you willing to do the work? If not, Sailfish,
> Alexander, would you be willing to? I don't want to but I might do it
> if nobody else would. :)
It shouldn't be a problem to expose the extension code into DOMi as
is. But I'm not sure EventSpy approach is much similar with DOMi one.
I put my thoughts into bug 388204 (https://bugzilla.mozilla.org/
show_bug.cgi?id=388204).
Alexander.