Undetermined tree:progressmeter and Mac/Pinstripe - Mozilla

This is a discussion on Undetermined tree:progressmeter and Mac/Pinstripe - Mozilla ; Is there any way to get the undetermined tree progressmeter to display correctly on Mac/Pinstripe? We use a custom image there (based on the mozilla one). The result unfortunately looks like this; the image simply "overflows". http://img205.imageshack.us/img205/9...magine2nx2.png There seems to ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Undetermined tree:progressmeter and Mac/Pinstripe

  1. Undetermined tree:progressmeter and Mac/Pinstripe

    Is there any way to get the undetermined tree progressmeter to display
    correctly on Mac/Pinstripe?

    We use a custom image there (based on the mozilla one).
    The result unfortunately looks like this; the image simply "overflows".
    http://img205.imageshack.us/img205/9...magine2nx2.png

    There seems to be a somewhat related bug:
    https://bugzilla.mozilla.org/show_bug.cgi?id=304147
    But it doesn't actually address treerogressmeter but the more general
    xul element.

    MXR for 1.8 and seamonkey indicate that the toolkit code doesn't handle
    "undetermined" at all?!

    Does anybody know if there is a workaround other than not displaying the
    image on mac at all?

    Nils

  2. Re: Undetermined tree:progressmeter and Mac/Pinstripe

    Nils Maier wrote:

    >MXR for 1.8 and seamonkey indicate that the toolkit code doesn't handle "undetermined" at all?!
    >
    >

    Tree rendering is actually part of core layout, rather than toolkit,
    although this is of course influenced by CSS style rules in the theme.

    Which browser/xulrunner platforms and version(s) are you targetting?

    --
    Warning: May contain traces of nuts.

  3. Re: Undetermined tree:progressmeter and Mac/Pinstripe

    Neil wrote:
    > Nils Maier wrote:
    >
    >> MXR for 1.8 and seamonkey indicate that the toolkit code doesn't
    >> handle "undetermined" at all?!
    >>
    >>

    > Tree rendering is actually part of core layout, rather than toolkit,
    > although this is of course influenced by CSS style rules in the theme.
    >
    > Which browser/xulrunner platforms and version(s) are you targetting?
    >

    Yeah, I know; just wasn't precise enough here. toolkit code does not
    seem to handle it because the core layout/widget code is either buggy or
    doesn't address this at all for mac.
    So I wondered if anybody got a work-around (some nifty set of css rules
    that will have it display correctly).

    Generally this is about DownThemAll!, and we're targeting 1.8 and
    1.9/trunk in general on all platforms (win, mac, unix (recent linux at
    least)), and FX, TB (2/1.8, 3/1.9), Songbird (0.4+/1.9), Flock (1.0/1.8)
    and Seamonkey (2/1.9) in particular.

    The undetermined treerogressmeter works fine for win, unix, but fails
    on mac, like displayed in the screenshot from my original post.
    I guess the screenshot was taken from FX2 on Tiger (or Leopard?).

    If interested, this behavior is visible when using this XPI:
    http://code.downthemall.net/releases...mall-1.0b3.xpi
    build from svn co http://code.downthemall.net/repos/branches/1.0.x/
    Just start a download and while the size is not known the undetermined
    bar is displayed.

    If no solution comes up, we have to disable that gfx for mac.

    I should file a bug for this?!; unfortunately I don't own a mac myself,
    so prepping a testcase or even a patch is impossible.

    The image is available here:
    http://bugs.code.downthemall.net/tra...determined.gif
    And the corresponding css-bit is this one:
    http://bugs.code.downthemall.net/tra...r/style.css#L6

    Which is very similar to:
    http://mxr.mozilla.org/mozilla1.8/so...l/tree.css#159
    But pinstripe leave this blank:
    http://mxr.mozilla.org/mozilla1.8/so...l/tree.css#163


    Nils

  4. Re: Undetermined tree:progressmeter and Mac/Pinstripe

    Nils Maier wrote:

    >But pinstripe leave this blank:
    >http://mxr.mozilla.org/mozilla1.8/so...l/tree.css#163
    >
    >

    It looks like an oversight on the part of Kevin Gerich... even the very
    first pinstripe tree.css omits it. See
    http://bonsai.mozilla.org/cvsblame.c...t=/cvsroot#126

    As for filing a bug, I suggest you need two reduced test cases, one with
    the default look and one with the custom look.

    --
    Warning: May contain traces of nuts.

+ Reply to Thread