Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature Request - Tabs should remember the environment they were executed such that going between tabs should remember the correct environment. #1256

Open
invalidred opened this issue Jul 15, 2015 · 4 comments
Open

Feature Request - Tabs should remember the environment they were executed such that going between tabs should remember the correct environment. #1256

invalidred opened this issue Jul 15, 2015 · 4 comments
Assignees
@a85 @vkaegis
Labels
configurations Environments feature history product/runtime tabs

Comments

@invalidred
Copy link

Steps

  1. On tab 1 run api on "development" environment
  2. Open a new tab (tab 2) and run another api on "staging" environment
  3. Go back to tab 1, the environment is "staging", it should be "development".

Tabs should remember the environments they were executed under.
@invalidred invalidred changed the title Tabs should remember the environment they were executed such that going between tabs should remember the correct environment. (Feature Request) Tabs should remember the environment they were executed such that going between tabs should remember the correct environment. Jul 15, 2015
@invalidred invalidred changed the title (Feature Request) Tabs should remember the environment they were executed such that going between tabs should remember the correct environment. Feature Request - Tabs should remember the environment they were executed such that going between tabs should remember the correct environment. Jul 15, 2015
@duepayer
Copy link

+1 looking forward to this feature

@invalidred
Copy link
Author

Same here... really want this feature.

@a85 a85 added transfer and removed transfer labels Jan 28, 2016
@a85 a85 mentioned this issue Dec 23, 2017
Closed
@a85 a85 self-assigned this Jun 29, 2018
@simonds
Copy link

simonds commented Jul 23, 2018

+1

@vkaegis vkaegis self-assigned this Nov 18, 2018
This was referenced Apr 14, 2021
Closed
Closed
@giridharvc7
Copy link

Duplicate issues #8202 and #6622

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@a85 a85

@vkaegis vkaegis

Labels
configurations Environments feature history product/runtime tabs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@simonds @duepayer @a85 @abhijitkane @giridharvc7 @vvs11 @invalidred @vkaegis