Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Mozilla Programming The Internet

Mozilla Launches Browser Built For Developers 74

HughPickens.com writes "Mozilla announced that they are excited to unveil Firefox Developer Edition, the first browser created specifically for developers that integrates two powerful new features, Valence and WebIDE that improve workflow and help you debug other browsers and apps directly from within Firefox Developer Edition. Valence (previously called Firefox Tools Adapter) lets you develop and debug your app across multiple browsers and devices by connecting the Firefox dev tools to other major browser engines. WebIDE allows you to develop, deploy and debug Web apps directly in your browser, or on a Firefox OS device. "It lets you create a new Firefox OS app (which is just a web app) from a template, or open up the code of an existing app. From there you can edit the app's files. It's one click to run the app in a simulator and one more to debug it with the developer tools."

Firefox Developer Edition also includes all the tools experienced Web developers are familiar with including: Responsive Design Mod, Page Inspector, Web Console, JavaScript Debugger, Network Monitor, Style Editor, and Web Audio Editor. At launch, Mozilla is starting off with Chrome for Android and Safari for iOS. and the eventual goal is to support more browsers, depending on what developers tell Mozilla they want, but the primary focus is on the mobile Web. "One of the biggest pain points for developers is having to use numerous siloed development environments in order to create engaging content or for targeting different app stores. For these reasons, developers often end up having to bounce between different platforms and browsers, which decreases productivity and causes frustration," says the press release. "If you're a new Web developer, the streamlined workflow and the fact that everything is already set up and ready to go makes it easier to get started building sophisticated applications."
Mozilla released a teaser trailer for the browser last week.
This discussion has been archived. No new comments can be posted.

Mozilla Launches Browser Built For Developers

Comments Filter:
  • I just kinda wish it was Chrome that came out with it.. In general I just prefer the layout of their development tools. I'll definitely give this a try though.

    • This, except the part about giving it a try. Firebug revolutionized everything when it first came out, but it's failed to improve in the way Chrome Developer Tools ... and Firefox's own developer tools have remained far behind both the entire time.

      After ignoring the web development community for so long, I have a hard time seeing myself ever going back to Firefox unless they get some *seriously* rave reviews.

  • by ArcadeMan ( 2766669 ) on Monday November 10, 2014 @11:16AM (#48350571)

    So, they're running Android and iOS on your computer to run the same binaries as those platforms? If not, it's only emulation and when someone says they're emulating another browser the result is usually not worth it and nowhere close to the actual results on the other platforms.

    • So, they're running Android and iOS on your computer to run the same binaries as those platforms?

      Of course not. But, of course, you have to find something to hate on. Mozilla can do no right.

      If not, it's only emulation

      Which is a decent first step.

      when someone says they're emulating another browser the result is usually not worth it and nowhere close to the actual results on the other platforms.

      Yep, and only an idiot would rely on the results of emulation and not engage in on-target testing.

    • by BZ ( 40346 ) on Monday November 10, 2014 @11:40AM (#48350785)

      > So, they're running Android and iOS on your
      > computer to run the same binaries as those
      > platforms?

      No. "They" are allowing you to connect your Android or iOS device to your computer (likely via USB), then debugging the on-device browser using the Firefox debugger running on your computer. That way you're debugging the thing you actually want to debug, but using the same developer tools you're using for your other debugging, and which therefore you're already familiar with.

      • by tepples ( 727027 )
        So you still have to buy an iPhone, an iPad, an Android phone, and an Android tablet to test on them, unless you're on a Mac with a running iOS Simulator and a way of simulating multitouch input. And according to this page [mozilla.org], the connection to Safari for iOS does not work on Windows, and an essential Linux component has to be built from source.
        • by BZ ( 40346 )

          > So you still have to buy an iPhone, an iPad, an
          > Android phone, and an Android tablet to test on them,

          Sure. The point here is to allow you to use the devtools of your choice, not to create a test environment.

        • by unrtst ( 777550 )

          So you still have to buy an iPhone, an iPad, an Android phone, and an Android tablet to test on them...

          1. If you're doing any serious development, you should have this already
          2. If your'e not very serious, then the andriod or ipad you personally use will be fine. For iPhone/iPad/etc testing, there is already a requirement to have something running Mac OSX + it's dev tools, or to own an i*thing* = no change here.

          ... and an essential Linux component has to be built from source.

          Oh no! They're expecting developers (the target audience) to *gasp* build something from source!!!

          Come on, there has to be more legitimate things to complain about!

          • by tepples ( 727027 )

            If you're doing any serious development [vs.] If your'e not very serious

            Then the question becomes one of making the transition from what you call "not very serious" to serious. Say a hobbyist web developer has developed a web application that he thinks will help him cross over from hobbyist to professional. Once he has something working on PC browsers and Android browser, where should he get funding to join the fruity ecosystem in order to test it on fruity machines before making it public? One could add "not yet tested on iPad; feedback is welcome" to the release notes, but th

            • by rHBa ( 976986 )

              ... and an essential Linux component has to be built from source.

              They're expecting developers (the target audience) to *gasp* build something from source!!!

              Knowledge of web development tools doesn't imply knowledge of native application development tools, nor vice versa.

              For most Windows users with knowledge of web development tools I'd generally agree but I'd have thought most Linux users (with knowledge of web development tools) would be fine doing a quick configure/make/make install.

          • Android makes their simulator (slow as it is) available for free, and it works on everything. iPhone wants you to buy a Mac so you can run XCode.

            I'm not going to spend money to improve another company's ecosystem. I'll code to standards and test with WebKit. Beyond that, Apple can suck it.

    • by tlhIngan ( 30335 )

      So, they're running Android and iOS on your computer to run the same binaries as those platforms? If not, it's only emulation and when someone says they're emulating another browser the result is usually not worth it and nowhere close to the actual results on the other platforms.

      I think it's more like remote viewing. You're running the real browser on a real device attached to your computer. The tools basically shove your code into that browser, capture the output, and then send the output back to your PC f

  • Instead of developers fixing websocket traceability [mozilla.org], they focus on making a new theme. Firefox has clearly too much designers. It's enough that every two or three versions the color of the developer console changes (and its design), and now an extra browser? I hope they don't transport the developer features into that browser, leaving firefox as a "customer only" product. When I was at places where I couldn't install software (libraries etc) I have been always happy to debug websites with the standard brows

  • Now the Firefox team can remove all the developer crap from the regular browser.

    Is amazing how most of the browsers, in order to pander to developers, became bloated with developer cruft. Do not get me wrong, getting developers to use your browser as primary is important. Nonetheless, this could have been done using the add-on/plug-in interfaces using an official set of add-ons/plug-ins, instead of bloating the browser.

    Here I hope that the offering of a specific browser for developers means that the consume

    • Now the Firefox team can remove all the developer crap from the regular browser.

      Removing even the most basic JavaScript console from the standard browser would be a bad idea. It'd encourage some developers of prominent web sites to block users of the developer browser as a "security" measure. Facebook and Netflix, for instance, already block use of the JavaScript console [ycombinator.com] out of "self-XSS" worries; removing even "view source" would make it even worse.

    • Re: (Score:2, Insightful)

      by Anonymous Coward

      Please don't. Even non-developers are increasingly using the basic devtools to manage the modern web (defeating right-clicks, removing elements that get in the way, etc). And far more practically, the dev tools let devs diagnose bugs with users as they happen, without having to frustrate them with lots of extra steps that might lose their session entirely. At this point it would be like removing images from the browser core just because blind people have no need for them.

    • Developers aren't marked from birth. The WWW took off because non-developers copied the html of various pages and made their own pages. Eventually some of them became developers. It's important to maintain at least some of these on-ramps.

      I'm no web dev but I often view the page source (e.g. so I can download a video instead of viewing it in my browser) or use "inspect element" (e.g. to get rid of some bar at the top or bottom taking up too much screen or being too distracting).

    • Comment removed based on user account deletion
  • I'm most interested to see if this means the release will be without a number of firefox's more annoying features, for example will I be free to disable warnings about third party extentions, and turn off the annoying messages about apps going fullscreen? Those alone would make me consider using it full time.
    • by Anonymous Coward

      Really? You're complaining about child-safety features and you're still not advanced enough to use addons or just go into about:config and change settings like full-screen-api.approval-required to false?

      Then what browser are you using that DOESN'T artificially kneecap or coddle you? Chrome won't even allow me to install third-party addons anymore.

  • We still use a Firefox 24 install for debugging GWT.

    http://www.gwtproject.org/miss... [gwtproject.org]

  • What they have "released" is just the Aurora channel with the Dev Tools theme covering all the browser.

    Everything else seems to be just the same that it used to be, the only improvement is the ability to run it side by side with another Firefox profile but if you used work with Aurora like I did, all this means that you must go back to the beta channel to keep an usable Firefox with a normal UI (after applying the Classic Theme Restorer)

    Their "mobile emulator" is quite simple, I don't understand why an
  • It's imperative that when I develop, that I'm developing and testing using the same browser an end user will have. Introducing differences where you have a developer and a non-developer browser is a bad idea.

    • by Anonymous Coward

      You still testing on/using the device in question. This just lets you connect to the device and debug things from the desktop firefox instance beside you, while you test on the device. Which is a damn sight better than having to install a ton of custom tools or try to figure it all out on the device (which is often a phone or other small-screened device). It's basically a debugging IDE.

    • Comment removed based on user account deletion
  • Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers.

    Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition.

  • The GUI is very bad. Black on black, nearly no contrast... I'm back to Pale Moon.

    Oh, and why is there no migration path between old sync and new sync? It's just a new authentication, everything under the hood is the same. If i run Pale Moon (old sync) and Firefox (new sync) i cannot have both of them, i'm forced to choose.

"The vast majority of successful major crimes against property are perpetrated by individuals abusing positions of trust." -- Lawrence Dalzell

Working...