Go to http://www.yahoo.com. Click in the text field. On the Linux viewer, this immediately takes you to another url (sometimes http://www.yahoo.com/r/wn, sometimes http://mail.yahoo.com). On win32, you can type something in and do a search.

Sujay, could you please check this with latest Linux build. I heard yahoo isn't even loading at all...let alone this problem. Thanks!

I'll probably need gdb help to debug this. I'll come bug this Linux guys Monday.

this still happens on 1/22 build of Linux. clicking in text field doesn't work and behaves sometimes like described below...

sujay, please try Jan 25 Linux build.

When I try it in my development build, I no longer see this behavior. Of course, I can't search because the submit button doesn't work.

still happens in 1/26 build.

Okay, we have a slightly better idea what this is doing. The events coordinates are not matching up with the text field. They're hitting the image at the top of the page. That's why it doesn't always happen. Clicking on the left edge of the field doesn't do it, clicking on the right does. First pass testing doesn't indicate where the coordinate problem is occurring. Continuing testing.

Inserting Milestone info.

Setting all current Open/Normal to M4.

sujay - can you try this one with latest Linux build.

sure will get to this in next build...

yes still happens in 3/2 build..

We have a potential fix but still has some stability problems. Currently this bug is annoying but can usually be worked around. Postponing fix to M5 rather than introduce fatal error.

Ramiro, I'm going to send this your way since I'm going to be out for the next week and a half. Perhaps your widget changes will just fix this anyway. But basically the problem was that the text widget isn't handling its own mouse events and as a result those mouse events are coming in through the parent widget but with child widget coords. The net effect was that a click 10 pixels into the text field translated in the layout system to a click 10 pixels into the doc. We had a potential fix that involved registering handle_button_press_event and release_event for the text widget but I notice those function are now gone out of nsGtkEventHandler. If this is still broken when I get back after M5 I'll look at it more.

i know this problem well, and my coming event system fixes will address this.

i dont think this happens anymore with some changes i checked in to prevent gtk events from percolating to the parent. however, i have some more fixes in this area. marking m6 to get out of the radar, but it might actually be fixed for m5.

yes, i fixed this in m5. marking fixed.

verified in 5/12 build.