On Nov 14, 12:59 am, woomla <[EMAIL PROTECTED]> wrote:
> The viewableLines stuff still is not correct. Firebug.js line 2105
> must be called unconditionally because otherwise the script view will
> have empty space above the lines after enlarging the window. Off
> course this should be triggered on another way.
I'm unsure what you mean here, but I guess: "Some things are better if
buildViewAround always calls setViewableLines"? Is it related to
resize failng?
>
> Resizing the firebug stand alone window does not repaint or re-calc
> the script view. This leaves a white area above/beneath the lines.
> Scrolling recalcs it.
There's someone with id woomla who's looking into this ;-)
My guess is that the onResize is not attached properly for the
standalone window.
>
> The lineheight in firebug.js is not measured correctly (on my systems
> that is). I.e. at a certain text size, measureText returns 17 but
> chromebug inspect shows a line size of 15. The number of viewableLines
> is therefor measured incorrectly, it is to small and thus to less
> lines are displayed leaving some white space beneath the script lines.
> I somehow solved it by using a magic number translation in measureText
> which changes 17 to 15 etc, but I don't think this is the correct
> solution.
I'm open to suggestions...
>
> line 1956 of firebug.js: FBTrace.sysout("setSourceBoxLineSizes....
> should be setViewableLines, if at least you want to output the method
> name.
done
> Sometimes chromebug breaks on error when it encounters an undefined
> variable in firebug,js line 1592. this.context.chrome sometimes is
> undefined. I'm not investigating this and don't know when it happens,
> but I've put a "if (this.context.chrome)" in. I don't know what the
> code should do when it is undefined though.
I know this is tempting and I've done it a lot, but lately I've
stopped adding these until I am convinced that I understand the reason
for the test. Otherwise we'll end up with "if (property)" in front of
every function call. Somehow navigate() is being called on an invalid
context, better to figure out why. I've not seen this happen however.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
