Closed Bug 458225 Opened 17 years ago Closed 17 years ago

Need a way to toggle freezing of mozmill DOM Explorer upon clicking

Categories

(Testing Graveyard :: Mozmill, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: farhad, Assigned: adam.christian)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 Build Identifier: Here is the conversation I had with Clint Albert: it explains why we need to toggle this thing, otherwise it will be impossible to find some of the elements on a lot of pages: [09:00] Farhad: I tested out the latest mozmill, it's actually working with flock's side bar (which i couldn't do with the older version)! [09:00] Farhad: one problem, that is with the explorer and it's kind of important [09:01] Farhad: when you click on an object, the explorer freezes, this is good for copy pasting, but... [09:01] *** josh has joined #qa. [09:02] Farhad: if you have a submenu (for example in yahoo compose mail button and a lot of other places), you can only reach the top level [09:02] Farhad: it's impossible to see the ID or Name of the element of any 2nd or 3rd or lower leverl elements [09:02] ctalbert: Farhad: you have a good point. We were thinking that freezing the explorer would make it easier to grab the text out of the explorer window [09:02] Farhad: is there any way, we can turn that on and off? [09:03] Farhad: ctalbert: exactly, i thought the same thing [09:03] *** dmoseAway is now known as dmose. [09:03] ctalbert: probably. Adam just implemented a key control to copy the explorer string directly to the clipboard so you don't have to worry about clicking any more. [09:03] Farhad: but then for those cases, it cuases problem, maybe a button to enable/disable would be awesome, [09:04] Farhad: ctablert: great, but still we will need the freezing to stop, so we can access lower level elements [09:04] ctalbert: yes [09:04] Farhad: u want a bug for that or not really! [09:05] ctalbert: yeah, if you don't mind, I would. admc is in channel, but I really don't think he's awake yet. And the explorer is pretty much his baby, so he'll need these details. [09:05] ctalbert: You can just copy/paste this conversation in the bugreport [09:09] Farhad: k, thanx Reproducible: Always Steps to Reproduce: see above
Severity: normal → major
I think we should have a toggle between "click" and "doubleclick" so that we can still have the same behavior for freezing.
Can someone assign this to me so I can close it?
Adam, what is the current solution for the problem? Which key or what else do I have to use to get the id copied? Assigning to you for further processing.
Assignee: nobody → adam.christian
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Oh, will it be solved by bug 456451?
So at this point we have the click, or double click, and if you are using the dom explorer and want to copy the current locator information without going back to the mozmill window you can press alt/option+shift+c and it will copy the data to the clipboard. I just tested all this and am marking this bug fixed.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Adam, can we add this accesskey to the inspector menu entry? Currently its greyed even the inspector is enabled. But it would make sense to point it out. Otherwise users are not aware of that fantastic feature. Shall I file a new bug?
Organized the menus better and gave them all key combos, Committed revision 302.
Adam, I've tested it now with the top level menu on http://mozilla-europe.org/en/. Pressing Shift+Alt+C while staying over an element copies the whole inspector output to the clipboard. Is that wanted or do we only wanna have to element? Otherwise it looks good.
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.