Closed
Bug 609664
Opened 14 years ago
Closed 14 years ago
Clearing locationBar is broken on 1.9.1
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: abillings, Unassigned)
References
Details
Attachments
(1 file)
390 bytes,
text/plain
|
Details |
I've been trying to figure out why testPasteLocationBar.js works on default and 1.9.2 but not 1.9.1. One issue that I've found is that the test clears the locationBar before pasting content into it. This clearing is broken on 1.9.1. The test does the following during setup (which is standard in mozmill cases I've seen): locationBar = new toolbars.locationBar(controller); Later, it does: locationBar.clear(); Following this, on default and 1.9.2, the locationBar is cleared. On 1.9.1, nothing happens.
Comment 1•14 years ago
|
||
Al, can you please come up with a minimized test which shows this problem? It will help me to easily reproduce the issue you are seeing. Thanks
Reporter | ||
Comment 2•14 years ago
|
||
Place this in your /firefox/testAwesomeBar directory or one at a similar depth in your mozmill-tests repo and run it. I didn't add an explicit assert of the failure but if you run it on 1.9.1, you won't see a navigation to twitter. If you run it on 1.9.2, you will.
Reporter | ||
Comment 3•14 years ago
|
||
Doh, this is a repro case for bug 610072. My bad.
Comment 4•14 years ago
|
||
(In reply to comment #3) > Doh, this is a repro case for bug 610072. My bad. So this bug is invalid too?
Reporter | ||
Comment 5•14 years ago
|
||
This was the focus problem.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Reporter | ||
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•14 years ago
|
||
Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Version: 1.9.1 Branch → unspecified
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•