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 301040 - incorrect range for a selected text
incorrect range for a selected text
Status: RESOLVED WONTFIX
Product: gtkhtml2
Classification: Deprecated
Component: Accessibility
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Rodney Dawes
Rodney Dawes
gnome[unmaintained]
Depends on:
Blocks: 136161
 
 
Reported: 2005-04-18 09:36 UTC by Oana Serb
Modified: 2012-03-31 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Oana Serb 2005-04-18 09:36:45 UTC 
For a selected text in yelp, I get wrong value for the selection range:
-----
CC=18 , CP=4, SS=1
TEXT (0)-(CC=18):About This Article:
TEXT (0)-(-1):About This Article:
SEL[0]-(7)-(25):his Article:
-----

the selection range is between 7 and 25 (SEL[0]-(7)-(25):his Article:), but the
text has only 18 characters (CC=18).
Comment 1 Oana Serb 2005-05-17 07:54:34 UTC 
The wrong value is obtained for the previous object which have the 'flows_from'
relation.
Comment 2 Christian Persch 2005-05-24 11:49:00 UTC 
Does this still happen in the gecko-based Yelp from cvs HEAD?
Comment 3 bill.haneman 2005-05-24 11:57:29 UTC 
Christian: the bug is logged against the accessible yelp, i.e. the libgtkhtml
one.   gtkhtml2 is still the preferred backend for accessibility.

We can transfer this to gtkhtml2 if you like.
Comment 4 Christian Persch 2005-07-03 13:32:17 UTC 
Ok thanks. Yes, this is a gtkhtml2 bug, should manifest itself on every
gtkhtml2-using app. Transferring.
Comment 5 André Klapper 2012-03-31 19:01:18 UTC 
According to its developer, gtkhtml2 is not under active development anymore.

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping - Please feel
free to reopen this bug report in the future if anyone takes the responsibility
for active development again.