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 114441 - Need visible pref for caret browsing.
Need visible pref for caret browsing.
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: Preferences
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Marco Pesenti Gritti
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2003-06-05 03:28 UTC by Dave Bordoley [Not Reading Bug Mail]
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
implementation (6.00 KB, patch)
2004-01-08 19:14 UTC, Christian Persch
none Details | Review

Description Dave Bordoley [Not Reading Bug Mail] 2003-06-05 03:28:09 UTC
We need a visible pref for caret browsing probably under an accessibility
tab. The always use desktop colors pref could go here as well as a default
style sheet. Of course, ideally these would be global gnome apps, that all
html viewing apps would use.
Comment 1 Marco Pesenti Gritti 2003-06-05 06:51:21 UTC
Why cant it follow the accessibility pref ? I wonder if this is not
done in mozilla itself actually ... it would be odd that their
accessibility depend on an hidden pref.
Comment 2 spark 2003-06-05 12:30:55 UTC
Actually, you can turn on caret browsing in Mozilla by pressing F7.

They don't seem to have much interest in adding a UI for it:
http://bugzilla.mozilla.org/show_bug.cgi?id=165362

...but they are about to add a confirmation thingy:
http://bugzilla.mozilla.org/show_bug.cgi?id=128025
Comment 3 spark 2003-06-05 12:39:05 UTC
Btw, wouldn't it make sense for this to be a global accessability pref
for the whole of GNOME - i.e. if someone wants caret browsing in ephy,
they probably want it in other read only text based apps.
Comment 4 Dave Bordoley [Not Reading Bug Mail] 2003-06-05 13:56:48 UTC
Re:
>Why cant it follow the accessibility pref

I talked with calum about this, and he didn't think that really made
sense (paraphrasing, I'll cc him though for clarification). You might
want to have caret browsing without enabling all the xkb keyboard a11y
features. But piers is right a global pref for this and other a11y
related features would be preferable, but that all depends on more
apps using gtkmozembed, so for now we need something.
Comment 5 Calum Benson 2003-11-26 14:01:59 UTC
Your paraphrasing is correct, from what I remember of our conversation
six months ago :)  The suggestion is purely based on my experience
with Mozilla, though, where I've had caret browsing turned on for
months and never once found it obtrusive, but very useful on the
occasions I've needed it.

Perhaps anyone who's used it more extensively can suggest why we
*wouldn't* want it turned on all the time?
Comment 6 Christian Persch 2003-11-26 14:18:36 UTC
We can't turn it on unconditionally because caret browsing is buggy.
For example http://bugzilla.mozilla.org/show_bug.cgi?id=202157 "caret
mode: spacebar and pageDown/pageUp don't scroll as expected",
http://bugzilla.mozilla.org/show_bug.cgi?id=205846 "caret eventually
gets stuck when trying to scroll with PageDown / PageUp keys".
Comment 7 spark 2003-11-26 14:22:37 UTC
Calum, i think the number of complaints when we did have this enabled 
by default suggests that this isn't a good idea. The main issue to me 
is that if i want to scroll a page with the keyboard, i click 
somewhere on the page and press the Up and Down keys to scroll. With 
caret browsing enabled, the page doesn't scroll until the cursor 
reaches the bottom of the page.

What is the main point of caret browsing? To be able to select text 
with the keyboard? Because you can do that anyway...
Comment 8 Calum Benson 2003-12-01 15:14:41 UTC
It's primarily an accessiblity feature-- without it, you can indeed
select text from the keyboard anyway, but you either have to set the
anchor point using the mouse (no use for accessibility) or by using
incremental search (not necessarily very efficient, and perhaps
impossible if it's just an image you're trying to copy).  And when you
do so, no text cursor is shown until you start making your selection,
which goes against the 508 requirement that focus must be clearly
shown at all times.

The bugs certainly sound like a good reason to make this optional at
least for now though.  (I'd be less inclined to say that interfering
with arrow up/down was a good enough reason on its own... how often do
you really have to scroll a webpage a line at a time from the
keyboard, rather than a page at a time?  Can't say I ever feel the
need myself :)

If you want to give it a keyboard shortcut, it should really go on a
menu rather than in a dialog.  So I'd maybe go for something like a
"View->Selection Caret" checkbox menu item (shortcut F7, for
consistency with Moz).
Comment 9 spark 2003-12-01 15:41:25 UTC
>how often do you really have to scroll a webpage a line at a time from
>the keyboard, rather than a page at a time? 

Well, i use it all the time :) This also applies to scrolling left and 
right. I think it'd be fine to have it as an option though, and aim
for a global GNOME preference (to cover all read-only documents such as 
Nautilus text viewer and GPDF) at some point down the line.
Comment 10 spark 2004-01-08 18:23:46 UTC
Can we at least hook up F7 to toggle caret browsing mode before the 
freeze?

gtkhtml2 now offers this feature too: see bug 123008
Comment 11 Christian Persch 2004-01-08 19:14:00 UTC
Created attachment 23121 [details] [review]
implementation
Comment 12 Christian Persch 2004-01-08 19:15:23 UTC
The patch implements an accellerator-only action (F7) which toggles
the mozilla pref.

Marco: Ok to commit?
Comment 13 Marco Pesenti Gritti 2004-01-08 22:51:32 UTC
Please commit, thanks. Christian please dont block on me with patches
adding features. It's a damn bad period for me so if you send me a
private mail about the patches you want to get in 1-2 days before the
freeze we will be sure to not fail to get them in (I noticed this one
accidentally ...)
Comment 14 Christian Persch 2004-01-09 09:33:03 UTC
Checked in.
Comment 15 Marco Pesenti Gritti 2004-01-26 19:02:15 UTC
IHMO we should close this and just follow what they does on yelp as we
have been doing
Comment 16 Dave Bordoley [Not Reading Bug Mail] 2004-01-26 19:51:35 UTC
what is yelp doing again. My opinion on this is "Whatever makes calum 
and bill happy."
Comment 17 Marco Pesenti Gritti 2004-01-26 19:55:53 UTC
There is an accell. I'm cced on that bug if they add a pref or
something we will see what to do (maybe share or clone ..).