Why do people seem to prefer Chrome's devtools over Firefox's?
1–10 of 101 posts
Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#2Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#3I develop, test, and debug on browsers that my users are using, and that ain't Firefox.
Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#4Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#5Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#6Example: Say firefox has been started from the Destop already and now I want to start a new Firefox window from a root terminal:
su desktopuser firefox
It does not work. It gives me "Firefox is already running, but is not responding.".Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#7For some reason, new Firefox windows can only be launched from the same environment from which the first window has been started. Even the same user who started FF cannot launch a new window from a new shell. That constantly interferes with my workflow. Example: Say firefox has been started from the Destop already and now I want to start a new Firefox window from a root terminal: su desktopuser firefox It does not wo…
Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#8Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#9I develop, test, and debug on browsers that my users are using, and that ain't Firefox.
Re: Why do people seem to prefer Chrome's devtools over Firefox's?
#10For some reason, new Firefox windows can only be launched from the same environment from which the first window has been started. Even the same user who started FF cannot launch a new window from a new shell. That constantly interferes with my workflow. Example: Say firefox has been started from the Destop already and now I want to start a new Firefox window from a root terminal: su desktopuser firefox It does not wo…
Use --new-instance.
Firefox is already running, but is not responding.
Have you tried it?