I agree that this can be very useful, but shouldn't it be discussed as part of http://code.google.com/p/fbug/issues/detail?id=179 ?
On Oct 24, 9:00 pm, Asrail <[EMAIL PROTECTED]> wrote: > On Fri, Oct 24, 2008 at 2:00 PM, John J Barton > > <[EMAIL PROTECTED]> wrote: > > But the CSS property may not even be in the original. Then what? > > The inserted javascript and html are the minor issues. > The easier, although the less useful, thing to implement is to track > the changes made using the Firebug interface and display them. > At least this will show the actual changes the user made to the page, > even though that may give undesirable results. > > One array or hash could be used to mark the changed rules fuzzy and > one could use a secondary cssstylesheet to store the old values. > > The hardest part is that the interpreted rules are not the same > present on the css files, so it is not so easy to port all changes. > But... at least it is better than nothing. > > The user would have to find the right rules, but at least he would > have a list of changed properties. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
