405679 - When performing a search on WordPress.org, the search results are not rendered on Vista, effective Sep 29, 2007.

Status: VERIFIED FIXED

(Core :: Disability Access APIs, defect, P5)

Description

[Marco Zehe (:MarcoZ)]

Perform the following steps:
1. With accessibility enabled in Minefield, visit http://wordpress.org.
2. In the Search box, type "trackback" (without the quotes), and press ENTER.
3. After the Search Results come up, use AccExplorer32 to explore the Accessibility tree.

Result: Search results come up, but only the Document Node is visible in AccExplorer, it has no children.

More information:
1. I cannot reproduce this on XP, only on Vista.
2. If I force Minefield to restart (e. g. by disabling or enabling a plugin), while the Search Page is still loaded, after the reload, the Search Page comes up fully rendered. It only fails to render to a11y if I come from the Search box on the WordPress's home page.
3. The regression range is:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-09-28+02%3A00&maxdate=2007-09-29+05%3A00&cvsroot=%2Fcvsroot

Comment 1

[Aaron Leventhal]

Hard to say which of those patches could have affected this.

Comment 2

[Aaron Leventhal]

Marco, I am unable to reproduce this. Can you back out the various patches and figure out which caused the regression?

Comment 3

[Aaron Leventhal]

Marco, it's probably bug 397112. Can you check?

Comment 4

[Marco Zehe (:MarcoZ)]

Another way to reproduce this for me is to simply go to https://bugzilla.mozilla.org, log in, and click the "My bugs" link. The page comes up empty.

I will back out fix for bug 397112 and see if that fixes me.

Comment 5

[Aaron Leventhal]

Same regression range as bug 408997.

Comment 6

[Mike Schroepfer]

Moving to wanted list...please ren-nom if you disagree this should really block

Comment 7

[Marco Zehe (:MarcoZ)]

As documented in bug 408997, that bug and this one both have the root cause in the fix for bug 397112. I am seeing this in far more places than just the WordPress example given, it often hits me in bugzilla as well. Aaron has a handle on the problem, so we should have a fix for beta 3 I think. Re-requesting blocking.

Comment 8

[Mike Schroepfer]

Ok - if that's the case we need a much higher priority on this than P5...

Comment 9

[Jason Bassford]

Fixed by the fix for bug 408997.