ColinFine wrote: > Yes this is a common problem, but there is no straightforward > solution. > > Firebug, and anything else running on your browser machine, has only > what your HTTP server sent out, and that is after PHP or any other CGI > language has finished with it. It has no idea where the code came from > or how it was generated. > > It is possible that FirePHP (http://www.firephp.org/) might be of > help, but apart from that, all I can suggest is searching your PHP > files for strings related to the bit you need.
There's a hint there: add a string (most likely a comment) to each bit that will be sent to the browser, that indicates its origin. Look at the earlier thread about "//@ sourceURL" for an example of this, one for which Firebug will actively assist. (Hmm, could Firebug learn to recognize a similar string in CSS "chunks" and somehow tag the styles that come from that chunk?) -- Don Dwiggins Advanced Publishing Technology --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
