Bug 183326 - Scrolling is by cursor
Summary: Scrolling is by cursor
Status: CLOSED NOTABUG
Alias: None
Product: Fedora Legacy
Classification: Retired
Component: mozilla (Show other bugs)
(Show other bugs)
Version: fc3
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Fedora Legacy Bugs
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-28 08:35 UTC by reef_tiger
Modified: 2007-04-18 17:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-28 18:56:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description reef_tiger 2006-02-28 08:35:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060211 Fedora/1.0.7-1.3.fc3.legacy Firefox/1.0.7

Description of problem:
A blinking cusor appears in the wab page. When using the up and down keys, the cursor moves up and down the page line by line. 

Version-Release number of selected component (if applicable):
mozilla-1.7.12-1.3.3.legacy

How reproducible:
Always

Steps to Reproduce:
1.load mozilla
2.visit any web page. click anywhere within the window.
3.use up or down key to scroll
  

Actual Results:  Blinking cursor moves up and down page. Page scrolls up or down only when cursor reaches top or bottom of page respectively. Scrolling is borked.

Expected Results:  Page should scroll imediately

Additional info:

Comment 1 David Eisenstein 2006-02-28 10:23:44 UTC
There is a poorly-documented feature in Mozilla called "caret browsing", which
enables the behavior you are experiencing.  The F7 key toggles this behavior
on and off.  Try pressing the F7 key and see if the browser resumes the normal
behavior.

Comment 2 reef_tiger 2006-02-28 18:56:23 UTC
Yes, that was it. Thank you


Note You need to log in before you can comment on or make changes to this bug.