Sebastian wrote: > The reason why the HTML output seen in the browser cannot be directly > mapped to the server-side source code is that it is mostly dynamically > generated.
For PHP-generated code, of course that's true. OTOH... in general, it *is* sometimes possible to map a Firefox-rendered page to the (static HTML) server source, using a Firefox extension called ViewSourceWith <https://addons.mozilla.org/en-US/firefox/addon/dafizilla-viewsourcewith/>. The interface is confusing and the 'documentation' even worse, but eventually I got the mapping set up between my devel websites and both my devel and live servers. This has nothing to do with Firebug, but it doesn't seem to conflict with Firebug either. (I wish Firebug could do this on its own, so I didn't have to bother with the additional extension.) ViewSourceWith lets me click a button in my Firefox Add-On Bar for any of my rendered pages, which then opens the actual server source of that page* -- not* a dupe, as in other "view source" utilities. It opens the page in BBEdit, which is my coding text editor that created those pages in the first place. This creates a good back-and-forth workflow between the browser and the editor. (Do real IDEs do something similar? I've never used one.) I've never been able to figure out the mappings ViewSourceWith supposedly allows for JavaScript, CSS, and other stuff, just for the core HTML... but BBEdit has a popdown menu from the HTML page that opens linked code pages, so that's okay. As for PHP mapping... no. As Sebastian said, that's dynamic server code. I assume the browser has no knowledge or memory of how the HTML and CSS was initially generated upstream, unless there's some clue being passed through the HTTP headers that I never noticed. Lawrence -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/CAMoMLKjANh0OQ1MXAtofk5K0k_8AOYgkFJsbQVoGVCQPNf8V0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
