I have caught myself many times clicking on something rendered in the HTML BBEdit preview window, and expecting it to hope to the line of code that created it. For example if I've spotted a typo. San's comment about Firebug (actually all the browsers' built-in code inspectors do this at this point) made me remember this feature, and that I've attempted to use it in BBedit! Clearly it couldn't work with out advanced logic if scripting was involved (say the text you clicked on was included from another document you didn't have open).
Anyhow, if it existed, I'd use it. On Wednesday, October 8, 2014 7:34:24 PM UTC-4, San wrote: > > 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].
