Skip to content

Support Firefox #492

Closed
Closed

Description

@12people

I'd really like to be able to use my browser of choice, Firefox, with Flutter's DevTools.

(Not only that, but I'd also appreciate if web projects in general weren't tied to specific browsers — it hurts web standards and I'd hate another IE-like situation where standards don't matter.)

Activity

  1. stevemessick commented on Apr 2, 2019

    @stevemessick
    Member

    Dup of #66

  2. 12people commented on Apr 2, 2019

    @12people
    Author

    @stevemessick #66 is about displaying messages in unsupported browsers. This bug is about supporting a browser other than Chrome. Two very different things.

  3. stevemessick commented on Apr 2, 2019

    @stevemessick
    Member

    #66 is a pretty extensive discussion about what it takes to support browsers other than Chrome. Including Firefox.

    However, I may be mis-interpreting it. I'll let @jacob314 chime in as to whether this should be re-opened.

  4. 12people commented on Apr 2, 2019

    @12people
    Author

    @stevemessick It does mention other browsers, yet the issue at hand is different. That issue comes down to "only Chrome is officially tested, should we display a warning in other browsers?".

    This "support Firefox" issue asks, "only Chrome is officially tested, should we still allow it to run DevTools, fix bugs for it, and/or add Firefox to the browsers we test in?" It's about broadening support rather than asking if a warning is needed.

  5. jacob314 commented on Apr 2, 2019

    @jacob314
    Contributor

    Flutter Web will support all modern browsers. If we are able to switch all of this application to use Flutter Web at that point we will begin to support more browsers. Until that point, our time is better spent adding features than making sure we avoid browser compatibility bugs.

  6. Afsar-Pasha commented on Apr 15, 2019

    @Afsar-Pasha

    @12people Try changing UA string using this addon.

  7. 12people commented on Apr 19, 2019

    @12people
    Author

    @jacob314 I understand your need for effectiveness.

    What if DevTools could be opened in Firefox, but there was a dismissable message on first open saying "Firefox is not officially supported. DevTools may not function properly" or something along those lines?

    Changing the UA string really feels like I'm going back to IE-incompatibility times and I'd really like to avoid that.

  8. jacob314 commented on Apr 19, 2019

    @jacob314
    Contributor

    I agree that warning that Firefox is not tested but still allowing it to open is fine.
    The main thing we want to avoid is giving users a bad experience because they accidentally opened the tool with a browser we don't support.

  9. TamasBarta commented on Jun 26, 2019

    @TamasBarta

    Just curiosity: is there anything specific you know about which feature won't work in Firefox, or you just generally don't trust Firefox?

    Edit: I checked, and the tabs' contents don't show up. I'm still curious how could this happen, but OK, looks like Chromium is the way to go for now.

  10. agilob commented on Nov 9, 2019

    @agilob

    I spoofed UA in firefox using https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher and devtools works fine.

  11. Blend3rman commented on Mar 11, 2020

    @Blend3rman

    This just feels dirty now. Basically DevTools is simply looking at the useragent string and deciding whether or not to show up. You could merely add a warning banner saying that Firefox support is untested, why do you have to completely disallow running DevTools on Firefox? As far as I have used DevTools it works perfectly fine on FF, seeing as how it's just a regular websocket, which is supposed to be universally supported by all browsers.

    I just feel like gatekeeping which browsers users may use is not a good way to go about this.

  12. 12people commented on Mar 11, 2020

    @12people
    Author

    @jacob314 Would you consider reopening this issue? It seems like Devtools work just fine in Firefox and allowing it along with a warning about the browser not being tested would be a good solution for those wanting to use the browser.

  13. Kogia-sima commented on Apr 1, 2020

    @Kogia-sima

    I love Firefox. I hope this will be fixed.

  14. hacker1024 commented on Jun 2, 2020

    @hacker1024

    It should be possible to get to the beta Flutter DevTools implementation in Firefox.

  15. Nico04 commented on Jun 25, 2020

    @Nico04

    What about now, with new Flutter release of the Dart Devtools?

  16. devoncarew commented on Jun 26, 2020

    @devoncarew
    Contributor

    Re-opening to track up-votes.

  17. kenzieschmoll commented on Jun 26, 2020

    @kenzieschmoll
    Member

    From some local testing, it looks like firefox may just work now that we are shipping with Flutter.

  18. Nico04 commented on Jun 27, 2020

    @Nico04

    From some local testing, it looks like firefox may just work now that we are shipping with Flutter.

    I've just tested myseft, and yes, it seems that it opens in Firefox without any issue nor warning now, that's great !

  19. desthercz commented on Jun 27, 2020

    @desthercz

    It works great, i don't see any reason why we can't set default browser in config. It really feels like unnecessary gatekeeping.

  20. kenzieschmoll commented on Sep 18, 2020

    @kenzieschmoll
    Member

    transferred request to set default browser to a different issue #2357. Closing this as fixed.

  21. stagefright5 commented on Sep 25, 2020

    @stagefright5

    Also, the official flutter web docs still says you "require" chrome for debugging.
    Please change it to something like, "we recommend chrome". Here is the link

    image

  22. NatoBoram commented on Feb 18, 2021

    @NatoBoram

    That's because you can't flutter run -d firefox

  23. NatoBoram commented on Jul 7, 2021

    @NatoBoram

    Is there a way to do It now?

    You can flutter run -d web-server and open it in Firefox, but Dart Debug is not available for Firefox, so no DevTools available either.

    It's July 2021, any updates?

    No.

  24. silpol commented on Jul 21, 2024

    @silpol

    It's July 2024 and it's clear now Google is gatekeeping Firefox. If there was will, it could be done with GSoC program so main resources are not engaged. Three years...

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions