On Jul 28, 9:22 am, "Alex Ryazanov AKA the Marrch Ca'at"
<[email protected]> wrote:
> > > 2. When I collapse the FB panel, switch to another tab that FB isn't
> > > active on and accidentally click on FB icon - FB becomes active and
> > > expanded. It's not what I want, so I press the Off button, and it's
> > > disabled and collapsed. But it doesn't treat that as collapsing
> > > internally, so when I switch to a tab I have FB active on, it's
> > > automagically expanded. It's a very unclear behavior, and I treat that
>
> > Well it's not "automagically" expanded. It opened because you switched
> > to a tab you want to debug.
>
> Oh, dubuggin' an app doesn't mean having the debugger windows opened
> all the time, does it??
I don't understand what you are saying here, sorry.
>
> > > as a bug: if the paradigm is that FB is expanded/collapsed for the
> > > whole app, not for a single tab, then when I collapse it on one tab it
> > > should be collpased everywhere - despite the way I did that.
>
> > That is not the paradigm. The paradigm is to be active on pages you
> > want to debug. If you deactivate it with Off, then naturally it won't
> > show up on that tab.
>
> Once more: you know better, that "active" != "expanded". I want to
> debug (tracing the scripts and network interactions and console output
> etc) several pages. But I don't need the panel to be placed on screen,
> to be expanded - for all that pages at the same time. ANd there is no
> obvious reason why I have to.
Again, I am unable to understand. I know it is quite tedious, but the
most successful way to communicate about the UI is to list the steps
one by one using the names of the buttons in the UI. That way we don't
get lost in the meaning of closed, off, deactivated active expanded
hidden and on and on.
>
> > The 'placement' (in browser, minimized, or detached in a new window)
> > is independent of the tab. If you have it open in browser on one tab,
> > then it will be open in browser on all tabs *that are active*. (And it
> > will be closed and inactive on other tabs).
>
> It's the paradigm I mentioned above. You don't want to allow user to
> have it minimized on one pages and expanded on others, instead you say
> "it's our decision to have one placement for all tabs instead, despite
> what do users want". I just said that. It's a pity.
Yes, despite what one user or ten users request, it may still make
sense to do something different. In this particular case, the two
reasons to not implement different placement for different pages is
complexity in the source code and complexity in explaining to users.
You can already see how much trouble we have in explaining the simpler
version we have now. But more important, we should put our time else
where, for more impact. I know from experience that no design for the
activation will be successful.
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
-~----------~----~----~----~------~----~------~--~---
