Middle mouse button scrolling also doesnt work on several computers.

I can confirm this one on a Toshiba P200. Scrolling using the right border of my 
touchpad works only if trying to scroll down. Upwards does not work.

I can confirm this on a HP nx6310, Vista Business.

Testing using a Toshiba Tecra A8

Scrolling up and down works perfectly using the touchpad.

Middle mouse button scrolling does not work.

Desktop with Windows XP
Middle mouse button scrolling is fine, but clicking on it does not bring up the 
button on the screen.
However, clicking on an hyperlink with the middle button does open up a new tab.

replicated on an Asus X50RL XP Pro, downward scroll works fine, but up doesn't work 
at all, dwspite the cursor showing a scroll icon.

I can confirm this on my HP Compaq 6910p, scrolling down just does not work.

Confirmed on Dell Inspiron 1520. I can only scroll down, not up.

(No comment was entered for this change.)

Mal, it appears to be a windows vista problem

Confirmed on custom built Intel CPU/Intel mobo Windows XP SP2 system. Scrolling up 
does not work. ALT + Scroll Wheel works though.

Scrolling works on my Windows XP with a Microsoft Intelleye, however I have Service 
Pack 3....

confirmed on Win XP SP2: middle scroll wheel down works (quirky), up does not 
respond.
scroll down often (but unpredictable) goes down to bottom of page, unlike 
ALT+scrolldown.

Both 'Up & Down' Scrolling works perfectly fine with Dell Latitude D620 running 
Windows XP Professional + SP3.

Confirmed. Scroll wheel scrolls down, not up.
XP SP3
Dell mouse using generic Windows driver

Confirmed. I cant *even* scroll. Not up, or down.

confirmed, i can scroll down, but not up on my Dell Vostro 1500 notebook touchpad.

great browser google, so lets get this fixed!!

Confirmed the same problem with a Dell XPS M1330 with Windows Vista Ultimate

Same issue when using TouchPad, HP dv2000t. Running Vista SP1 with Synaptics TouchPad 
v6.2.

Confirmed on a Dell Inspiron 1520 with Windows XP Pro SP3 - using the touchpad, 
Chrome is only scrolling down (and faster than it should, I'd say), not scrolling 
back up. Using a normal mouse's wheel works fine, still pressing the wheel (middle 
button) won't let you scroll the page by moving the mouse up and down (like in IE).

confirmed on Fujitsu Siemens Amilo Pro. Touchpad scrolling down (extremely fast) but 
not up. also tap scrolling only working down (normal speed) and not up.

Microsoft Windows XP Professional
Version 2002
Service Pack 2

Touchpad details:
Synaptics Pointing Device v8.2.26 21Apr06
Device settings: Synaptics TouchPad V6.2 on PS/2 port

Similar problem.
Dell 1520, running vista business x64 SP1
with built-in touchpad (Synaptics V6.3), Microsoft 5000 Bluetooth Mouse, and Logical 
optical mouse.

If mouse-scroll (in the control panel) is set as several lines, than the mousewhell 
works fine, virtual scroll-up doesn't work, and scroll-down runs almost twice as 
fast.

If set as "one page", than mousewhell actions are inverted and slower, while virtual 
scroll-up has no action, and virtual scroll-down scrolls in the opposite direction.

Confirmed on a HP Pavilion dv6830ed laptop running Windows Vista Home Premium: I can
use the scroll area of the touch pad to scroll down, but not up. (Synaptics touch pad)

Chrome build 1583

Confirmed on a HP Pavilion dv7-1016nr Windows Vista Home Premium 64-bit notebook. I
can scroll down, but not up, and it's using a Synaptics touch pad.

Confirmed on a Dell Inspiron 6400 running Vista Business. Also uses Synaptics touch 
pad.

Confirmed on an HP dv1000 Pavilion
XP Pro, SP3. Synaptics touchpad.

Confirmed on an HP dv2000 pavillion running Vista and Synaptics touchpad.

I CAN scroll on my Dell laptop's touchpad scrollbar, but it's too fast to be useful,
it works almost like a page down, page up deal.

Using the scroll wheel on the external mouse works fine.

XP SP3

Confirmed on Toshiba A105-S2051 laptop with Synaptics drivers.
Scrolling down works, up doesnt work

Confirmed Windows XP on Dell M1330 - just down not up

confirmed on dell xps1320 with vista premium

Confirmed Windows XP SP2 on HP zv6000.
Scrolling down works, a little jumpy but works, up does not.

Confirmed: Windows XP SP2 on Medion MD97600 with Synaptics LuxPad.

Scrolling down works, up doesn't work

Confirmed issue with dell inspiron 6400 running synaptics driver ver 9.x then updated 
to 10.x - both versions scroll down but not up - friend on Dell XPS m1710 running 
syaptics driver ver 8.2.4.6 and scrolls perfectly...

confirmed with vista premium on hp dv6000

scrolling down works
scrolling up does not

I hace an Acer Asipre 4520 and my touchpad cannot scroll. And it's not a vista's 
problem, I'm usin WIN XP!! SP2 and SP3. Cant scroll up! =(

Confirmed on Asus X51RL, Vista Home Premium.

Confirmed on HP G6032 Vista premium.

interesting. in addition to my comment 23 in this thread, the scrolling works 
perfectly when i view full history from the New Tab page. scrolling down goes at the 
right speed and scrolling up works at the same speed as down. the problem still 
persists on web pages though.

[CONFIRMED]

confirmed for Inspiron 1520 running Vista.

I can confirm exact events described in comment 42.

comfirmed for Comapq Presario F700, trackpad- I can scroll down but not up

last addition to this thread. the same problem exists with left - right scrolling 
using the edge of the touchpad. it scrolls to the right extremely quickly and doesn't 
scroll left at all. i can't confirm if left right scrolling works in the full history 
(comment 42) because no matter how narrow i make the history tab, no horizontal 
scroll bars appear.

Confirmed with Acer Aspire 5630. I can scroll down but not up.

It is very annoying as using the scroll buttons has become a habit over the years. 

confirmed with HP Pavilion Entertainment PC. Scrolling up with touchpad impossible.

Confirmed with Asus F3jc, Windows XP pro sp3 with Synaptics drivers version 6.1.

Offtopic: Cool, I can resize the text box.

Confirmed Gateway CX2726

poop

Confirmed Dell Inspiron 1520.

Synaptics Touchpad.

Confirmed HP Pavillion dv6500
Vista Home Premium

Confirmed HP 8710p
Windows XP SP2

Works down but not up.

Looks like it's related to Synaptics TouchPad.
C:\Program Files\Synaptics\SynTP

right and left click are fine and touch pad is fine too
but scroll up using the side of touchpad does not work but scroll down works but way 
too fast.
Laptop: hp pavilion dv6000 running Windows Vista

right and left click are fine and touch pad is fine too
but scroll up using the side of touchpad does not work but scroll down works but way 
too fast.

using only CHROME...rest of apps and firefox and IE are working fine.

Laptop: hp pavilion dv6000 running Window Vista
using Synaptics Pointing Device 

It seams to be Synaptics only. I'll try it out on my mums laptop tonight, it has a 
alps touchpad.

I thought I just needed to restart a little later tonight...  Confirmation from Vista 
Home Premium 32-bit on a Dell Inspiron 1318.

Definitely a Vista issue. Same as 56. Homemade with XP Pro works.

I can confirm this on a Dell Inspiron E1505, Vista Home Premium.

Synaptics PS/2 Port Pointing Device
Driver provided: Synaptics
Driver date: 11/6/2006
Driver version: 9.0.1.3
Digital signer: microsoft windows hardware compatibility publisher

HP Pavilion DV9910US (17" HP Notebook) using Synaptics Touchpad v6.3;  Windows Vista 
Home Premium;
Touchpad scroll works downward only and will not scroll up.

HP Pavillon dv6000 also has problem of scrolling down and not up incredibly 
frustrating and tedious!

confirmed bug running on windows xp pro , using a Toshiba a135s4467, with touch pad Synaptics v 6.2

scroll goes down but not up... III

Bug also confirmed on my laptop: Synaptics version 8.3.8.0 on a Compaq Presario C3000 
running XP Home SP2.  Downward scrolling works fine, upward scrolling does not work.

Synaptics TouchPad v6.3 on a Toshiba Satellite notebook running Vista (32bit)

Same exact problem all others are having. I can scroll down but not up.

Confirmed.

Dell XPS M140.... Scrolls down, but not up!

Confirmed on Acer Aspire 5100 that scroll toggle or mouse pad up does not work...down 
fine....using Windows Vista

Confirmed HP 6510b
Windows XP SP2

Touchpad:
Works down but not up.

Mouse:
Middle click, not working at all.

Occurs on my work HP Compaq 8510p running XP Pro. Works on mouse with scroll wheel 
when attached to dock - but scroll up does not work on touchpad.

Same problem with Synaptics PS /2 Port TouchPad on a hp dv6338 ....scrolls only down 
and NOT UP!

Confirmed on Acer Aspire 6920g with Windows XP. Scrolling doesnt work from touchpad. 
But i can use wheel of usb mouse for scrolling.

And there is no easy-scroll mode when i click wheel of usb mouse. with other 
browsers, when i click wheel, a up-down arrow icon appear on screen and i can scroll 
only moving mouse.

Confirmed here. Dell Inspiron 1501, Vista HP 32bit. Cannot scroll up with touchpad,
only down, and that seems like a page at at time.

same problem, on dell inspiron 6400. OS: vista
scrolls only down very fast, and NOT UP!

Confirmed on Dell Inspiron 1521 running Vista. Scrolls down quickly, never up.

confirmed Acer Aspire 5102 with synaptics touchpad

Problem confirmed on HP Pavilion dv9601AU with synaptics touchpad. Running Vista Home Premium 32bit with SP.

Checked on my mums laptop with a Alps touchpad.

Can scroll down and up, but it goes way to fast.

Windows Vista Business, Alps Driver version 7.0.1301.2

Problem confirmed on my Lenovo laptop with synaptics touchpad on Win XP SP2.

Confirmed for my Dell Vostro 1500. Right border allows downward scrolling only. 
Middle-mouse button scrolling is also non-functional.

Confirmed for HP Compaq nx9420 with Synaptics Touchpad V6.2 (driver version 10.2.4)
Windows XP PRO

no scroll up.

Confirmed.
Scrolling up with Synaptics Touchpad on Toshiba L40 not working on Windows XP SP3.

Confirmed for my HP Compaq 6510b, scrolls down only.

Confirm with MSI Wind U100 Netbook, also horizonal scroll not working either.

Same thing happening with my synaptics touchpad on my dell vostro 1500.

Scrolling works but is far too fast on my laptop.
Model: Sager NP2092
Motherboard: JFL92 IFT00
Mobo chipset: Intel PM965 rev. C0
Southbridge: Intel 82801HBM (ICH8-ME)
Elantech Touchpad (Drivers: 5.0.3.13 dated 2/13/2007)

Bug is present on toshiba A200-PFA6A running windows vista home premium

Confirmed on HP Pavillion dv2000. Vista 32-bit. Snynaptics Touchpad.

Scrolling down works, but scrolling up does not.

Bug confirmed on Acer Aspire 9301AWSMi. Vista 32-bit. Synaptics Pad. Down works, Up
doesn't work.

Confirmed on a MSI wind u100

Confirmed on a VISTA Ultimate ACER 6920G.

Great browser by the way, keep up the good work google!

Confirmed on Acer TravelMate 6292, mouse driver Synaptics v10.1.8 06Dec07

I can confirme the bug too. It looks like it is the Synaptics Pad.

Synaptics Pad
WinXP SP3
HP dv6153eu Notebook

The bug exists while using Dell Inspiron E1505.

Problem only when using Synaptics touchpad for me. When USB mouse is used it works 
perfectly fine :)

Confirmed on Asus F5R with Synaptics drivers, XP Pro SP3.

This problem happen in Google Talk Client too.

Can confirm I have the same problem on my "HP Compaq 6715b" on Google-Chrome. The
mouse scroll pade works fine going down (it's a little fast though) and does NOT work
scrolling up.

Confirmed on Lenovo 3000 N200. Scrolling down works, scrolling up doesn't.

Confirmed. Synaptics touchpad, HP Pavilion dv9312eu.

Also confirmed for HP Pavilion dv2173ea with a Windows XP with SP3.

Also exactly confirmed for Medion MD 96290 Laptop running XP

Reproduces on Dell XPS M1330 with Synaptics touchpad drivers (masked as Dell Touchpad 
Driver v 10.1.2). Windows Vista Business Rus SP1

Confirmed on my Dell XPS M1710 with Synaptics touchpad drivers.
Windows Vista SP1

Confirmed, HP dv8000.

Synaptics touchpad. Scroll up doesn't work - works fine in every other application
including zoom in for games and scrollbar for Firefox, Windows XP SP3, etc.

Confirmed on ASUS M50SA

Vista SP1

Synaptics Touchpad.
Scroll up doesn't work

Confirmed, MSI Wind U100

Confirmed on my Dell Inspiron 1520. Works perfectly with FF3 just can't scroll up 
with Chrome.

I was just about to report this.  it does not work on the HP tx2000 eithier.

Doesn't scroll up on an Acer Aspire 5670 series.

HP NW8440, latest synaptics driver.
Scroll down via right-side of touchpad in Chrome is too fast and it does not scroll 
up at all.

It works on my Dell Inspiron 9400 notebook, with the latest Synaptics Driver

Confirmed on Compax NX6125, Windows XP SP 2

Touchpad scrolls down much faster than middle button on the mouse, up doesn't work at 
all. Middle button scrolls without a problem, middle clicking does nothing.

I have the same problem on my packard bell with windows xp sp2

Confirm: cannot scroll up on web page/source view.
hp6510b, Windows XP SP3, Synaptics Touchpad

Confirmed on Dell XPS M1330 and Win Vista SP1 (latest synaptics drivers):
Srolling down with touchpad is too fast.
Scrolling up with touchpad doesn't work.

Confirmed.  Cannot scroll up with the touchpad on a Gateway MX8738, Windows Vista 
Home Premium.

Dell Inspiron 1420, Vista 32bit Home Basic

Unlike some, I can scroll up and down with touch pad. Like other users however, it is 
far too fast. Only usable on very long pages (such as this one).

Confirmed Acer Aspire 5610Z, Synaptics Touchpad V6.2, Vista

Acer Travelmate 5720: Touchpadscroll down faill confirmed (XP pro 32bit)

Confirmed again. Scroll wheel on USB mouse works as expected. Touchpad works when 
scrolling down but not when scrolling up.

Confirmed on Dell Optiplex 745 with Dell optical 5 button mouse. Autoscroll doesn't 
work either.

Confirmed on Toshiba Portege M600. Scrolls down but does not scroll up.

Confirmed on HP Compaq 6715s Scrolls down but does not scroll up.. using touchpad

Confirmed. Scrolling down is too fast and up does not work at all on a dell vostro
1500 running Vista business sp1 (32) with synaptics touchpad driver 9.1.18.6. 

Same here on my Acer Nb.

Scrolling down is arguably too fast, and scrolling up does not work at all. Dell 
Inspiron 1520 / Vista Home.

(No comment was entered for this change.)

Confirmed, Synaptics touchpad only scrolls down.

It seems to work on pages with frames, though.

I have fixed this problem on my computer.  I had similar issues in that I could 
scroll down, but not up.  Holding Alt would allow me to scroll upwards.

I was using a generic Microsoft USB Optical Mouse.  Intellipoint version 4.00.0657.  
Issue was resolved by going to Control Panel, Mouse.  Under the Wheel tab, Advanced 
under Wheel Troubleshooter, adding the Chrome executable (i.e. chrome.exe) to the 
list of exception software resolved my issue.

Since disabling the IntelliPoint wheel software implementation fixed this issue, it 
seems that IntelliPoint (at least on this version) conflicts with some calls being 
made by Chrome, as Chrome provides its own wheel implementation without taking into 
account outside software.

Change in issue confirmed using Synaptics touchpad, driver 9.1.3.0 on a Gateway.

Bug reproduced on Synaptics TouchPad v6.2 Software version 10.2.4 18Jan08 running on 
Windows XP SP2, HP Compaq nw8440.

Confirmed for synaptics touchpad 6.3 on a Compaq laptop.  Software version 10.1.8

Confirmed for HP Pavilion dv6253cl (dv6000 series), with Synaptics touchpad 6.3. 
Running Windows XP Professional SP2 32bit.

[CONFIRMED] On my work coputer (simple Lenovo mouse, no additional drivers). On my 
home it works (Logitech MX Revolution).

Confirmed, using Synaptics TouchPad V6.3 on Acer Aspire 6920, running Vista Home 
Premium SP1.

Confirmed for HP Pavilion dv6911 us Entertainment Notebook PC

It does the same on my laptop:
Compaq Presario V2000
Vista Ultimate (SP1)

Confirmed for HP Pavilion DV 6560EL, cannot scroll up with Touchpad

Confirmed with Logitech optical mouse and IBM ThinkCentre

Confirmed with:

Lenovo ThinkPad T61
Windows XP
Wired Lenovo Optical Mouse

don't work with: 

lenovo version 5.11
windows xp
optical mouse

Confirmed on Acer Extensa 4420 [vista] - both on side-of-touchpad and on the quick
scroll buttons

Confirmed on my Compaq 6715s

Confirmed with:
Dell Inspiron E1705
Windows Vista
Synaptics Touchpad

Confirmed on HP Pavillion dv9000 laptop.
Windows Vista
Synaptics touchpad
Scrolls down but not up.

Confirmed on a Lenovo 3000 N100 laptop and a Dell Vostro 200 desktop (with optical 
scroll wheel mouse).
Both running Windows XP SP2.

same problem with hp dv2109tx (synaptic touchpad) window xp

Confirmed on:
Compaq Presario v2406
Windows XP Professional SP2
Synaptics (Driver Version 10.1.8.0)

Scrolls down but not up. Scrolls down on full history.

Windows Vista Home Professional 32b, desktop
AMD Athlon 64 X2, MSI mobo
Commodore mouse
Wheel scroll ok, middle button scroll doesn't work

Confirmed on:
HP dv5000t
Windows Vista SP1
Synaptics touchpad - driver version 10.0.13.2 (9/14/2007)
Scrolls down but not up; scrolls down too fast.

Confirmed, Gateway m 6862 with synaptics touchpad on vista x 64 with latest gateway
synaptics driver 9.1.3. Tried newer generic driver to same problem. Scrolls down
REALLY fast but not up at ALL.

Not just synaptics! I have a sony TZ195 running Vista Business 32... Scrolling either
direction is TOO FAST, like it's super sensitive.

^^^ Sorry, forgot to add: that's an ALPS touchpad.

Confirmed on my HP notebook with synaptics touchpad.  down goes really fast, up 
pretends but doesn't do anything.  Hope this is fixed soon.

Thanks

Toshiba A100 with Synaptics on Vista Ultimate. Scrolls down but not up.

Confirmed on a Compaq HP 6000n with newest synaptics driver on Windows XP, SP3

confirmed on acer 4520 on windows xp sp2, using touchpad, scroll up not working

Confirmed on a Compaq 6720s running Windows Vista Premium.

confirmed on acer aspire 4520 windows xp sp2...
I think it's the synaptic touchpad...

I can confirm this on HP Compaq 6910p with XP SP3. Down works, up doesn't.

Confirmed on a Dell Optiplex 745 with XP Sp3 and Dell mouse. Out-of-the-box setup and 
drivers as it came from Dell. 

confirmed on LG M1 Express Dual with Vista Business SP1.

hp compaq nc8430 with synaptic touchpad driver 10.2.4.0 doesnt work.

Using an original Microsoft Wireless Intellimouse Explorer (that is the first version  
hardware not 2.0, 3.0 or 4.0) with Microsoft IntelliPoint 4.1 software that was 
supplied with the device. I am unable to scroll up although the customised middle 
button click triggers F5 keystroke to initiate a page refresh. Running XP SP3 on 
Lenovo T61 ThinkPad. I can't upgrade to a more recent version of the IntelliPoint 
software (currently 5.5) as my mouse is no longer correctly supported since version 
5.0. Unless this issue is fixed within Chrome I would have to replace the mouse to 
resolve the problem.

Confirmed on Asus-U6E series laptop that also has Synaptics Touchpad. I downloaded
the latest driver from their site last night and it still didn't help.

confirmed on Dell 6400 
windows server 2008
synapics  v 6.2

Confirmed on HP/Compaq nx6325 (Synaptics touchpad, Win XP/SP2).

Confirmed on Lenovo ThinkCentre Desktop with Windows XP SP2 and Lenovo USB Optical 
Wheel Mouse (MouseSuite 5.02.2): middle scroll wheel works on down (quirky, jumping), 
but up does not respond. The same with Automatic Scroll.

scrolling works after alt+scrolling once

I have the same problem. Gateway Laptop Windows vista home premium

Reposting the solution that worked for me, since it got buried amongst the useless 
"+1" posts:

I have fixed this problem on my computer.  I had similar issues in that I could 
scroll down, but not up.  Holding Alt would allow me to scroll upwards.

I was using a generic Microsoft USB Optical Mouse.  Intellipoint version 4.00.0657.  
Issue was resolved by going to Control Panel, Mouse.  Under the Wheel tab, Advanced 
under Wheel Troubleshooter, adding the Chrome executable (i.e. chrome.exe) to the 
list of exception software resolved my issue.

Since disabling the IntelliPoint wheel software implementation fixed this issue, it 
seems that IntelliPoint (at least on this version) conflicts with some calls being 
made by Chrome, as Chrome provides its own wheel implementation without taking into 
account outside software.

On My Acer Aspire 9300 using the touchpad and scroll buttons I can go down but not up 
also I can go right but not left

Thank you moderator

Microsoft Optical Wheel MOuse would not scroll up, only down, on my Dell Dimension 
running Windows XP Home.  Microsoft Intellimouse is installed.  Opening the Wheel 
troubleshooter in the Mouse Properties Window of the Control Panel and following the 
steps there resolved the issue on my computer.  The following explanation was given.

IntelliPoint added this program to the list in the Wheel Troubleshooter Advanced 
dialog box.  The Advanced dialog box lists all programs turned off in the 
IntelliPoint software.  
See the Microsoft Pointing Device User's Guide for instructions on using the Wheel 
Troubleshooter Advanced dialog box.

I can confirm on my HP dv6000 series that I can scroll down but not up.

confirmed on my hp dv5030 running stock XP Media

sorry. stock as in up to date with stock OS.  All HP updates and MS updates about my
hardware

I can confirm that bug.

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

After 100's of MeToo's, we all now know that this bug is there, for a lot of 
different hardware profiles.

"Starred" people are not interested in every individual name and case and receive a 
mail about it. Only create comments when you REALLY have something informational, 
which is not mentioned before! The "star" is the way to say "I can see this as well" 
or "I am interested in new development". 

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

confirmed

When the find bar is selected, scrolling up works for me (strangely), however when it
isn't selected I cannot scroll up.

188 doesn't work for me - mine still fails to scroll up (or down when the find bar is 
selected)

Confirmed on a Dell Inspiron E1705 with Vista Home Premium. The touchpad scrolls down 
but not up. My wireless USB mouse scrolls both ways no problem.

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

After 100's of MeToo's, we all now know that this bug is there, for a lot of 
different hardware profiles.

"Starred" people are not interested in every individual name and case and receive a 
mail about it. Only create comments when you REALLY have something informational, 
which is not mentioned before! The "star" is the way to say "I can see this as well" 
or "I am interested in new development". 

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

lol... i wanted to report this bug but it looks like the other 5000 people using 
touch pads beat me to it... like comment 191 though... thought that would have 
happened sooner.

present! same thing here in HP520 touchpad.
plus another issue is its scrolls TOO FAST!

Confirmed for a HP Dv5 using synaptic touchpad driver. Fix please.

Another thing about the scrolling -- it doesn't scroll the correct amount of lines & 
if the scroll wheel option in XP is set to "One screen at a time" then it goes 
backwards!

http://spreadsheets.google.com/pub?key=piEywtesotIPC4Q7mScNUWA&output=html

Confirmed on HP 6710b Vista 64 - scrolls down and not up using touchpad (synaptics)

Confirmed. HP Pavilion dv9266ea. Vista Home Premium. Synaptics touchpad.

Also fails on HP Compaq nx6325 under Windows XP SP3 32bit

Is there anyway to close this thread to stop people posting confirmations? I don't 
want an email everytime someone with a laptop discovers chrome, i want to know when 
something happens about it!

--NO MORE CONFIRMATIONS PLEASE. WE KNOW THERE'S A BUG!!!--

@rjw.pope: you were comment 189.  --WE KNOW THERE IS A BUG!!-  
gee whiz your'e a fool.

Confirmed Its a bug with HP Pavillion dv6000

Confirmed 3 days ago, but just thought I'd add mine to the list.

Synaptic Touchpad. Dell Precision M90.

This is a confirmed bug which I noticed the first day Chrome was released (can 
scroll down but not up).
But what is ALSO an issue (which I haven't seen mentioned) is if you turn on 
horizontal scrolling (right/left) on my Synaptics TouchPad it will only scroll right 
and then not scroll back to the left.
Please add this to the bug list if possible.

Confirmed with HP tablet: Pavilion TX1000 series. Scroll space on touchpad scrolls 
down but not up.

The same problem is confirmed on:
Acer Aspire 5610   
Vista SP1
Touchpad Synaptics

well, a new beta was released tonight, but that bug was not fixed :(

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

Click the Star at the top if you want to confirm.

@plamenkatev of course not, that is why the bug report is still open.

Scrolling up and down via rolling the scroll wheel work ok for me, but an unable to 
click the middle mouse button for continuous scrolling

Thinkpad T60, Windows XP, Microsoft wireless notebook optical USB mouse

confirmed + I also see this + '+1' 
on acer aspire 5570
thanks

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

Google Chrome has been updated to version 0.2.149.29.

Problem still remains (can't scroll up and too fast down).

Comment 42 is true for me too:
"interesting. in addition to my comment 23 in this thread, the scrolling works 
perfectly when i view full history from the New Tab page. scrolling down goes at the 
right speed and scrolling up works at the same speed as down. the problem still 
persists on web pages though."

Confirmed on Acer Extensa 4620 model. Running Vista Home Premium.

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

Confirmer. I also see this. +1
;-p

I can comfirm this on compaq presario f500

Confirmed on my Lenovo T61 laptop - running Windows XP SP3

Confirmed on Dell latitude D630 / T7500 @2.2Ghz w/ 32-bit XP SP2

Confirmed on HP Pavilion dv6233se running 32-bit XP Pro SP3 w/ Synaptics TouchPad 
v6.3 running driver v11.1.21.0

I can confirm this on my Acer Extensa 5420. It goes down, but not up. It only happens 
in Google Chrome, no other applications have this problem. 

I have Synaptics PS/2 Port TouchPad driver version 9.0.1.0 and I'm running Windows 
Vista Ultimate 32-bit SP1.

Confirmed on a HP dv5 1060 with vista premium x32

Same problem on an Acer Aspire One, running xp sp3

Confirmed on a Acer Extensa 5620Z, running Windos Vista Home Premium

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

Just star it. WE KNOW IT DOSNT WORK!!!

I just wish you would stop telling people to stop it. It's not about the fact that
they _know_ it doesn't work. It's about narrowing the issue to where and why it's
happening. The only way to do that is to let them know what it doesn't work with.

It dosnt work that way. We know now that its comfirmed. You can just star it. As of 
now, we know their is a bug and its been assigned. So sit tight and wait for a fix. 
No need to further tell us that their is a bug. We KNOW

Confirmed on Toshiba A135-S4527 using Synaptics touch pad.

If using a mouse with scroll wheel it works fine.


Information like people are posting here is helpful for developers, like mmihajlovic
said it helps developers narrow down the bug.

Confirmed on Dell/Intel Core 2 Duo.
Dell mouse model R41108
Using WinXP SP2 with "Dell Mouse Suite" installed.  Mouse suite allows for scroll 
speed, which seems to affect the downward scroll speed (too fast actually), but 
upward is always at zero.

Tried it on several HP laptops running windows XP, all have the same problem.

Confirmed on Acer 5611 awlmi using Synaptics touch pad.

Confirmed issue on HP Pavilion dv6835nr, Synaptics touch pad.
Windows Vista Home Premium.

Also confirmed on XP SP2 and XP SP3 on Acer Travelmate 8200 (8204) with Synaptics 
touch pad.

Confirmed comment 42 on Vista Home Premium 32-bit.

Mr affan do you know if they identified the exact problem and do u have any idea when 
the fix will be available.

Is there any laptop / touchpad with which scrolling does work?

> Is there any laptop / touchpad with which scrolling does work?

Yes, laptops with alps touchpads... but scrolling is a bit fast.

So the issue is with Synaptics driver+GC (And possibly others)?

(Scrolling is wrong on a regular desktop too)

http://spreadsheets.google.com/pub?key=piEywtesotIPC4Q7mScNUWA&output=html


>>
>> Is there any laptop / touchpad with which scrolling does work?
>
> Yes, laptops with alps touchpads... but scrolling is a bit fast.
>

I'm not sure about this, as my laptop has been sent off for repair and I can't test 
the theory, also I'm not a windows programmer. 

I think the synaptic drivers don't use the standard windows scroll wheel interface, 
but instead send scrolling events directly to the window, this allows the driver to 
chose between sending the events to the active window or the window under the wheel 
which windows doesn't natively support.

Confirmed on HP/Compaq 6910p, Synaptics Touchpad v6.2 (on PS/2 port 3), Synaptics 
driver version 10.0.13.2, Windows XP SP2

If anyone else with this problem has Dell Mouse Suite running, try closing it.  That 
fixed this bug for me.

signal to noise ratio approaching zero here - how about someone closing this bug and opening a new one with 
explicit directions in the bug to NOT POST +1's etc.  

otherwise, well, i hate to say it but all these blatantly annoying people make me want this bug to never be fixed 
- i want it to annoy them forever.  i feel like i'm reading the comments to a slashdot post about religion.  -bleh-

@Ajundi: No, I am not sure when this will be fixed. I have a feeling that there might
be a update release from Synaptics to fix their driver issue IF that is the case as
PhireN points out.

Confirmed on HP Compaq nc6220. Scroll down works and scroll up does not works :(

Some quotes:
"The only way to do that is to let them know what it doesn't work with."
[...]
"Information like people are posting here is helpful for developers, like mmihajlovic
said it helps developers narrow down the bug."

I agree, but there is a limit! Do you really think any developer is going to read 
200+ post with every computer configuration possible to narrow the bug? That is just 
not true, I can know: I am a developer.

People just annoy the rest of the people who starred the bug and is working 
CONTRAPRODUCTIVE. Real important messages are being flood by people like above. 
I just disabled email all together, got tired of the massive amount of spam this bug 
generated.

SO PLEASE STOP POSTING COMMENTS UNTIL A DEVELOPER IS ASKING FOR MORE INPUT OR YOU 
HAVE SOMETHING _REALLY_ INTERESTING TO MENTION!

What he said.

Downward scrolling not working on Asus g50v A-1.

also cannot scroll up on an acer extensa 5420

Works fine on a Vaio Laptop. The only issue is the touchpad scrolls too much per 
scroll.

I'm sorry but these spam post saying

-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --
-- PLEASE STOP POSTING "CONFIRMATIONS" OR "I ALSO SEE THIS" OR "+1"'s --

are the MOST counterproductive at all, follow your own advice and post something
useful or don't post at all.

^so you basically just contradicted your self. It is useful. I have starred this to 
show that this issue needs to be taken care of. 

If you have any idea whats wrong, or can provide a code snippet, or debug the 
problem, by all means reply. but replying with useless comments (which the developer 
obviously does not need) is a waste of my time and email space.

I am testing on Windows XP with:
- A plug-and-play USB mouse, listed as "HID-compliant mouse" in Device Manager, with
Microsoft driver version 5.1.2600.0.
- My touchpad, listed as "Alps Pointing-device for VAIO", with Alps driver version
5.3.511.2.

With the USB mouse, if the Windows mouse-scroll setting is "One screen at a time" (my
preferred setting), it only scrolls one *line* at a time, and the scroll directions
are inverted.  (i.e., up is down and down is up.)  If I change the Windows setting to
"scroll N lines at a time" (where N is a number), it works correctly.

With the touchpad, if the Windows setting is "One screen at a time", it doesn't
respond at all.  If I change to "N lines at a time", it responds, but it scrolls N
times the distance the USB mouse does on the same setting.

Confirmed: Win XP - SP 3
The scroll up never works on synaptic touchpad

windows vista. synaptic touchpad. scroll up does not work  on side scroll of 
touchpad.

Confirmed on a HP Pavillion dv9000 running vista ultimate.

Synaptics Touchpad Edgemotion panel scan scroll down, but not up
Confirmed on Vista SP1 with several HP Pavilion notebooks

Same with HP Laptop Touchpad + Windows XP. Scroll down is OK but not going up.

Confirmed with HP Pavillion dv2000 running vista home primium....
scrolling only downwords. scroll up does not work  on side scroll of 
touchpad.(synaptic touchpad)

Same issue on HP Pavillion dv9628nr running Windows Vista. Can only scroll down using 
touch pad but NOT up!

Confirmed on an Acer Aspire One running Windows XP Home SP3. Touchpad scrolls down 
but not up.

Is there a way to up the priority on this? Seems to me like this is a pretty big 
deal; Laptop users' browsing experience are seriously hindered by this bug.

Confirmed with HP Compaq 6820s

Confirmed on Toshiba Satellite A105-S4001 windows xp home. Touchpad scrolls down but 
not up.

:)))))
Just do this in this blog's software:(pseudo)

if Assigned(case):
   while(posts.end):
      if post.find('confirm') > 0 Then
         DiscardPost(post)
      else:
         # added for more robustness
         if post.find('+1'):
            DiscardPost(post)

You should be pleased, I have not seen any customer like this. Someone even gave
his/her graphic card model:)))

b/1368021

We know this is a bug and a fix is in the works 
(http://codereview.chromium.org/2878). 

I'm going to mark this read only to prevent further confirmation and 'me too' 
messages. 

(No comment was entered for this change.)

I still have this problem , scrolling does not work up or down on most web pages.
The exception is the history results page of chrome itself , where the the pointer 
jumps to the scroll bar moves up or down as required and then jumps back to the web 
page. I have the synaptics touchpad. 

@joseph.f.brennan:

This problem has been fixed for Dev Channel releases and has been for the last 2 Dev 
Channel releases.  The problem will probably be fixed in the next standard Chrome 
release, which I unfortunately have no idea of a date for when it will happen.

am i right in assuming that when it is included in a standard release that this topic
will post notification?

Yes, I am pretty sure this will be updated and in some way closed once it is included 
in the standard release.

Hi does anyone know how i can get the latest code? I am new with SVN and stuff so I 
am also looking for a tutorial as well.

Thanks

I have not been doing anything with the actual code, but I do know that if you click 
the Tools button (the wrench) in Chrome and click "About Google Chrome" it will check 
for and install the latest build of Google Chrome.  Also, somewhere there is a 
download for chromechannel-1.0 which will change you from the standard Chrome channel 
to the Dev Channel if you want, which receives updates earlier and more frequently 
(ie. we already have the fix for this bug).

App to update to the latest Dev builds as they are released:
http://chromium.googlecode.com/files/chromechannel-1.0.exe

I have done this, and it is working fine. No issues as far as I can see.

Google Chrome: 0.3.154.3 (Official Build 3339)
WebKit: 525.19
V8: 0.3.4.1
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19
(KHTML, like Gecko) Chrome/0.3.154.3 Safari/525.19

Yes, that is the latest Dev build.  http://googlechromereleases.blogspot.com

it is still not fixed.... i m facing this from the first day... this sucks.. :(

works fine on 0.3.155.0

I never tried a Chromium release or the dev-channel releases. A clean install of 0.3.154.9 and I see the problem is fixed. (WinXP x64)

Fixed in 0.3.154.9 noticed it this morning.(HP 6510b)
Thank you!

As reported by my brother : scrolling issue NOT fixed by 0.3.154.9 :(

He tells he tried different mouse drivers without success. He adds : how is it that 
no app (other than Chrome) has problems with wheel scrolling ? (Me: maybe is Chrome 
multi-platform and using diverse pieces of open source not optimised for/correctly 
tested on Windows ?)

Please look into this issue very seriously lest Chrome's inadequacy to address real 
problems became a joke. (Yes there are many problems with the rendering engine too)

Regards

-- 
Czerno

@nimbux

The synaptic drivers do scrolling in a unconventional way, and other apps do have
problems.

However synaptic releases driver updates to work around the problems when they
happen, but they haven't had time to release a fixed driver for chrome yet.

@282 (PhireN) : I'll be gathering /full/ details (hardware, OS and drivers  
versions...)  & report. Postponing answer till then. Thanks for your reply though. 

Fixed for me in 0.3.154.9 . I have an Asus U6E with the Synaptic touchpad. For those 
of you who haven't seen it fixed yet, make sure to manually go to the About window 
and check for updates. That is how I got mine fixed. Thanks Google!

nimbux:

It'd help if we can get information about the hardware and software installed so that 
we can try it out in-house to reproduce it and make a fix.

Also, please note that sometimes Chrome needs to be restarted in order for the update 
(to the latest version) take effect. 

Amit, my brother just answered my query : 


- Windows XP SP3 OS. 
- His mouse is IBM (Lenovo) model "MO3280"
- drivers, according to Windows driver mgmt app : mousclas.sys et mouhid.sys
- version 5.1.260.2180

- symptom : wheel scrolling down, not up.

I'll have him restart and check for Chrome's reported version number and more precise
machine details (it's a desktop comp, not a portable). Unfortunately won't be until
tomorrow, please stay tuned !

So, his Chrome is confirmed up to date (0.3.154.9)
Mouse drivers (HID) mouseclas.sys 5.1.2600.5512(xpsp.080413-2108) and 
mouhid.sys 5.1.2600.1(XPClient.010817-1148)

The machine itself is an unspecified ACER desktop with AMD 64-dual core processor.

HTH...

Last minute... *** RESOLVED **** 

The mouse still had to be unhooked from the USB, then hooked on again. Scrolling both 
up and down now, works as designed  :=)

Does the above reported voodoo make any sense, considering the machine had been 
rebooted several time without repairing the problem ? 

Case closed anyway as far as we're concerned, and hopefully for all the others too !

Lenovo HID mouse, has the same problem, can't scroll up!

Is there a regression bug with this issue again ? After updating to the latest
0.4.154.22 (dev channel)... Brother's USB mouse won't scroll up  :-(

This time unplugging/replugging it does NOT cure the problem.

I respectfully suggest a complete top-down (or would it be bottom up ?)
reexamination/rework of the mouse scrolling in Chrome under Windows !

Sometimes redoing things from scratch has not been a loss of time in my (old) experience.

Regards


-- 
NimbUx

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=9953 

------------------------------------------------------------------------
r9953 | idanan@chromium.org | 2009-02-18 10:55:46 -0800 (Wed, 18 Feb 2009) | 2 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/tabs/tab.cc?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/tabs/tab.h?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/tabs/tab_strip.cc?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/tabs/tab_strip.h?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/custom_frame_window.cc?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/custom_frame_window.h?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/event.h?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/root_view.cc?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/view.cc?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/widget_win.cc?r1=9953&r2=9952
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/widget_win.h?r1=9953&r2=9952

Solved 2 bugs which caused Chrome to maximize itself whendouble clicking, either on the new tab button, on the closetab button or on a single tab.BUG=2827BUG=3787The problem comes from the Windows event sequence upon adouble-click (simplified here):1 - hit-test2 - mouse-down4 - mouse-up/click5 - hit-test6 - mouse down7 - mouse up/double-clickThe 1st hit-test is always performed correctly, returningclient for tabs and non-client for the tab-strip (background).The 2nd hit test is not performed correctly to avoid crashesin Chromebot from events being processed while tabs are animating.Since we have no record of these crashes, Ben prefers we keepthis special-case, even though we are responding incorrectlyto the windows hit-test. So, when the tabs are animating wereturn a HTNOWHERE hit which the caller translates into anHTCAPTION hit. This even though a tab-control (new-tab/close-tab)may have been hit.The problem is that having returned HTCAPTION to Windows defaultmessage handling, we get a NON-CLIENT double-click event insteadof a standard one.To keep the behavior of the second hit-test AND prevent theChrome window from maximizing, this change simply declaresthe non-client double-click as handled when the tabs areanimating.Another trick we pulled in the hit-test is to return HTCAPTIONwhen a single tab is present. This allows the entire window to be dragged but causes the context menu to be wrong and the windowto maximize when double clicking on the single tab.The solution here is to correct return a client hit for a singletab and, upon handling a client single-click, delegate to thenon-client single-click default handler.
Review URL: http://codereview.chromium.org/21268
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=21203 

------------------------------------------------------------------------
r21203 | estade@chromium.org | 2009-07-21 12:51:24 -0700 (Tue, 21 Jul 2009) | 100 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view_gtk.cc?r1=21203&r2=21202
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view_gtk.h?r1=21203&r2=21202
   M http://src.chromium.org/viewvc/chrome/trunk/src/webkit/api/src/gtk/WebInputEventFactory.cpp?r1=21203&r2=21202

This change list improves IME support on Linux. Many corner cases that were not
handled in original code are addressed, for example the input method in password
box case.

The most important change in this CL is the change to key event processing flow.
 In old code, a key event will first be sent to webkit then dispatched to IME
for filtering. With this CL, a key event will first be dispatched to IME for
filtering, then how to send the event to webkit is decided by the filtering
result.

This CL tries to emulate the keyboard input behavior on Windows as much as
possible. For example, if a keydown event is filtered by IME, then its virtual
key code will be changed to VK_PROCESSKEY(0xE5) to prevent webkit from
processing it again. This behavior can workaround  bug 16281 .

To test this CL, you may cut and save following html code into a file and open
it in chrome.
------------------8<----cut here----->8---------------------
<html><head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">

<script>
function keyEventHandler(event) {
  var props = [ "type", "charCode", "keyCode", "altKey",
    "ctrlKey", "shiftKey", "metaKey" ];
  var info = document.getElementById('info');
  var s = '';
  for (var i in props) {
    s += props[i] + ':' + event[props[i]] + ' ';
  }
  info.value += s + '\n';
}

function textEventHandler(event) {
  info.value += "type:" + event['type'] + " data:" + event['data'] + '\n';
}

function passwordChangeEventHandler(event) {
  var input2 = document.getElementById('input2');
  info.value += "password:" + input2.value + '\n';
}

function onLoad() {
  var input = document.getElementById('input');
  input.addEventListener('keydown', keyEventHandler, false);
  input.addEventListener('keyup', keyEventHandler, false);
  input.addEventListener('keypress', keyEventHandler, false);
  input.addEventListener('textInput', textEventHandler, false);
  var input2 = document.getElementById('input2');
  input2.addEventListener('change', passwordChangeEventHandler, false);
}
</script>
</head><body onload="onLoad()">
<input id="input" size="20">
<input id="input2" type="password" size="20">
<p>
<textarea id="info" rows="40" cols="150"></textarea>
</p></body></html>
------------------8<----cut here----->8---------------------

This CL was confirmed to fix following issues:
BUG=16281 "arrow keys and backspace/delete keys move/delete two characters at a
time when xim immodule is used"
BUG=16282 "Disable IMEs in a password input"
BUG=16596 "fcitx (chinese input method) not working in ubuntu 9.04"
BUG=16659 "Crash near RenderWidgetHostViewGtk::IMEUpdateStatus"
BUG=16699 "Can't move cursor to omnibox and use input method if cursor is
currently in a text input box in web page."
BUG=16796 "Input method issue: When inputting text in a text box, if there is a
composition string then pressing Backspace or Delete will cause the composition
string be cleared and the text box refuses to accept any further input.

All tests assume above html code is used.
TEST=Start scim with "scim -d" and start chrome with GTK_IM_MODULE=xim and
XMODIFIERS=@im=SCIM. Type something in input box, eg. "hello", then press
backspace, to see if only one character is deleted.
TEST=Move cursor to password input box, press ctrl-space to see if input method
is not activated. Switch keyboard layout to Canadian-French then type a'[{' key
and an 'a' key, then press enter, to see if a Latin character "U+00E2" is
inputted in password box.
TEST=Install fcitx with "sudo apt-get install fcitx" (assume you are using
Ubuntu/Debian). Open a terminal, export XMODIFIERS=@im=fcitx and
GTK_IM_MODULE=xim then run fcitx, then start chrome. Move cursor into an input
box, press ctrl-space and input something, eg. "nihao" then press space. Check
if some Chinese characters are inputted.
TEST=Start chrome with GTK_IM_MODULE=scim. Move cursor into a text input box
then move into a password box, chrome should not crash.
TEST=Move cursor into a text input box, then click omnibox, and see if the text
input box has lost focus. Press ctrl-space to activate input method, then type
something, and see of the input goes into omnibox.
TEST=Move cursor into a text input box and enable a Chinese Pinyin input method,
then type something, eg. "dajiahao", make sure a composition string is displayed
in the text input box, then press backspace and see if there is still a
composition string and backspace is handled by input method.

patch by James Su <james.su [at] gmail>
original review URL: <http://codereview.chromium.org/149755>


Review URL: http://codereview.chromium.org/155869
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=29749 

------------------------------------------------------------------------
r29749 | mark@chromium.org | 2009-10-21 18:47:49 -0700 (Wed, 21 Oct 2009) | 42 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_mac.h?r1=29749&r2=29748
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_mac.mm?r1=29749&r2=29748

Change the strategy used to attempt nesting-deferred work to account equally
well for nested run loops under our own control (those started by Run) and
those beyond our control (native event loops).

Previously, upon any exit from a nested native loop, we would schedule
nesting-deferred work for processing.  However, some nested native loops do
not execute in a single loop; rather, they start and stop the CFRunLoop
rapidly.  In such cases, each exit from the CFRunLoop would cause
nesting-deferred work to be scheduled, and on each new entry to the CFRunLoop,
we would attempt to process it.  This rapid-fire action meant that we'd never
sleep.  Nested loops managed by Run were exempt from these problems since
r28811, because we could defer scheduling nesting-deferred work until
returning to Run.

The new strategy is to detect whether any nested loops (native or managed by
Run) had run before the run loop goes to sleep or exits.  If any nested loops
did run, nesting-deferred work is scheduled for processing.

BUG=24968
TEST=1. Test case from  bug 24968 , printing: open any page, press command-P,
        leave the dialog up, and check Chrome's CPU usage.  No Chrome process
        should be monopolizing any CPU.  This tests nested native run loops.
     2. Test case from  bug 24337 , JS alerts: open Gmail, start composing a new
        message in a new window, address it to yourself, move focus to the
        subject field, click the Discard button, and click "OK" at the alert.
        The alert and composition window should close.
     3. Test case from  bug 24383 , JS alerts: no Chrome processes should use
        100% CPU after visiting javascript:alert("hi").  The JS alert cases
        test nested run loops managed by Run.
     4. Test case from  bug 13468  comment 5, autocomplete: autocomplete should
        still work after using "Back" from a contextual menu.  This tests
        that nesting-deferred work is processed after leaving a nested run
        loop.
     5. First run UI test case (no bug).  Remove or move aside the profile
        directory (~/Library/Application Support/Chromium or
        ~/Library/Application Support/Google/Chrome) and launch the
        application.  There should be first-run UI and it should be usable.
        Upon clicking "Start (application)", the application should start and
        be usable as normal.  This tests delegateless run loops and
        delegateless work redispatch.
     6. base_unittests --gtest_filter='MessageLoopTest.*'
Review URL: http://codereview.chromium.org/300044
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=32640 

------------------------------------------------------------------------
r32640 | jshin@chromium.org | 2009-11-20 11:24:35 -0800 (Fri, 20 Nov 2009) | 12 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/linux/icudt42l_dat.s?r1=32640&r2=32639
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/mac/icudt42l_dat.s?r1=32640&r2=32639
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/patches/data.build.patch?r1=32640&r2=32639
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/patches/segmentation.patch.txt?r1=32640&r2=32639

Remove invuca.icu table from the ICU data file again. It was added to make Chrome not crash with a webkit patch for
bug 30437 (https://bugs.webkit.org/show_bug.cgi?id=30437)

However, the webkit patch was rolled back so that we don't need invuca.icu for now. Removing it will cut down the data size by 230k (before compression and in the Chrome executable on Linux/Mac and the ICU data dll on Linux).
This has to be added back when it becomes necessary again to fix the aforementioned webkit bug. 

See also http://crbug.com/28132 (a bug about ~ 4kB of space wasted by copyright statements) 

BUG=20406
TEST=NONE

Review URL: http://codereview.chromium.org/399089
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=32651 

------------------------------------------------------------------------
r32651 | jshin@chromium.org | 2009-11-20 12:01:15 -0800 (Fri, 20 Nov 2009) | 16 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/icudt42.dll?r1=32651&r2=32650
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/source/data/in/icudt42l.dat?r1=32651&r2=32650

Remove invuca.icu table from the ICU data file again (part 2 : Windows. For part 1, see http://codereview.chromium.org/399089/show)

It was added to make Chrome not crash with a webkit patch for 
bug 30437 (https://bugs.webkit.org/show_bug.cgi?id=30437) 

However, the webkit patch was rolled back so that we don't need invuca.icu for now. Removing it will cut down the data size by 230k (before compression and in the Chrome executable on Linux/Mac and the ICU data dll on Linux). 
This has to be added back when it becomes necessary again to fix the aforementioned webkit bug. 

See also http://crbug.com/28132 (a bug about ~ 4kB of space wasted by copyright statements) 

TBR=evan
BUG=20406
TEST=NONE 


Review URL: http://codereview.chromium.org/418018
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=33118 

------------------------------------------------------------------------
r33118 | jshin@chromium.org | 2009-11-25 13:22:20 -0800 (Wed, 25 Nov 2009) | 16 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=33118&r2=33117

Pull in icu@32651:

Remove invuca.icu table from the ICU data file again(see http://codereview.chromium.org/399089/show)

It was added to make Chrome not crash with a webkit patch for 
bug 30437 (https://bugs.webkit.org/show_bug.cgi?id=30437) 

However, the webkit patch was rolled back so that we don't need invuca.icu for now. Removing it will cut down the data size by 230k (before compression and in the Chrome executable on Linux/Mac and the ICU data dll on Linux). 
This has to be added back when it becomes necessary again to fix the aforementioned webkit bug. 

See also http://crbug.com/28132 (a bug about ~ 4kB of space wasted by copyright statements)

BUG=20406
TEST=All the webkit tests pass.

Review URL: http://codereview.chromium.org/418019
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=33157 

------------------------------------------------------------------------
r33157 | jshin@chromium.org | 2009-11-25 15:47:28 -0800 (Wed, 25 Nov 2009) | 19 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/249/src/DEPS?r1=33157&r2=33156

Merge 33118 - Pull in icu@32651:

Remove invuca.icu table from the ICU data file again(see http://codereview.chromium.org/399089/show)

It was added to make Chrome not crash with a webkit patch for 
bug 30437 (https://bugs.webkit.org/show_bug.cgi?id=30437) 

However, the webkit patch was rolled back so that we don't need invuca.icu for now. Removing it will cut down the data size by 230k (before compression and in the Chrome executable on Linux/Mac and the ICU data dll on Linux). 
This has to be added back when it becomes necessary again to fix the aforementioned webkit bug. 

See also http://crbug.com/28132 (a bug about ~ 4kB of space wasted by copyright statements)

BUG=20406
TEST=All the webkit tests pass.

Review URL: http://codereview.chromium.org/418019

TBR=jshin@chromium.org
Review URL: http://codereview.chromium.org/434104
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=32640 

------------------------------------------------------------------------
r32640 | jshin@chromium.org | 2009-11-20 11:24:35 -0800 (Fri, 20 Nov 2009) | 12 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/linux/icudt42l_dat.s?r1=32640&r2=32639
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/mac/icudt42l_dat.s?r1=32640&r2=32639
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/patches/data.build.patch?r1=32640&r2=32639
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/patches/segmentation.patch.txt?r1=32640&r2=32639

Remove invuca.icu table from the ICU data file again. It was added to make Chrome not crash with a webkit patch for
bug 30437 (https://bugs.webkit.org/show_bug.cgi?id=30437)

However, the webkit patch was rolled back so that we don't need invuca.icu for now. Removing it will cut down the data size by 230k (before compression and in the Chrome executable on Linux/Mac and the ICU data dll on Linux).
This has to be added back when it becomes necessary again to fix the aforementioned webkit bug. 

See also http://crbug.com/28132 (a bug about ~ 4kB of space wasted by copyright statements) 

BUG=20406
TEST=NONE

Review URL: http://codereview.chromium.org/399089
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=32651 

------------------------------------------------------------------------
r32651 | jshin@chromium.org | 2009-11-20 12:01:15 -0800 (Fri, 20 Nov 2009) | 16 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/icudt42.dll?r1=32651&r2=32650
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/source/data/in/icudt42l.dat?r1=32651&r2=32650

Remove invuca.icu table from the ICU data file again (part 2 : Windows. For part 1, see http://codereview.chromium.org/399089/show)

It was added to make Chrome not crash with a webkit patch for 
bug 30437 (https://bugs.webkit.org/show_bug.cgi?id=30437) 

However, the webkit patch was rolled back so that we don't need invuca.icu for now. Removing it will cut down the data size by 230k (before compression and in the Chrome executable on Linux/Mac and the ICU data dll on Linux). 
This has to be added back when it becomes necessary again to fix the aforementioned webkit bug. 

See also http://crbug.com/28132 (a bug about ~ 4kB of space wasted by copyright statements) 

TBR=evan
BUG=20406
TEST=NONE 


Review URL: http://codereview.chromium.org/418018
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=34440 

------------------------------------------------------------------------
r34440 | oshima@chromium.org | 2009-12-12 19:07:36 -0800 (Sat, 12 Dec 2009) | 3 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/valgrind/unit_tests.gtest_mac.txt?r1=34440&r2=34439

4th attemp to make valgrind/mac happy. see bug 30209.

TBR: viettrungluu@chromium.org
------------------------------------------------------------------------