Skip to content

P0: VS Code: Delegate launching browser to DevTools to always get Chrome #1505

Closed

Description

@DanTup

Activity

  1. added
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    in commandsRelates to commands (usually invoked from the command Palette)
    on Mar 4, 2019
  2. added this to the v2.25.0 milestone on Mar 4, 2019
  3. DanTup commented on Mar 4, 2019

    @DanTup
    MemberAuthor

    This will be handled in the server instead.

  4. removed
    in commandsRelates to commands (usually invoked from the command Palette)
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    on Mar 4, 2019
  5. removed this from the v2.25.0 milestone on Mar 4, 2019
  6. skybur commented on Apr 5, 2019

    @skybur

    Sorry for commenting in this closed issue. So how do I start devtools in chrome if it's not my default browser? Thanks

  7. DanTup commented on Apr 5, 2019

    @DanTup
    MemberAuthor

    Currently you'd have to open Chrome manually and copy the URL from the default browser that is launched. This will be fixed, but requires flutter/devtools#463.

    I'm re-opening this, since there will be work today when that lands which I forgot about.

  8. reopened this on Apr 5, 2019
  9. added this to the v2.26.0 milestone on Apr 5, 2019
  10. added
    in commandsRelates to commands (usually invoked from the command Palette)
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    on Apr 5, 2019
  11. 19 remaining items

  12. added a commit that references this issue on Apr 29, 2019
    be505bc
  13. DanTup commented on Apr 30, 2019

    @DanTup
    MemberAuthor

    I've opened flutter/devtools#611 in the DevTools repo for supporting this from stdin (since this issue will soon be closed). If it's urgent, let me know.

  14. added 3 commits that reference this issue on Apr 30, 2019
    464037d
    204b108
    8a78454
  15. added a commit that references this issue on Apr 30, 2019
    934226a
  16. DanTup commented on May 1, 2019

    @DanTup
    MemberAuthor

    I'm disabling this for v2.26.1 because I'd like to release the other fixes and there are complications with this. If it fails - most likely because Chrome isn't installed - it seems to unregister the service unexpectedly. I'll put it back in another patch once I'm sure we can handle the failure in a reasonable way.

  17. reopened this on May 1, 2019
  18. modified the milestones: v2.26.1, v2.26.2 on May 1, 2019
  19. added 3 commits that reference this issue on May 1, 2019
    2db7508
    c05bce5
    674e912
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

importantSomething important!in commandsRelates to commands (usually invoked from the command Palette)is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions