If I have an expandable node that has children then the tree uses an image tag with just a style property and no src to create a space between the expand/colapse image and the node text/icon. In IE7 this isn't visible but in IE8 you can see a sunken border around it. This is evident in the Samples Browser on the IG website.
I've worked around this by using some javascript to set all img tags with no src attribute to point to clearpixel.gif but I'm wondering if this is any issue IG are aware of and if it's been fixed in a more recent version (I'm using 2008v1)
I've looked at the samples for our recently released 9.1 and didn't see what you describe. Could you perhaps attach a screenshot. An option is to upgrade to 9.1 and use the new AJAX WebDataTree. This does not use images to create space, so you would not have this problem.
This problem definately occurs in IE8, I'm looking into it now. Those empty images are just spacer images that should not be displayed.
Hey guys, this problem was written up as Bug 15995, the issue is that IE8 is displaying the contents of an empty image, the resolution was to also apply visibility:hidden to the element. Should be available in the next hotfix, for versions 8.1 and up.
When do you believe this hotfix will be released. The latest hotfix for 8.2 does not show in the fixed bugs that this is corrected.
Thanks.
I'll check on that for you, I suspect that the reason it's only marked fixed in versions 8.3 and up is that it was only reported for 8.3.
However, since I fixed the bug personally I feel safe telling you that it was definately fixed in versions 8.1 - 9.1. So if you install the latest update for 8.2 and you're still encountering a problem it is most likely a different bug with similar symptoms.
The release notes indicate it's only fixed in 8.3 and 9.1.
8.3.20083.2074 CLR 2.0, 8.3.20083.2074 CLR 3.5, 9.1.20091.2021 CLR 2.0, 9.1.20091.2021 CLR 3.5
travissmith said: When do you believe this hotfix will be released. The latest hotfix for 8.2 does not show in the fixed bugs that this is corrected. Thanks.
Hey Travis,
That bug (15995) has been mared fixed and closed in versions 8.1 through 9.1. So it should be resolved in the latest 8.2 hotfix. You can also verify the fix by contacting our support department. If you are still encountering problems along these lines then it's possible that you are seeing a different error than the one that was originally reported.