[PP]Jan22:Linux: Clicking on text field loads new url

VERIFIED FIXED in M6

Status

()

Core
Event Handling
P2
normal
VERIFIED FIXED
20 years ago
19 years ago

People

(Reporter: Akkana Peck, Assigned: Ramiro Estrugo)

Tracking

Trunk
Other
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

20 years ago
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.

Comment 1

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

Updated

20 years ago
Status: NEW → ASSIGNED

Comment 2

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

Comment 3

20 years ago
this still happens on 1/22 build of Linux.

clicking in text field doesn't work and behaves sometimes
like described below...

Updated

20 years ago
Hardware: PC → Other
Summary: [PP] Linux: Clicking on text field loads new url → [PP]Jan22:Linux: Clicking on text field loads new url

Comment 4

20 years ago
sujay, please try Jan 25 Linux build.
(Reporter)

Comment 5

20 years ago
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.

Comment 6

20 years ago
still happens in 1/26 build.

Comment 7

20 years ago
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.

Comment 8

20 years ago
Inserting Milestone info.

Comment 9

20 years ago
Setting all current Open/Normal to M4.

Comment 10

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

Updated

20 years ago
QA Contact: 4079

Comment 11

20 years ago
sure will get to this in next build...

Comment 12

20 years ago
yes still happens in 3/2 build..

Updated

20 years ago
Target Milestone: M4 → M5

Comment 13

20 years ago
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.

Updated

19 years ago
Assignee: joki → ramiro
Status: ASSIGNED → NEW

Comment 14

19 years ago
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.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 15

19 years ago
i know this problem well, and my coming event system fixes will address this.
(Assignee)

Updated

19 years ago
Target Milestone: M5 → M6

Comment 16

19 years ago
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.
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 17

19 years ago
yes, i fixed this in m5.

marking fixed.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 18

19 years ago
verified in 5/12 build.
You need to log in before you can comment on or make changes to this bug.