On Friday, May 6, 2016 at 12:03:15 AM UTC+2, San wrote: > > As Alfonso mentioned, the Firefox DevTools already have a feature that >> goes into that direction... >> > > Sebastian, the link Alfonso supplied doesn't refer to the Firefox dev > tools, it involves the Chrome dev tools. >
My mistake. It was Erik that mentioned them. Though, as far as I know, the dev tools of all major browsers support source maps, probably even the ones from Edge, though I can't test that at the moment. > And it seems a little closer to what I'm talking about than your link > does, although I'm not sure... I think they expect you to do the editing in > their dev environment, not in your own text editor as I prefer. I only > looked briefly at the Moz page you linked to, but from the introduction, it > seems to refer only to finding the original JavaScript sources of compiled > JavaScripts. > Yes, that's it. It doesn't work with external editors, it only allows you to debug the original sources within their tools instead of the compiled ones and that only works with CSS and JavaScript. Sorry for not being clear about that before! > I'm interested in mapping the current browser-rendered page to its main > HTML server page, and then opening that HTML in my text editor, nothing > more. Nothing fancy. > In case the HTML is dynamically generated, there is no *main* HTML server page, it will be some server-side script. This is so important to me (the way I work) that if a newer version of > Firefox breaks the extension I'm using, I'll stop upgrading Firefox and > stick with the old version. If Firefox could be scripted with AppleScript, > I might be able to figure out a way to do the mapping there... but AFAIK > Mac Firefox isn't AppleScript-able. > > I like the Firefox/Firebug devel interface better than Chrome's (I guess > I'm just more used to it), but Chrome is much more successful at rendering > a wide range of pages for ordinary browsing... so I could see a situation > where I end up *developing* in an old version of Firefox, but doing > routine *browsing* in a current version of Chrome. Which sounds a little > awkward. That's what I'm hoping to avoid. > Again, I can fully understand your request and I'd really like to have that feature, though it doesn't fit to the topic of this thread. I found bug 1026674 <https://bugzilla.mozilla.org/show_bug.cgi?id=1026674> now, which targets live editing the source files within Firefox's WebIDE. And I've now created bug 1270733 <https://bugzilla.mozilla.org/show_bug.cgi?id=1270733> for opening the files in an external editor. If you want to follow these reports or comment on them, you need to create a Bugzilla account. Sebastian -- 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 https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/d5e5c978-88df-4d03-a3ba-a619c1065124%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
