That's an interesting question: how could you accomplish that in BBEdit? It's easier to understand how Firebug does it -- clicking on part of the rendered web page jumps to a line in the HTML, or vice versa, because Firebug is working with Firefox's *generated* source code (transformed as the browser understands it in terms of its own DOM), not with the *original* source as we do in BBEdit. And yet...
If you think about it, the browser *must* have an internal concept of the relationship between the original source code and its generated HTML/DOM in order to render the page in the first place. I would guess that the browser doesn't bother maintaining a "memory" of how it transformed the original to the rendered version once it's accomplished that, but I don't know... maybe there's a way to tap into that correlation on a low level? -- This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" 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].
