Today I dove in headfirst on automating bookmarks from browser-chrome. I normally read the code to figure out what is going on, but instead installed DOM Inspector and my life became much easier.
I found a post on mfinkle’s blog and started there. This didn’t work so well (we have incremented Fennec version since it was last modified) so I installed it on firefox and then copied the extension to fennec. This can be done by looking in your extensions directory inside your profile ~/.mozilla/firefox//extensions/inspector@mozilla.org/* and then copying all of that to ~/.mozilla/fennec//extensions/inspector@mozilla.org/.
This is all assuming you have installed Fennec and it uses your default profile directory. In my case, I have many versions of Fennec, so I have to go into my Fennec/extensions directory and copy the inspector@mozilla.org to it.
Ok, once installed, I fired up fennec, and hit CTRL+SHIFT+I and up popped the inspector. Being a n00b, I didn’t figure out the file->”inspect chrome document” for about 5 minutes, then it started making sense and I was able to drill down and figure out the layout inside of Fennec.
3 Comments
May 20, 2009 at 1:12 pm
[...] About using dom inspector with fennec [...]
May 27, 2009 at 12:23 am
[...] the problem was about clicking the thing. First of all, the image button object according to Domi has no click property so clicking won’t work. I figured some sort of mousedown event needs to [...]
June 10, 2009 at 3:29 pm
[...] to create a .jar file out of fennecmark instead of an unzipped extension in the profile (similar to dom inspector). This was a frustrating process until I found Ted’s wizard. After running the wizard, [...]