10 ms·

Firefox 70 released for Firefox Quantum: Developer Edition

362 points by romelsongalia 7y ago

CJefferson 7y ago
Can anyone explain exactly what's different about this? Are all these features not in normal Firefox? Is this like a beta of normal firefox, set of extensions, or a significant fork?
- pjmlp 7y ago
  They are not, apparently the reasoning was not to make Firefox bigger with needless features not requires by non-techie users. At least this is how I recall it, please anyone correct me if I am mistaken.
  - fimdomeio 7y ago
    It's a beta with special features for developers. right now dev edition for me is 70.0b1 regular is firefox 68.0.2 It also has the new logo and I suppose there's new stuff on the dev tools. "What's new" page is broken so not absolutely sure.
    - giancarlostoro 7y ago
      Definitely a few developer friendly plugins like one that parses and renders JSON responses in a new tab instead of showing unformatted plain-text.
    - jonathaneunice 7y ago
      Seems very much a beta for developers. Some cool dev features promised, but didn't always work as demoed. Font parameter manipulation for example. UI's there and pretty...it just doesn't affect the look/styling of fonts rendered on a real site like it does their demo site. Also, a number of UI controls slow to respond (e.g. cursors for dragging, clicking, etc.) β β β so very β
- ptx 7y ago
  I think it's mainly a difference in configuration. The developer version, IIRC, allows you to install extensions on your own machine without seeking approval from Mozilla, but on the other hand it apparently subjects you to additional telemetry: > Firefox Developer Edition automatically sends feedback to Mozilla ... In addition to the data collection described in this Privacy Notice, these versions by default may send certain types of web activity and crash data to Mozilla and in some cases to our partners.
  - gigatexal 7y ago
    When was the last time devs took time out of their day to create detailed bug reports with crash logs and context? Telemetry done right is just a way to surface bugs properly.
    - mcny 7y ago
      I use nightly as my main browser because I want Mozilla to see my bugs. And I want Mozilla to not do telemetry in production. No such luck.
  - bovine3dom 7y ago
    If you just want to be able to install unsigned extensions with neither the extra bugs from running a beta nor the telemetry, you can use the far less advertised "unbranded builds" of Firefox [1] instead. [1]: https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Builds https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu...
    - yjftsjthsd-h 7y ago
      Don't the unbranded builds also lack automatic updating?
      - bovine3dom 7y ago
        It's possible. Last I heard was that the unbranded builds were too eager to update [1] so it could well have been disabled totally. The Mozilla wiki doesn't mention anything about updating being disabled which to me implies it is not. If you find out for certain, please let me know! I don't personally use the builds as Mozilla has not yet blocked signing of our extensions and `web-ext run` serves me well for development. Automated signing is not brilliantly documented but works well enough [2-3] to ensure that our builds are tested by real users before we release a stable version. [1]: https://www.ghacks.net/?p=123637 https://www.ghacks.net/?p=123637 [2]: https://github.com/tridactyl/tridactyl/blob/f45c990eac074df815e9cd8c27bf7a56b0527bbd/scripts/sign#L5 https://github.com/tridactyl/tridactyl/blob/f45c990eac074df8... [3]: https://github.com/tridactyl/buildbot/blob/master/autobuild.sh https://github.com/tridactyl/buildbot/blob/master/autobuild....
- input_sh 7y ago
  Special features: kind of like an IDE on top of Firefox, meant to be used by web developers. Comes with its own config profile, so you can fuck around and not break stuff in stable/beta that you are supposed to have concurrently installed. Kind of like beta: all of the new APIs and features related to web development are there three months before they hit stable.
  - shawnz 7y ago
    The retail edition of Firefox already includes dev tools.
    - input_sh 7y ago
      ...and Firefox Developer comes with dev tool features that have not yet reached Firefox Stable.
      - ihuman 7y ago
        Which ones are not in the stable version yet?
- deleted 7y ago
  [deleted]
- sciurus 7y ago
  It is based on the beta release channel and has some configuration tweaks. See https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Developer_Edition https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Dev...
fareesh 7y ago
I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
- me_bx 7y ago
  I guess it's a question of habit. I have the same problem in the opposite directions: the interface of Chromium developer console is unfriendly to me, I never manage to get comfortable with it...
  - lol768 7y ago
    >I have the same problem in the opposite directions Me too, as one example: Chrome had no way to edit/re-send AJAX requests for the longest time
- tenryuu 7y ago
  meanwhile I'm the exact opposite. I've been using the firefox dev tools too much that using chrome on someone else's machine is something I feel like I have to put up with. That's not me saying Firefox's tools are actually better though, there's still a number of weird quirks or features that could be lacking, while also having features I can't find in chrome that I also take for granted
- bleuarff 7y ago
  Each has their pros and cons. My favorite features in FF devtools which are missing from Chrome are CSS diff and the advanced filtering in the network panel. Chrome filtering only works on hosts, while FF can filter in query strings and other sections of a request.
  - jefftk 7y ago
    I often use network filtering in Chrome devtools to find requests by query string. If you start typing into the search box it matches it against the whole request including url parameters.
gigatexal 7y ago
Not a front end dev but this looks really neat.
zaphirplane 7y ago
What’s the Mozilla community like for external contributions? Before the big google dollars it seemed cliquey and now seems mostly paid people. Is that accurate ? I wonder what happens to Firefox if the search dollars run out and companies are uniting behind chrome/WebKit
- The_rationalist 7y ago
  I regularly watch commits from webkit, chromium, gecko-dev and servo. Webkit is developed almost exclusively by Apple (or more maintained because development is very slow, btw I suspect that Apple will drop webkit as it become too far behind) There are also a few igalia devs and one Sony dev + one Gmail dev. Chromium is developed by so many people, Google, Microsoft, opera, QT, hardware makers (ARM, Intel, nvidia), some enterprises, and many contributors (I wonder if chromium has more opensource non paid contributor than gecko) Servo is mostly developed by paid mozilla devs, but had major improvements made by contributors. Proportionally far more non paid contributor than the gecko of today, I expect mostly because they work on github which is more friendly than bugzilla and mailing lists... Gecko dev today non paid developers are a few minority. If Firefox does not die by himself, expect Google to slowly stop paying them Thus mozilla will die which would be a great loss. Mozilla could save it's future, mozilla could become sustainable: I made a proposal here: https://github.com/servo/servo/issues/24026 https://github.com/servo/servo/issues/24026
  - leadingthenet 7y ago
    What a terrible argument. I really don’t understand how people don’t see the negative effects of browser monoculture. I feel like I’d just be rehashing the same old points :(
    - The_rationalist 7y ago
      Which argument? Firefox is dying, it's a fact, watch the marketshare over time. Were you referring to my proposal on github?
archie2 7y ago
Has there been a significant update to the devtools recently? I've been a devedition user for years, odd to see it on the front page of HN just linking to the homepage..
- SquareWheel 7y ago
  This is why I dislike these software posts without context. It's never clear if there's been an update or if the submitter just discovered them for the first time.
  - Mister_Snuggles 7y ago
    I really wish posts like this, and posts that are just random Wikipedia articles, would have a paragraph (or at least a sentence) from the submitter. Why is this interesting? For Wikipedia articles about people this is doubly important because the title is inevitably just the person's name - unless you already know who that person is there's no hint as to why they are significant.
    - deleted 7y ago
      [deleted]
    - sweeneyrod 7y ago
      Disagree. I like the way this system stops submitters giving their potentially half-baked opinions on articles, and adds an element of mystery to things.
      - duxup 7y ago
        I'm inclined to agree, tossing in the poster's spin tends to drive the topic, often to odd places rather than the actual thing. At the same time links to pages without any context as to why leaves me wondering why I should be looking at this page. Particularly product pages that are not easy to parse what the point is sometimes.
rasfincher 7y ago
Am I crazy or does Option-Command-S not open the Debugger as it says in the Debugger tutorial?
- OrgNet 7y ago
  You made me discover a new shortcut... <ctrl>-<shift>-<s> opens the screenshot tool ... too bad they removed the cloud hosting feature though...
lovetocode 7y ago
Did they fix the memory bloat on Mac OS? It’s pretty much useless to me on MacOS.
- mosselman 7y ago
  Wondering about this as well. On my 2017 MacBook Pro with touchbar I don't notice the performance hit, but on my 2015 MacBook Pro the whole system freezes with Firefox. What completely solves this however is enabling 'low res mode' (right click app icon -> get info -> check the low-resolution checkbox). But, as the name suggest, Firefox now runs in non-retina resolution. It looks crappier, but I still prefer it to other browsers.
- tbassetto 7y ago
  I saw a tweet recently about macOS power consumption fixes: https://mobile.twitter.com/pcwalton/status/1166193770016079872 https://mobile.twitter.com/pcwalton/status/11661937700160798... Haven't noticed any memory bloat myself though (= it consumes a lot of memory, like any browsers). It's somewhere between Safari and Chrome.
  - lovetocode 7y ago
    Good to know thanks. The last time I used it it was taking up nine gigs of RAM with only one tab open. Maybe I’ll give it a go again
  - The_rationalist 7y ago
    Random question: Do you use safari? Do you see significant performance differences with chrome? Do you see broken/partially broken websites on safari vs chrome ?
    - tbassetto 7y ago
      I only use Safari on my personal computer. And at work I use Firefox for development, and Safari for personal stuff. I used to use Chrome but nowadays it's very rare (testing something specific). The thing is, Chrome actually feels snappier than both Firefox and Safari when I am using it, probably because it's profile is empty (almost no extensions, no history, etc.). I rarely see broken websites, with any browser. And usually it's because of my ad-blocking extensions. Google websites are slower on Firefox, but rumours are saying that it's almost on purpose… (one more reason to not use Google products like Chrome).
iicc 7y ago
Would love to see something like this for Android (Android firefox doesn't have developer tools to save space).
- The_rationalist 7y ago
  It's not to save space, they could download it opt-in.. It's because they don't have the resources and have many P1 features to catch up.
- mpnordland 7y ago
  You can turn on usb debugging and attach to it from your computer. Then go to about:debugging to inspect, add breakpoints, etc.
karthickshiva 7y ago
Why Firefox is not allowing us to edit JS code as allowed by Chrome.
maxheadroom 7y ago
Should the title have a (2017) at the end, since Quantum initially came out then[0,1]? (I understand it points to a current-version but it seems like, from the comments, it's being mistaken for having recently been released.) [0] - https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-beta-developer-edition/ https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-bet... [1] - https://en.wikipedia.org/wiki/Firefox_version_history#Firefox_52_through_59 https://en.wikipedia.org/wiki/Firefox_version_history#Firefo...
- Kuinox 7y ago
  No, i'm using the developer edition and got the update only this morning. But I don't know if something have changed...
  - knd775 7y ago
    The Quantum version of Firefox (and Firefox Developer) did not come out this morning. You likely just got a routine build update.
    - wlesieutre 7y ago
      It bumped up from 69 to 70 this morning, a "major" update so much as browsers have those anymore. But it's not clear what's actually new in this. Here's what they listed for 70.0a1 back in July, but the release notes link for today's update is a dead end. https://www.mozilla.org/en-US/firefox/70.0a1/releasenotes/ https://www.mozilla.org/en-US/firefox/70.0a1/releasenotes/
      - konart 7y ago
        Dev edtition gets the last nightly build two weeks before the same release hits Beta channel. One of the main changes for me as a Mac user is this: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32 https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32
        7y ago
AlphaWeaver 7y ago
FYI, this post is because Firefox 70 was released for Firefox Quantum: Developer Edition. Should the title be changed?
nocture 7y ago
Worth noting, this landed a patch that moves some of the UI work to Core Animation on MacOS[1]. More work will happen that builds on top of this, but some reports in that ticket are promising already. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 https://bugzilla.mozilla.org/show_bug.cgi?id=1429522
- minedwiz 7y ago
  Finally
- GeekyBear 7y ago
  Moving from OpenGL to Core Animation has required a huge amount of work, but even at this early stage (before many of the changes in progress land) the power savings and performance gains are already significant. Good work, and much appreciated!
tajstar 7y ago
Quantum has been out for some time but it seems have updated some of the dev tools as well as added in a new shape editor and fonts panel, something that is not available in chrome. looking forward to trying these out.
demarq 7y ago
Even though I stayed away from FF because of it's macos issues, I found myself using it(normal ff) for development. I'm not the only one at work either. It's a weird angle for a browser to compete from, but I guess it's working.
badrabbit 7y ago
What happened to Servo?

362 points by romelsongalia 7y ago

Can anyone explain exactly what's different about this? Are all these features not in normal Firefox? Is this like a beta of normal firefox, set of extensions, or a significant fork?

pjmlp 7y ago
They are not, apparently the reasoning was not to make Firefox bigger with needless features not requires by non-techie users. At least this is how I recall it, please anyone correct me if I am mistaken.
- fimdomeio 7y ago
  It's a beta with special features for developers. right now dev edition for me is 70.0b1 regular is firefox 68.0.2 It also has the new logo and I suppose there's new stuff on the dev tools. "What's new" page is broken so not absolutely sure.
  - giancarlostoro 7y ago
    Definitely a few developer friendly plugins like one that parses and renders JSON responses in a new tab instead of showing unformatted plain-text.
  - jonathaneunice 7y ago
    Seems very much a beta for developers. Some cool dev features promised, but didn't always work as demoed. Font parameter manipulation for example. UI's there and pretty...it just doesn't affect the look/styling of fonts rendered on a real site like it does their demo site. Also, a number of UI controls slow to respond (e.g. cursors for dragging, clicking, etc.) β β β so very β
ptx 7y ago
I think it's mainly a difference in configuration. The developer version, IIRC, allows you to install extensions on your own machine without seeking approval from Mozilla, but on the other hand it apparently subjects you to additional telemetry: > Firefox Developer Edition automatically sends feedback to Mozilla ... In addition to the data collection described in this Privacy Notice, these versions by default may send certain types of web activity and crash data to Mozilla and in some cases to our partners.
- gigatexal 7y ago
  When was the last time devs took time out of their day to create detailed bug reports with crash logs and context? Telemetry done right is just a way to surface bugs properly.
  - mcny 7y ago
    I use nightly as my main browser because I want Mozilla to see my bugs. And I want Mozilla to not do telemetry in production. No such luck.
- bovine3dom 7y ago
  If you just want to be able to install unsigned extensions with neither the extra bugs from running a beta nor the telemetry, you can use the far less advertised "unbranded builds" of Firefox [1] instead. [1]: https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Builds https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu...
  - yjftsjthsd-h 7y ago
    Don't the unbranded builds also lack automatic updating?
    - bovine3dom 7y ago
      It's possible. Last I heard was that the unbranded builds were too eager to update [1] so it could well have been disabled totally. The Mozilla wiki doesn't mention anything about updating being disabled which to me implies it is not. If you find out for certain, please let me know! I don't personally use the builds as Mozilla has not yet blocked signing of our extensions and `web-ext run` serves me well for development. Automated signing is not brilliantly documented but works well enough [2-3] to ensure that our builds are tested by real users before we release a stable version. [1]: https://www.ghacks.net/?p=123637 https://www.ghacks.net/?p=123637 [2]: https://github.com/tridactyl/tridactyl/blob/f45c990eac074df815e9cd8c27bf7a56b0527bbd/scripts/sign#L5 https://github.com/tridactyl/tridactyl/blob/f45c990eac074df8... [3]: https://github.com/tridactyl/buildbot/blob/master/autobuild.sh https://github.com/tridactyl/buildbot/blob/master/autobuild....
input_sh 7y ago
Special features: kind of like an IDE on top of Firefox, meant to be used by web developers. Comes with its own config profile, so you can fuck around and not break stuff in stable/beta that you are supposed to have concurrently installed. Kind of like beta: all of the new APIs and features related to web development are there three months before they hit stable.
- shawnz 7y ago
  The retail edition of Firefox already includes dev tools.
  - input_sh 7y ago
    ...and Firefox Developer comes with dev tool features that have not yet reached Firefox Stable.
    - ihuman 7y ago
      Which ones are not in the stable version yet?
deleted 7y ago
[deleted]
sciurus 7y ago
It is based on the beta release channel and has some configuration tweaks. See https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Developer_Edition https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Dev...

fareesh 7y ago

I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.

me_bx 7y ago
I guess it's a question of habit. I have the same problem in the opposite directions: the interface of Chromium developer console is unfriendly to me, I never manage to get comfortable with it...
- lol768 7y ago
  >I have the same problem in the opposite directions Me too, as one example: Chrome had no way to edit/re-send AJAX requests for the longest time
tenryuu 7y ago
meanwhile I'm the exact opposite. I've been using the firefox dev tools too much that using chrome on someone else's machine is something I feel like I have to put up with. That's not me saying Firefox's tools are actually better though, there's still a number of weird quirks or features that could be lacking, while also having features I can't find in chrome that I also take for granted
bleuarff 7y ago
Each has their pros and cons. My favorite features in FF devtools which are missing from Chrome are CSS diff and the advanced filtering in the network panel. Chrome filtering only works on hosts, while FF can filter in query strings and other sections of a request.
- jefftk 7y ago
  I often use network filtering in Chrome devtools to find requests by query string. If you start typing into the search box it matches it against the whole request including url parameters.

gigatexal 7y ago

Not a front end dev but this looks really neat.

zaphirplane 7y ago

What’s the Mozilla community like for external contributions? Before the big google dollars it seemed cliquey and now seems mostly paid people. Is that accurate ? I wonder what happens to Firefox if the search dollars run out and companies are uniting behind chrome/WebKit

The_rationalist 7y ago
I regularly watch commits from webkit, chromium, gecko-dev and servo. Webkit is developed almost exclusively by Apple (or more maintained because development is very slow, btw I suspect that Apple will drop webkit as it become too far behind) There are also a few igalia devs and one Sony dev + one Gmail dev. Chromium is developed by so many people, Google, Microsoft, opera, QT, hardware makers (ARM, Intel, nvidia), some enterprises, and many contributors (I wonder if chromium has more opensource non paid contributor than gecko) Servo is mostly developed by paid mozilla devs, but had major improvements made by contributors. Proportionally far more non paid contributor than the gecko of today, I expect mostly because they work on github which is more friendly than bugzilla and mailing lists... Gecko dev today non paid developers are a few minority. If Firefox does not die by himself, expect Google to slowly stop paying them Thus mozilla will die which would be a great loss. Mozilla could save it's future, mozilla could become sustainable: I made a proposal here: https://github.com/servo/servo/issues/24026 https://github.com/servo/servo/issues/24026
- leadingthenet 7y ago
  What a terrible argument. I really don’t understand how people don’t see the negative effects of browser monoculture. I feel like I’d just be rehashing the same old points :(
  - The_rationalist 7y ago
    Which argument? Firefox is dying, it's a fact, watch the marketshare over time. Were you referring to my proposal on github?

archie2 7y ago

Has there been a significant update to the devtools recently? I've been a devedition user for years, odd to see it on the front page of HN just linking to the homepage..

SquareWheel 7y ago
This is why I dislike these software posts without context. It's never clear if there's been an update or if the submitter just discovered them for the first time.
- Mister_Snuggles 7y ago
  I really wish posts like this, and posts that are just random Wikipedia articles, would have a paragraph (or at least a sentence) from the submitter. Why is this interesting? For Wikipedia articles about people this is doubly important because the title is inevitably just the person's name - unless you already know who that person is there's no hint as to why they are significant.
  - deleted 7y ago
    [deleted]
  - sweeneyrod 7y ago
    Disagree. I like the way this system stops submitters giving their potentially half-baked opinions on articles, and adds an element of mystery to things.
    - duxup 7y ago
      I'm inclined to agree, tossing in the poster's spin tends to drive the topic, often to odd places rather than the actual thing. At the same time links to pages without any context as to why leaves me wondering why I should be looking at this page. Particularly product pages that are not easy to parse what the point is sometimes.

rasfincher 7y ago

Am I crazy or does Option-Command-S not open the Debugger as it says in the Debugger tutorial?

OrgNet 7y ago
You made me discover a new shortcut... <ctrl>-<shift>-<s> opens the screenshot tool ... too bad they removed the cloud hosting feature though...

lovetocode 7y ago

Did they fix the memory bloat on Mac OS? It’s pretty much useless to me on MacOS.

mosselman 7y ago
Wondering about this as well. On my 2017 MacBook Pro with touchbar I don't notice the performance hit, but on my 2015 MacBook Pro the whole system freezes with Firefox. What completely solves this however is enabling 'low res mode' (right click app icon -> get info -> check the low-resolution checkbox). But, as the name suggest, Firefox now runs in non-retina resolution. It looks crappier, but I still prefer it to other browsers.
tbassetto 7y ago
I saw a tweet recently about macOS power consumption fixes: https://mobile.twitter.com/pcwalton/status/1166193770016079872 https://mobile.twitter.com/pcwalton/status/11661937700160798... Haven't noticed any memory bloat myself though (= it consumes a lot of memory, like any browsers). It's somewhere between Safari and Chrome.
- lovetocode 7y ago
  Good to know thanks. The last time I used it it was taking up nine gigs of RAM with only one tab open. Maybe I’ll give it a go again
- The_rationalist 7y ago
  Random question: Do you use safari? Do you see significant performance differences with chrome? Do you see broken/partially broken websites on safari vs chrome ?
  - tbassetto 7y ago
    I only use Safari on my personal computer. And at work I use Firefox for development, and Safari for personal stuff. I used to use Chrome but nowadays it's very rare (testing something specific). The thing is, Chrome actually feels snappier than both Firefox and Safari when I am using it, probably because it's profile is empty (almost no extensions, no history, etc.). I rarely see broken websites, with any browser. And usually it's because of my ad-blocking extensions. Google websites are slower on Firefox, but rumours are saying that it's almost on purpose… (one more reason to not use Google products like Chrome).

iicc 7y ago

Would love to see something like this for Android (Android firefox doesn't have developer tools to save space).

The_rationalist 7y ago
It's not to save space, they could download it opt-in.. It's because they don't have the resources and have many P1 features to catch up.
mpnordland 7y ago
You can turn on usb debugging and attach to it from your computer. Then go to about:debugging to inspect, add breakpoints, etc.

karthickshiva 7y ago

Why Firefox is not allowing us to edit JS code as allowed by Chrome.

maxheadroom 7y ago

Should the title have a (2017) at the end, since Quantum initially came out then[0,1]? (I understand it points to a current-version but it seems like, from the comments, it's being mistaken for having recently been released.) [0] - https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-beta-developer-edition/ https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-bet... [1] - https://en.wikipedia.org/wiki/Firefox_version_history#Firefox_52_through_59 https://en.wikipedia.org/wiki/Firefox_version_history#Firefo...

Kuinox 7y ago
No, i'm using the developer edition and got the update only this morning. But I don't know if something have changed...
- knd775 7y ago
  The Quantum version of Firefox (and Firefox Developer) did not come out this morning. You likely just got a routine build update.
  - wlesieutre 7y ago
    It bumped up from 69 to 70 this morning, a "major" update so much as browsers have those anymore. But it's not clear what's actually new in this. Here's what they listed for 70.0a1 back in July, but the release notes link for today's update is a dead end. https://www.mozilla.org/en-US/firefox/70.0a1/releasenotes/ https://www.mozilla.org/en-US/firefox/70.0a1/releasenotes/
    - konart 7y ago
      Dev edtition gets the last nightly build two weeks before the same release hits Beta channel. One of the main changes for me as a Mac user is this: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32 https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32
      - 7y ago

AlphaWeaver 7y ago

FYI, this post is because Firefox 70 was released for Firefox Quantum: Developer Edition. Should the title be changed?

nocture 7y ago

Worth noting, this landed a patch that moves some of the UI work to Core Animation on MacOS[1]. More work will happen that builds on top of this, but some reports in that ticket are promising already. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 https://bugzilla.mozilla.org/show_bug.cgi?id=1429522

minedwiz 7y ago
Finally
GeekyBear 7y ago
Moving from OpenGL to Core Animation has required a huge amount of work, but even at this early stage (before many of the changes in progress land) the power savings and performance gains are already significant. Good work, and much appreciated!

tajstar 7y ago

Quantum has been out for some time but it seems have updated some of the dev tools as well as added in a new shape editor and fonts panel, something that is not available in chrome. looking forward to trying these out.

demarq 7y ago

Even though I stayed away from FF because of it's macos issues, I found myself using it(normal ff) for development. I'm not the only one at work either. It's a weird angle for a browser to compete from, but I guess it's working.

badrabbit 7y ago

What happened to Servo?