Ben please open a bug report with this information. Otherwise I will lose track of it. http://code.google.com/p/fbug/issues/list jjb
On Jul 10, 1:52 am, Ben Periton <[email protected]> wrote: > Ok, I didn't have time last night to try and get a test case working, > but there is a trace using SOURCEFILES, ERRORS, and SRCUNITS > at:http://ben.periton.co.uk/firebug-tracing-logs.txt > > Ben > > On Jul 10, 6:35 am, johnjbarton <[email protected]> wrote: > > > Yes, if you ran the trace with SOURCEFILES, ERRORS, and SRCUNITS we > > might get some hints. > > jjb > > > On Jul 9, 8:05 am, Ben Periton <[email protected]> wrote: > > > > I thought that would be the case, but as the only way I've been able > > > to reproduce this is using the development area of the product I work > > > on, its a bit tricky. > > > The development mode is only available using a username/password which > > > would allow access to private data. > > > > I'll try and get a test case working on my site and post back to the > > > issues list. > > > > If not, would a firebug trace be of any use? That is what directed me > > > to the line above? > > > > On Jul 9, 3:12 pm, johnjbarton <[email protected]> wrote: > > > > > Ben the hint on a fix is great but what we really need is a test case > > > > demonstrating the problem posted to our issues > > > > list:http://code.google.com/p/fbug/issues/ > > > > jjb > > > > > On Jul 9, 6:56 am, Ben Periton <[email protected]> wrote: > > > > > > Hi there, > > > > > > I've come across an issue with a site I have been working on. > > > > > This site has 2 modes; live and development. In live firebug works > > > > > fine, but in development mode it does not. > > > > > > When in the Script panel, clicking the dropdown to display the list of > > > > > scripts on the page doesnt populate the list - it is empty. > > > > > > From what I can gather, the issue lies with this: > > > > > > <iframe style="border-width: 0pt; position: absolute; visibility: > > > > > visible; width: 10em; height: 10em; top: -104px; left: -104px;" > > > > > id="_yuiResizeMonitor" src="data:text/html;charset=utf-8,%3Chtml%3E > > > > > %3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize > > > > > %3Dfunction > > > > > %28%29%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire > > > > > %28%29%3B%7D%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C > > > > > %2Fhtml%3E"></iframe> > > > > > > I had a look around the extension, and after a bit of playing this > > > > > seems to do the trick: > > > > > > [lib.js 2381] > > > > > props['name'] = decodeURIComponent(props['encodedContent'].substr > > > > > (0,200)).replace(/\s*$/, ""); > > > > > > replace with > > > > > > props['name'] = decodeURIComponent(props['encodedContent']).replace(/ > > > > > \s*$/, ""); > > > > > > Im sure this isnt the way to fix this, but it seems that limiting it > > > > > to 200 chars stops the last </html> (in the src of the iframe) from > > > > > being processed. > > > > > > Hope this is of some use! > > > > > Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
