Hello all,
Not sure if this is the place to put stuff like this, so please excuse me if this belongs elsewhere. I’ve been using FF Developer Edition as my daily dev browser for a long time, but haven’t ever posted issues.
I’m currently hacking on some legacy apps that use a lot of iframes. We load a custom Softphone into a popular CRM. The telephony backend is all proprietary, so there’s a lot of chatter back and forth.
While debugging these tools, I’ve noticed Firefox has a hard time showing me the proper source code. Let’s say the site I’m on has source from 6 frames. I select the frame I’m interested in, and then proceed to select my file from the tree-view on the Debugger tab. Clicking on said file results in a blank file. Firefox displays a single line of code in a 6000 line javascript file. I.e. setInterval()
Typically, I’ve found I can fix this by clicking somewhere within the source-code and then refreshing my browser. (clicking makes sure my frame selection is honored)
I see this happening with multiple files on this same project. All are over 5k lines. No libraries or tooling, just vanilla JS.
I’ve also seen that firefox’s debugger cannot follow iframe communication. For example, stepping into the following always results in an error, where Chrome is fine to follow the chain of events.
function PostMessage(msgType, data) {
var msg = JSON.stringify({ msgType: msgType, data: data });
g_IframeComms.contentWindow.postMessage(msg, g_AgentConfig.domain);
}
Is this just the nature of the beast, using a beta debugger? If so, I’m glad to report issues.
Thanks!