You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
Reacted by Michael Pfaff, ShameenShetty, desthercz, Tamás Nagy, Richard Cooper, Dhaval Patel, Zoltán Ujszászi, Jeff Casavant, yapdianhao, Saran Tanpituckpong ✔️ and 18 more
@stevemessick#66 is about displaying messages in unsupported browsers. This bug is about supporting a browser other than Chrome. Two very different things.
Reacted by Andriy Tymchenko, Evgen Fil, Wakeel Furqan Ahmed and Roscoe Rubin-Rottenberg
@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.
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.
@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.
Reacted by Foorack / Max Faxälv, Tamás Barta, Kurt Wilson, Yogeshwar Bala, Addison Heavner, Alexandre, Y.M.S, Allan Laal, lucas, Saran Tanpituckpong ✔️ and 1 more
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.
Reacted by 12people, Pranjal Rastogi and Richard Popeliš
Reacted by Yogeshwar Bala, Addison Heavner, Alexandre, Y.M.S, Richard Cooper, Zoltán Ujszászi, UsetIT, mohd-taba, Nato Boram and Andriy Tymchenko
Reacted by Anton Kuzmin, Lambda4, Tamás Barta, Vivek Kekuda, LinArcX, Eduardo Moreno, Richard Cooper and Evgen Fil
Reacted by Siggi Gunnarss, Chinloyal, Yogeshwar Bala, Eduardo Moreno, Michael Pfaff, ShameenShetty, Richard Cooper, Zoltán Ujszászi, William Oprandi, Benedict Dube and 1 more
Reacted by Yogeshwar Bala, Eduardo Moreno, Michael Pfaff, ShameenShetty and Nicolas Bourras
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.
Reacted by 12people, agilob, Kogia-sima, Vitalii Hurianov, Addison Heavner, Alexandre, Eduardo Moreno, Michael Pfaff, Nicolas B, magus9001 and 19 more
@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.
Reacted by Y.M.S, Zoltán Ujszászi and EriKWDev
Reacted by Yogeshwar Bala, Eduardo Moreno, Michael Pfaff, ShameenShetty, 8fdafs2, Richard Cooper, Maxime Alardo, Nato Boram and Andriy Tymchenko
Reacted by M.Mahdi Bakhshi, Richard Popeliš, Eduardo Moreno, Samuel Martineau, ShameenShetty, hearot, Nicolas B, 8fdafs2, Костадин Дамянов, Y.M.S and 10 more
Reacted by Nicolas B, 8fdafs2, Marlon Macedo, Y.M.S, Richard Cooper, Lucas Salas, Zoltán Ujszászi, 12people, Saran Tanpituckpong ✔️, Marcus Xavier and 16 more
It works great, i don't see any reason why we can't set default browser in config. It really feels like unnecessary gatekeeping.
Reacted by Alif Taufik, Marlon Macedo, ductranit, Костадин Дамянов, Y.M.S, Richard Cooper, Michael Pfaff, Zoltán Ujszászi, 12people, Jaween Ediriweera and 4 more
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
Reacted by Nicolas B, Saran Tanpituckpong ✔️, Tamás Barta, Rohan Bansal, Maxime Alardo, Nato Boram, maan2003, lucas, Andriy Tymchenko, Benedict Dube and 1 more
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...
Reacted by Saran Tanpituckpong ✔️, Ciro García Belmonte, Leora, Raúl Gutiérrez and Lyubomir
Activity
stevemessick commentedon Apr 2, 2019
Dup of #66
12people commentedon Apr 2, 2019
@stevemessick #66 is about displaying messages in unsupported browsers. This bug is about supporting a browser other than Chrome. Two very different things.
stevemessick commentedon Apr 2, 2019
#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.
12people commentedon Apr 2, 2019
@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.
jacob314 commentedon Apr 2, 2019
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.
Afsar-Pasha commentedon Apr 15, 2019
@12people Try changing UA string using this addon.
12people commentedon Apr 19, 2019
@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.
jacob314 commentedon Apr 19, 2019
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.
TamasBarta commentedon Jun 26, 2019
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.
agilob commentedon Nov 9, 2019
I spoofed UA in firefox using https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher and devtools works fine.
Blend3rman commentedon Mar 11, 2020
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.
12people commentedon Mar 11, 2020
@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.
Kogia-sima commentedon Apr 1, 2020
I love Firefox. I hope this will be fixed.
hacker1024 commentedon Jun 2, 2020
It should be possible to get to the beta Flutter DevTools implementation in Firefox.
Nico04 commentedon Jun 25, 2020
What about now, with new Flutter release of the Dart Devtools?
devoncarew commentedon Jun 26, 2020
Re-opening to track up-votes.
kenzieschmoll commentedon Jun 26, 2020
From some local testing, it looks like firefox may just work now that we are shipping with Flutter.
Nico04 commentedon Jun 27, 2020
I've just tested myseft, and yes, it seems that it opens in Firefox without any issue nor warning now, that's great !
desthercz commentedon Jun 27, 2020
It works great, i don't see any reason why we can't set default browser in config. It really feels like unnecessary gatekeeping.
kenzieschmoll commentedon Sep 18, 2020
transferred request to set default browser to a different issue #2357. Closing this as fixed.
stagefright5 commentedon Sep 25, 2020
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
NatoBoram commentedon Feb 18, 2021
That's because you can't
flutter run -d firefoxNatoBoram commentedon Jul 7, 2021
You can
flutter run -d web-serverand open it in Firefox, but Dart Debug is not available for Firefox, so no DevTools available either.No.
silpol commentedon Jul 21, 2024
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...