Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Active tab update issue #9023

Merged
merged 7 commits into from
May 25, 2017
Merged

Active tab update issue #9023

merged 7 commits into from
May 25, 2017

Conversation

bridiver
Copy link
Collaborator

@bridiver bridiver commented May 24, 2017

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Ran git rebase -i to squash commits (if needed).

Fixes #8974

Test Plan:

Reviewer Checklist:

  • Adequate test coverage exists to prevent regressions
  • Tests should be independent and work correctly when run individually or as a suite ref
  • New files have MPL2 license header

@bridiver bridiver requested review from bbondy and bsclifton May 24, 2017 16:28
@bridiver bridiver changed the base branch from master to dev-channel May 24, 2017 16:32
@bridiver bridiver force-pushed the active-tab-update-issue branch 3 times, most recently from 3627bc0 to f303a06 Compare May 25, 2017 00:04
bsclifton and others added 2 commits May 24, 2017 17:07
add some index checks
remove unused method
fix tab close behavior
bsclifton and others added 2 commits May 24, 2017 17:31
only use strings for keys

misc cleanup
fix closing pinned tabs
rename method
@bsclifton bsclifton added this to the 0.15.300 milestone May 25, 2017
Copy link
Member

@bsclifton bsclifton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs more tests and also needs to be merged to master. Important to note this includes behavior changing when closing tabs which @bridiver reviewed with @bradleyrichter

++! 👍

Copy link
Member

@bsclifton bsclifton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

retested original test case (ctrl + w issue) and it failed ☹️

@bsclifton
Copy link
Member

I think a new Muon version is needed (build is in progress). This includes the following patch:
brave/muon@4fdf666

When using this code as-is, I was able to cause an issue by setting tab close behavior to the default (parent). Will retest when new Muon is available 😄

@bsclifton
Copy link
Member

After the Muon PR, the issues I saw were fixed 👍

I think he only remaining issue is:
Behaviors for close (when you pick one of the three options) don't seem to work as described
screen shot 2017-05-25 at 8 54 51 am

@bsclifton
Copy link
Member

My setup:
2 pinned tabs (https://slashdot.org/, https://www.roboform.com/filling-test-all-fields)

select the last viewed tab - this always seems to be choosing the 2nd pinned tab, no matter what I do

select the next tab - this behavior is inconsistent. Sometimes, it picks the previous tab, sometimes it picks what seems to be a random tab (maybe the previous index?). If I have two tabs open and try to close the first, it selects the first pinned tab.

select its parent tab - this seems to be working for the most part. It doesn't always select the parent though. If I open the same link via middle clicking 3 times, closing one of them chooses another one (not necessarily the opener)

bsclifton and others added 2 commits May 25, 2017 10:33
@bridiver
Copy link
Collaborator Author

I pushed a fix for "last active", but I can't replicate any issues with "next tab". "parent" should only go back to the parent if it is also the last active tab, otherwise it should go to "next"

Copy link
Member

@bsclifton bsclifton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes work great 😄

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants