I can see valid reasons for all proposed activation models and valid issues/dislikes/conflicts with each specific one depending on your use case.
Has it ever been discussed to allow them all? We can pick one default one which is most "typical" but then allow the user to change it. We could add a "debug profile" feature where you can specify different debug profiles and for each profile you can specify how you want things activated. Profiles could be browser window specific and you could easily switch between them. As firebug evolves there will be additional reasons for each use case. Especially if there are new firebug extensions that need activation in a specific way to function properly. If we introduce the concept of debug profiles we could also add the ability to specify custom request headers for each profile. That way we can tell our server code to do something different if we are accessing anything for debug purposes. By providing the basic tools to allow systems to recognize specific developers and respond accordingly we can open up the door to a whole new set of possible firebug extensions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
