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.

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

Not all tabs persisted in order between sessions #2998

Closed
CalvinQuark opened this issue Dec 29, 2023 · 1 comment · Fixed by #3036
Closed

Not all tabs persisted in order between sessions #2998

CalvinQuark opened this issue Dec 29, 2023 · 1 comment · Fixed by #3036
Labels
ADO cat: devtools DevTools-related content.

Comments

@CalvinQuark
Copy link

CalvinQuark commented Dec 29, 2023

The claim on this page that "Your custom tool order persists across DevTools sessions" apparently does not apply to Extension-provided tabs. I am encountering with the GraphQL Network Inspector extension sourced from the Chrome web store that this extension's tab is always positioned after the standard DevTools native tabs.

If this behavior is intentional, then it would be helpful if it were noted down on this page. However, it would be more useful if the positions of extension tabs were likewise persisted between sessions.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

AB#48368746

@captainbrosset
Copy link
Contributor

I agree that it would be more helpful if extension-provided tabs would also get their position persisted, and I would advise you to file this as a feature request on the DevTools feedback repository instead, here: https://github.com/MicrosoftEdge/DevTools.

In the meantime, we can also make a change to the documentation, something like "For the time being, extension-provided tabs are always positioned after the built-in tabs".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ADO cat: devtools DevTools-related content.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants