Can move selected item in autocomplete drop down in other tab with some special script

RESOLVED WORKSFORME

Status

()

Firefox
Address Bar
RESOLVED WORKSFORME
13 years ago
12 years ago

People

(Reporter: Martijn Wargers (dead), Assigned: jst)

Tracking

unspecified
x86
Windows 2000
Points:
---
Bug Flags:
blocking-aviary1.0 -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041024 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041024 Firefox/0.9.1+

See upcoming testcase.
Open the link in that testcase in a new tab. Visit that new tab.
Open the autocomplet drop down menu by double clicking on the input textbox.
Result:
After every 1 second, the selected item of the autocomplete drop down gets moved
one item below. This should not happen.
Also, when typing a letter, the text of the autocomplete drop down gets copied
into the input every second.

This also happens in the 1.0 aviary branch.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

13 years ago
Created attachment 163406 [details]
Testcase

This is the script that seems to cause this, by the way:
var x=document.getElementsByTagName('body')[0];
var me = document.createEvent("MouseEvents");
me.initMouseEvent('click',1,1,window,0,0,0,0,0,0,0,0,0,0,x);
x.dispatchEvent(me);

Updated

13 years ago
Flags: blocking-aviary1.0?
Summary: Can move selected item in autocomplete drop down in other tab with some special script → Can move selected item in autocomplete drop down in other tab with some special script

Comment 2

13 years ago
Jst's gonna look into this.
Flags: blocking-aviary1.0? → blocking-aviary1.0+

Updated

13 years ago
Assignee: bugs → jst
(Assignee)

Comment 3

13 years ago
We want to fix all these issues, but to do that we need to sentralize some
checking for trusted events, and that requires making some more events trusted
etc, and that means a big patch, something we don't want for 1.0 any more. And
since we don't see this as a security problem, it won't make it into 1.0...
Flags: blocking-aviary1.0+ → blocking-aviary1.0-

Updated

13 years ago
Flags: blocking-aviary1.1?
(Reporter)

Comment 4

13 years ago
This is wfm now with a 2005-05-06 trunk build.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME

Updated

13 years ago
Flags: blocking-aviary1.1?
You need to log in before you can comment on or make changes to this bug.