On Jul 3, 4:09 pm, jjj <[email protected]> wrote:
> There is a failure of properly defining the difference between
>
> "firebug ON" (plugin is in a state of systems interaction) and
Let's see. First Firebug is an "extension" or an "add-on", not a
plugin.
I guess a state of systems interaction would be when Firebug has
active listeners on the web page. We'd call that "active".
> "firebug OPEN" (plugin is in a state of user interaction)
Ok open is the Firebug UI is showing, visible.
>
> They are not the same.
Yes we agree.
>
> "firebug on" may imply "firebug open" or "firebug closed". either
Well, since "closed" could be ambiguous. We use "closed" to mean not
active. So your Firebug On + Closed is what we call "minimized".
> way, the plugin should not make that determination unless there has
> been user interaction to direct to to "firebug open" or "firebug
> closed".
Ok, sure.
>
> while
>
> "firebug open" must imply that firebug is on and not closed. this is
> a direct result from user interaction with firebug notifying it to
> display itself.
Well "on and not closed" would be "minimized".
>
> I think this UI defect being resolved would resolve a lot of end-user
> confusion.
? What defect. I don't get it.
I think a more effective way to communicate these issues is to
describe the buttons/key you push and the state you see/don't see.
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
-~----------~----~----~----~------~----~------~--~---
