Clearing locationBar is broken on 1.9.1

VERIFIED INVALID

Status

Mozilla QA
Mozmill Tests
VERIFIED INVALID
8 years ago
8 years ago

People

(Reporter: [PTO until July 27], Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

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

8 years ago
Created attachment 488620 [details]
Repro case using mozmill and mozmill-tests hg repo

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

8 years ago
Doh, this is a repro case for bug 610072. My bad.
(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

8 years ago
This was the focus problem.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
(Reporter)

Updated

8 years ago
Status: RESOLVED → VERIFIED
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.
Component: Mozmill Tests → Mozmill Tests
Product: Testing → Mozilla QA
Version: 1.9.1 Branch → unspecified
You need to log in before you can comment on or make changes to this bug.