Issue 1267 in dactyl: find-next and find-previous, scroll to middle

2 views
Skip to first unread message

dac...@googlecode.com

unread,
Feb 10, 2015, 2:36:41 AM2/10/15
to dacty...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Project-Pentadactyl

New issue 1267 by livibet...@gmail.com: find-next and find-previous, scroll
to middle
https://code.google.com/p/dactyl/issues/detail?id=1267

I'd like to request for the behavior of <find-next> and <find-previous>:

* an option or
* a permanent change

That would make the hit to be scrolled to middle of screen. Currently, it
behaves like Vim. It scrolls the next hit into the bottom of screen when
press key [n]; or top of screen with [N]; if scrolling is required.

Normally, this works without any issues, however, I find some websites use
overlay bars, that would either stay on top or on bottom. As you try to
jump to next hit, or just start [/] search keyword, the page is scrolled
and the next hit result is unfortunately blocked by the overlay bar.

This is not a bug of Pentadactyl, nor dactyl's issue, to be perfectly
honest. Unfortunately, many websites are designed to use overlay bars.

If you use Firefox's search bar, that's [Ctrl+V][Ctrl+F], the result would
be scroll to the middle of screen, that doesn't have problems, and that's
why I am requesting a workaround. Perhaps, an option that can enable users
to choose where to scroll to, so users don't have to press [Down/Up] just
to awkwardly and annoyingly unveil the hits.

----

:version
Pentadactyl hg7101 (created 2014/07/04 00:00:03) running on:
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

dac...@googlecode.com

unread,
Feb 10, 2015, 2:57:47 AM2/10/15
to dacty...@googlegroups.com
Updates:
Status: Duplicate
Mergedinto: 593

Comment #1 on issue 1267 by dougk...@gmail.com: find-next and
(No comment was entered for this change.)

dac...@googlecode.com

unread,
Feb 10, 2015, 7:02:46 AM2/10/15
to dacty...@googlegroups.com

Comment #2 on issue 1267 by mi...@lazarescu.org: find-next and
This is not the same as issue 593 and should not be merged.

dac...@googlecode.com

unread,
Feb 10, 2015, 11:34:59 AM2/10/15
to dacty...@googlegroups.com
Updates:
Status: WontFix

Comment #3 on issue 1267 by dougk...@gmail.com: find-next and
Rejecting as the reporter insists on a special-case option or undesirable
default behaviour rather than utilizing the long pending "zz" cursor
centering command.

The problem that provoked the enhancement request is generally related to
the unresolved issue 1082.
Reply all
Reply to author
Forward
0 new messages