James, I"m making a third pass over your note, mainly to advertise you trying 1.5a9. Below:
On Jul 6, 10:13 am, nod <[email protected]> wrote: > Okay, let's start fresh and try this again. Long time user, 2nd post. > > Looking through the newsgroup, I see several people trying to > articulate this point and explain why it's such a significant problem, > without success on the receiving end. I don't know if I'll be more > successful, but I'll be trying to be very concrete, logical, and step- > by-step. > > Core problem description: conflation of UI visibility with activation > I'll be trying to explain: > 1. what this is > 2. that this is different from previous Firebugs > 3. why the conflation is a bad thing > 4. why the way the change was implemented is a bad thing > > Scenario A: > 1. Ctrl-F12, "Open Firebug in New Window" > 2. See a greyed-out window with a button in the middle saying > "Activate Firebug for the selected Firefox tab" > 3. Think "ok, I will activate Firebug so that it will be 'on' and I > can debug this web page" > 4. Click the Activate button. > 5. Discover that a page refresh is needed, and refresh the web page. > 6. Use Firebug to investigate an issue in the web page > 7. Be finished with Firebug for the moment, but want to continue > working with the web page > 8. Use i) Ctrl-W, ii) File->Close, iii) the red "X", or iv) "Open > Firebug in New Window" to close the Firebug window. > 9. User now thinks Firebug window is closed, but that Firebug is still > running (like all previous versions) on this web page. > 10. Repeat step 1. > Expected: To be in the same state as the beginning of step 8 > Actual: The user is at state 5 > Expected: That the console log and net tab have been operating between > steps 9 and 10 > Actual: Firebug has been "suspended" during that time, so any issues > have to be recreated Please try Firebug 1.5a9 and let me know if this is fixed. ... > Expected: "minimize" works the same for all modes of Firebug > Actual: in-page Firebug is hidden completely by minimize, while the > external window stays around in the Windows taskbar. I don't plan to change this. I could add back the [_] button inside the UI but it would do the same thing and the operating system window close. > Expected: if the Firebug UI insists on being visible when active and > hidden when deactivated, then the external window should hide itself > for non-active tabs > Actual: the Firebug external window remains open (but greyed out) when > the user switches to a non-active tab I don't get what the problem here is. > Expected: external window mode v. in-page mode will be remembered > Actual: if a user uses the "switch to non-active page, then close > external window, then come back to active page" trick, the Firebug UI > comes back inside the page rather than as an external window I don't know the exact sequence here, let me know if 1.5a9 works or not. ... jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
