Last modified: 2010-12-05 15:03:09 UTC
Tested with IE 5.2.1 on Mac OS X 10.4...
Subcategory links are all stacked on each other in some weird way... ewww!
Non-functional [+] buttons appear, and simply show "loading..." when clicked.
Created attachment 2672 [details]
Screenshot of subcategories on [[Category:Programming languages]]
Same behavior in 5.0 under Classic.
I'd recommend not inserting the [+] links until a js compatibility check is done, so the system degrades
gracefully when no JS ability is present or limited JS with no AJAX-ability.
Depending on how badly the visibility bug is broken, just removing those might sidestep the problem.
(Mac/IE has lots of these weird bugs where text goes zipping around in weird places if the styles
are kinda weird. Often seemingly unrelated changes will "fix" it.)
Ugh, are we still putting effort into support IE5/Mac?
I'm more concerned about general nice degradation when there's no JS or limited JS. :)
(In reply to comment #3)
> I'd recommend not inserting the [+] links until a js compatibility check is
> done, so the system degrades
> gracefully when no JS ability is present or limited JS with no AJAX-ability.
> Depending on how badly the visibility bug is broken, just removing those might
> sidestep the problem.
> (Mac/IE has lots of these weird bugs where text goes zipping around in weird
> places if the styles
> are kinda weird. Often seemingly unrelated changes will "fix" it.)
I've done this in r48101, but I don't have a copy of IE5/Mac, so I'm not sure if the problem has been resolved.
Created attachment 5896 [details]
IE/Mac on left, Firefox 3 on right
The broken expando boxes are now gone, but the actual text links are still missing too.
Something seems to be getting confused... the link's hidden even with JS off. Admittedly the structure's a little scary:
It may be confused by the combination of styles in some way. I'd probably recommend not putting specific effort into this, but if CategoryTree's output is rewritten to be cleaner there's a good chance this'll clear up.
Marking this bug as Lowest priority.
I've done this in a batch to (usually enhancement request) bugs where:
* It is not clear that this bug should be fixed.
* It is not clear how to fix this bug.
* There are difficulties or complications in fixing this bug, which are not justified by the importance of the bug.
* This is an extremely minor bug that could not be fixed in a few lines of code.
If you're interested in having one of these bugs fixed, your best bet is to write the patch yourself.
Doesn't even show up in the squid reports anymore, so is likely to have a market share of below 0.01%