Open Bug 817979 Opened 12 years ago Updated 10 years ago

Mousewheel preferences update for new delta_multiplier values

Categories

(SeaMonkey :: Preferences, defect)

SeaMonkey 2.14 Branch
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: chalx, Unassigned)

References

Details

Now (bug 801101) there are 3 ways to use delta_multiplier_* values (actually percents): 1-999 to scroll faster/slower; ~10000-99999 to scroll exactly one page up/down; 100000+ to scroll full document to top/bottom. Not sure about the last one (home/end option), but pageup/pagedown options are very useful and can not be easily reproduced with keyboard (you need to wait for keypress autorepeat delay or to repeat tapping PgUp/PgDn rapidly). And there were an option to scroll one page in the old preferences dialog. Now there is no such option (regression?) and the percentage fields are limited to input only [+-]1-999 values. It even can't print a large value (>999) already set manually. I think the preferences dialog should be able to setup page (and may be document) scrolling via some self-explanatory options. And for sure it must output correct values without truncation. PS: Tested in SeaMonkey/2.14.1 (20121129230834). mousewheel.with_alt.delta_multiplier_y=9999 already works as pagedown.
Depends on: 782143, 801101
(In reply to chAlx from comment #0) > Now (bug 801101) there are 3 ways to use delta_multiplier_* values (actually > percents): > > 1-999 to scroll faster/slower; > ~10000-99999 to scroll exactly one page up/down; There is no such "feature". Limited the page scroll amount to one page width/height is a feature which had been implemented for a long time. The actual behavior uses this feature for the trick, so, not a feature. Actually, please check the DOM wheel event's delta value with large delta_multiplier values. Then, you do NOT see the delta value indicating a page scroll. So, even if you customize the delta_multiplier values, that notifies web applications of just a large amount scroll. > Now there is no such option (regression?) and the percentage fields are > limited to input only [+-]1-999 values. It even can't print a large value > (>999) already set manually. It's wrong. There is no border line which changes the behavior between line/pixel scroll and page scroll. There is just a border line which enables or disables the one page scroll limit, the value is 100000 (x1000). > I think the preferences dialog should be able to setup page (and may be > document) scrolling via some self-explanatory options. And for sure it must > output correct values without truncation. So, such UI must not make sense. I think that this should be marked as INVA. But if the textbox don't accept the large value, it might be better to increase the capacity.
The textboxes (we have ones for horizontal and vertial) currently do not accept values larger than 999, so at least that needs to be changed AFAIU.
> Limited the page scroll amount to one page width/height is a feature > which had been implemented for a long time. This was internal solidity check. Now end users have to use it to emulate previously existed abilities (due to removed page scroll options in the Preferences dialog). Thus both non-transparent behaviors for this option (exceeding page size and exceeding magic 100000 value) should be reflected in GUI (as additional options or comments to existing form fields). And definitely 999 should be increased.
Depends on: 819644
> And definitely 999 should be increased. I filed a bug to cover this specific issue: Bug 819644 - (Mousewheel preferences) Increase the range for new delta_multiplier values to 6 digits (+/-999999)
Depends on: 819652
No longer depends on: 819644
We had a clear option in the Preferences to scroll one page via mouse wheel. Now we have not. There is a workaround: set large zoom factor to force one page scrolling. I (as reporter) have already knew it from Bugzilla. So let's not care a dime about other users missing the feature (available earlier in prefs dialog). Or let's give them a hint (in the dialog and documentation) how to use an existing option.
You need to log in before you can comment on or make changes to this bug.