After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 452023 - Document text "missing" in FF3
Document text "missing" in FF3
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.19.x
Other All
: Normal normal
: ---
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2007-06-28 20:19 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2007-08-13 02:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Joanmarie Diggs (IRC: joanie) 2007-06-28 20:19:48 UTC
This is a blocking/tracking bug for the following Firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=386235
the <link> tag for stylesheets can cause text in document frame to be inaccessible.

An example of this can be seen when viewing items for sale on craigslist. (Thanks Mike!)  It seems that if you get the <link> tag for the stylesheet just right, none of the document_frame text is accessible/exposed. Text contained within descendants of the document_frame will still be accessible. 

I posted a very simple test case which will hopefully help them get to the bottom of it.
Comment 1 Joanmarie Diggs (IRC: joanie) 2007-07-30 23:38:08 UTC
Kenny posted another example of missing text which I think is another instance of the same bug:

> I'm running Firefox 3.0 on Debian Sid.  Orca version is 2.19.5.
> I'm not able to read the results from a search on 411.com.  Is anyone else having a problem with site?
> 
> If you want to duplicate my exact serch:
> 
> firefox 411.com
> Tab to business search.
> Type Dominos Pizza in the business name.
> Type Huntsville in the city/zip field.
> Select Alabama in the combo box for the state.
> 
> The location and phone number of the results aren't being read in Firefox.
> The same site works fine in elinks.

When the bug we're tracking gets fixed, we should test 411.com as well.
Comment 2 Joanmarie Diggs (IRC: joanie) 2007-07-31 00:02:51 UTC
Mike had emailed me this example of missing text:
http://www.sfgate.com/cgi-bin/article.cgi?f=/chronicle/archive/2007/07/29/SP13R95O71.DTL

I'm not seeing the article in Accerciser either.  Adding it to the test-post-Mozilla-fix list. Thanks Mike!
Comment 3 Mike Pedersen 2007-07-31 00:13:26 UTC
ccing Ginn so he has all the examples to test against.
Comment 4 Joanmarie Diggs (IRC: joanie) 2007-08-07 15:57:30 UTC
Good news:  The blocking bug has been marked as FIXED.  I have just confirmed that it indeed fixes the test case and the example from Mike upon which that case is based (description of items for sale on craigslist).

Bad news:  It would seem something else is going on w.r.t. the missing text on 411.com and sfgate. Drat! :-( 

I am unblocking this bug for now.  Given that the text that's missing is not showing up in Accerciser, I'll undoubtedly be re-blocking against a new bug.  I just need to figure out what's causing the issue and create a new, simple test case for the Firefox guys.  And until I do that, I'm not blocked. :-)
Comment 5 Ginn Chen 2007-08-08 07:34:12 UTC
Joanie, I noticed the text of sfgate is still missing from Accerciser.
It's missing from the a11y hierarchy, but I saw it in DOM inspector, and Orca can read it.

I think it's a bug other than bug 386235.

It would be great if we can have a tiny testcase.

Comment 6 Ginn Chen 2007-08-08 09:20:39 UTC
OK, I found the problem, similar issue as Firefox bug 387347.
https://bugzilla.mozilla.org/show_bug.cgi?id=387347

I'm working on a fix.
Comment 7 Joanmarie Diggs (IRC: joanie) 2007-08-13 02:18:54 UTC
Seems that we're good here.

Note that our only reading the first line of each paragraph in Mike's SF Gate example is another case of bogus character extents.  See https://bugzilla.mozilla.org/show_bug.cgi?id=391991 (tracking with bug #463783)

Because the issue reported in this bug has been fixed, I'm closing it out as NOTGNOME.  

Thanks very much Ginn!