Closed Bug 1127831 Opened 5 years ago Closed 5 years ago

Implement handling of tabs


(Testing :: Firefox UI Tests, defect)

Version 2
Not set


(Not tracked)



(Reporter: whimboo, Assigned: whimboo)




(1 file)

This bug will cover the light-weight handling of tabs compared to bug 1121705. It will not make use of any event and observer code, which the other bug is blocked on.
A current WIP of the functionality is available at:

I got all the basics working so far. Means opening and closing of tabs work. The same for switching between tabs. But there is still a bit of work to do:

* Fully implement all possible trigger methods for opening and closing tabs
* Add assertions to methods which ensure that the trigger action was successful
* Check how we have to handle the focus and automatically switch to newly opened tabs
* Implement the remaining methods which exist as skeletons in the tab module
* Get more tests written, also with two open browser windows

Chris, if you want to continue please do so and let me know about your branch. That way I can re-import your changes and continue on Monday. Please keep in mind that there is a follow-up bug, which is about getting all the remaining tabbar features in. Those things are trivial and I can surely work on those on Monday. So we should be set for Tuesday.
Not sure why but all the toolbar tests fail on travis for this above branch. You might wanna have a look at this first. Maybe I missed something to correctly rebase.
(In reply to Henrik Skupin (:whimboo) from comment #2)
> Not sure why but all the toolbar tests fail on travis for this above branch.
> You might wanna have a look at this first. Maybe I missed something to
> correctly rebase.

This is the same problem I had to work around trying to merge the locationbar library. We end up in "content" context by tearDown when a test is skipped. This seems like a bug in marionette automation, but easy enough to work around.
I got further with this in the top three commits at:

I think this is looking good. From the list in comment 1, there might be more trigger methods to implement, and more tests would be in order. I'm not sure about automatically switching into tabs, but I suspect because the effect of this is primarily for which tab receives content commands, and we'll primarily work in chrome, the more relevant thing for us will be tab selection in the UI.
Chris, thanks for the additionally work. I will have a look at it soon and continue with the remaining bits now. I will have a review request for you later today.
Chris, please have a look at the Github pull request. I just uploaded the final version of my patch. Thanks.
Attachment #8558106 - Flags: review?(cmanchester)
Comment on attachment 8558106 [details] [review]

I left a few comments in Github that should be addressed if possible, no hard blockers.
Attachment #8558106 - Flags: review?(cmanchester) → review+
Thanks Chris for the review. I made all the required changes and merged the PR as:
Closed: 5 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
I had to push a follow-up for this because the Tab documentation was missing on readthedocs:
Product: Mozilla QA → Testing
No longer blocks: 1121705
You need to log in before you can comment on or make changes to this bug.