Closed
Bug 339565
Opened 19 years ago
Closed 19 years ago
google.com textfield autocomplete shows unexpectedly with gok
Categories
(Firefox :: Disability Access, defect)
Tracking
()
RESOLVED
FIXED
Firefox 2 beta2
People
(Reporter: ginnchen+exoracle, Assigned: nian.liu)
References
()
Details
(Keywords: access, fixed1.8.1)
Attachments
(2 files)
120.48 KB,
image/png
|
Details | |
1.79 KB,
patch
|
aaronlev
:
review+
neil
:
superreview+
beltzner
:
approval1.8.1+
|
Details | Diff | Splinter Review |
1) open www.google.com, make sure firefox saved some values for the text field.
2) focus the text field (it is focused by default when www.google.com is loaded)
autocomplete dropdown isn't shown at this time
3) "ui grab" with gok, click "About Google" button in gok window
4) "About Google" page rendered with textfield autocomplete dropdown at the middle of the page
I'm not sure if this bug belongs to A11y, but I can only reproduce it with gok.
btw: if focus is not in the textfield as step 2), this bug can't be reproduce.
Assignee | ||
Comment 2•19 years ago
|
||
at-poke shows first autocomplete get the focus then link "about google" get the focus.
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → nian.liu
Assignee | ||
Comment 3•19 years ago
|
||
mimic real ui event.
Attachment #224400 -
Flags: review?(ginn.chen)
Attachment #224400 -
Flags: review?(ginn.chen) → review?(aaronleventhal)
Comment 4•19 years ago
|
||
Comment on attachment 224400 [details] [diff] [review]
patch
Cool.
Attachment #224400 -
Flags: review?(aaronleventhal) → review+
Assignee | ||
Updated•19 years ago
|
Attachment #224400 -
Flags: superreview?(roc)
Updated•19 years ago
|
Attachment #224400 -
Flags: superreview?(roc) → superreview?(neil)
Comment 5•19 years ago
|
||
Comment on attachment 224400 [details] [diff] [review]
patch
> nsIPresShell *presShell = doc->GetShellAt(0);
...
>- content->HandleDOMEvent(presShell->GetPresContext(), &clickEvent, nsnull,
>- NS_EVENT_FLAG_INIT, &eventStatus);
>+ presShell->HandleDOMEventWithTarget(content, &downEvent, &eventStatus);
>+ presShell->HandleDOMEventWithTarget(content, &upEvent, &eventStatus);
>+ presShell->HandleDOMEventWithTarget(content, &clickEvent, &eventStatus);
These calls can theoretically destroy the pres shell. Before, there was only one call, so it didn't matter. However, you now need to store the pres shell in an nsCOMPtr to ensure that it continues to exist. sr=me with that fixed.
Attachment #224400 -
Flags: superreview?(neil) → superreview+
Updated•19 years ago
|
Assignee | ||
Comment 6•19 years ago
|
||
> These calls can theoretically destroy the pres shell. Before, there was only
Neil,
can you help me know how that destroy the pres shell?
> one call, so it didn't matter. However, you now need to store the pres shell in
> an nsCOMPtr to ensure that it continues to exist. sr=me with that fixed.
>
Assignee | ||
Comment 7•19 years ago
|
||
aaron,
we need to change nsIPresShell *presShell = doc->GetShellAt(0);
to nsCOMPtr<nsIPresShell> presShell = doc->GetShellAt(0);
as Neil addressed.
Comment 8•19 years ago
|
||
(In reply to comment #6)
>can you help me know how that destroy the pres shell?
Basically, any event can invoke JavaScript which can close the window.
Comment 9•19 years ago
|
||
Okay, made the nsCOMPtr<> change.
Updated•19 years ago
|
Attachment #224400 -
Flags: approval1.8.1?
Updated•19 years ago
|
Flags: blocking-firefox2?
Target Milestone: --- → Firefox 2 beta2
Comment 10•19 years ago
|
||
We'll plus the patch when beta 1 clears...
Flags: blocking-firefox2? → blocking-firefox2+
Comment 11•19 years ago
|
||
Comment on attachment 224400 [details] [diff] [review]
patch
You are cleared to land, sir.
Attachment #224400 -
Flags: approval1.8.1? → approval1.8.1+
Updated•18 years ago
|
Whiteboard: [has approval, needs checkin]
Reporter | ||
Comment 12•18 years ago
|
||
Checking in src/base/nsAccessible.cpp;
/cvsroot/mozilla/accessible/src/base/nsAccessible.cpp,v <-- nsAccessible.cpp
new revision: 1.165.2.8; previous revision: 1.165.2.7
done
Keywords: fixed1.8.1
Whiteboard: [has approval, needs checkin]
You need to log in
before you can comment on or make changes to this bug.
Description
•