Mozilla Firefox Version 38.0.1 Free Download Released with Fix for Critical Issues
Mozilla Firefox is no different as the company has been repeatedly launching one version after the other. Every time, they fix a new set of identified bugs, make plug-ins work better and also launch a new feature or two. The latest version of Firefox ...
Mozilla has a long history of innovating with how users interact with content: tabs, add-ons, live bookmarks, the Awesome bar – these and many more innovations have helped the Web to dominate desktop computing for the last decade. Six months ago we launched Directory Tiles in Firefox, and have had great success with commercial partnerships and in aiding awareness for content important to the project, including Mozilla advocacy campaigns in support of net neutrality and the Mozilla Manifesto.
Today, I’m pleased to announce Suggested Tiles – our latest innovation and complement to Directory Tiles, as we work to create a more powerful and personalized Web experience for our users. I discussed the Mozilla mission in the context of digital advertising earlier this year. Suggested Tiles represents an important step for us to improve the state of digital advertising for the Web, and to deliver greater user agency.
Much of today’s digital advertising utilizes data harvested through a user’s browsing habits to target ads. However, many consumers are increasingly weary of how their data is being collected and shared in the advertising ecosystem without transparency and consent – and complex opt-outs or unreadable privacy policies exacerbate this. Many users even block advertisements altogether. This situation is bad for users, bad for advertisers and bad for the Web.
With Suggested Tiles, we want to show the world that it is possible to do relevant advertising and content recommendations while still respecting users’ privacy and giving them control over their data. And to bring influence to bear on the whole industry, we know we will need to deliver a highly effective advertising product.
We believe users should be able easily to understand what content is promoted, who it is from and why they are seeing it. It is the user who owns the profile: only a Firefox user can edit their own browsing history. And for users who do not want to see Suggested Tiles, opting out only takes two clicks from the New Tab page, without having to read a lot of instructions. To deliver Suggested Tiles we do not retain or share personal data, nor are we using cookies. If you want to learn more about how Suggested Tiles protect a user’s data, we produced this infographic, and the Mozilla policy team have described the details of how our data principles translate to the data policy for Suggested Tiles.
Suggested Tiles are controlled by the user, respect their privacy and are not directed towards a captive audience. As different as this sounds, we believe that this makes Tiles a better experience for users and for advertisers.
Suggested Tiles will help advertisers and content owners connect with millions of Firefox users, and do so at a time when the user is receptive to hearing from them, making it a much more valuable connection. By delivering content experiences based on the user’s recent and most frequent browsing, we know when content will have high relevance. And because we are delivering this content early in a browsing session – rather than mixed in with the user’s activity – we know they are more likely to engage with it. We already have some very satisfied partners for Directory Tiles, and I am confident that Suggested Tiles will deliver even higher levels of engagement.
For partners who are interested in getting involved with the Suggested Tiles initiative, we have a site where you can learn more and register your interest: http://content.mozilla.org.
So what happens next? Suggested Tiles will be going to Beta soon and then live later in the summer. Initially, users will first see “Affiliate” Tiles advertisements for other Mozilla causes and Firefox products before Suggested Tiles from our content partners appear. Note that we’ll be rolling out the product in phases starting first with Firefox users in the US.
If you have any questions about how Suggested Tiles will work, need more information or want to explore a potential partnership with us, please visit content.mozilla.org.
This is still one of our early steps towards our goal of improving the state of digital advertising for the Web – delivering greater transparency for advertisers, better, more relevant content experiences and, above all, greater control for Firefox users.
I wrote a previous update about my work on multiplexing in curl. This is a follow-up to describe the status as of today.
I’ve successfully used the http2-upload.c code to upload 600 parallel streams to the test server and they were all sent off fine and the responses received were stored fine. MAX_CONCURRENT_STREAMS on the server was set to 100.
This is using curl git master as of right now (thus scheduled for inclusion in the pending curl 7.43.0 release). I’m not celebrating just yet, but it is looking pretty good. I’ll continue testing.
Commit b0143a2a3 was crucial for this, as I realized we didn’t store and use the read callback in the easy handle but in the connection struct which is completely wrong when many easy handles are using the same connection! I don’t recall the exact reason why I put the data in that struct (I went back and read the commit messages etc) but I think this setup is correct conceptually and code-wise, so if this leads to some side-effects I think we need to just fix it.
Next up: more testing, and then taking on the concept of server push to make libcurl able to support it. It will certainly be a subject for future blog posts…
At Mozilla we’ve been using The Mozilla Defense Platform (lovingly referred to as MozDef) for almost two years now and we are happy to release v1.9. If you are unfamiliar, MozDef is a Security Information and Event Management (SIEM) overlay for ElasticSearch.
MozDef aims to bring real-time incident response and investigation to the defensive tool kits of security operations groups in the same way that Metasploit, LAIR and Armitage have revolutionized the capabilities of attackers.
We use MozDef to ingest security events, alert us to security issues, investigate suspicious activities, handle security incidents and to visualize and categorize threat actors. The real-time capabilities allow our security personnel all over the world to work collaboratively even though we may not sit in the same room together and see changes as they occur. The integration plugins allow us to have the system automatically respond to attacks in a preplanned fashion to mitigate threats as they occur.
Notable changes include:
- Support for Google API logs (login/logout/suspicious activity for Google Drive/Docs)
- http://cymon.io api integration
- myo armband integration
Using the Myo armband in a TLS environment may require some tweaking to allow the browser to connect to the local Myo agent. Look for a how-to in the docs section soon.
Feel free to take it for a spin on the demo site. You can login by creating any test email/password combination you like. The demo site is rebuilt occasionally so don’t expect anything you put there to live for more than a couple days but feel free to test it out.
Mozilla hosts Kids Vision Bay Area Mentor Series
I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.The Review Queues
- Most nominations for full review are taking less than 10 weeks to review.
- 194 nominations in the queue awaiting review.
- Most updates are being reviewed within 6 weeks.
- 112 updates in the queue awaiting review.
- Most preliminary reviews are being reviewed within 9 weeks.
- 222 preliminary review submissions in the queue awaiting review.
If you’re an add-on developer and would like to see add-ons reviewed faster, please consider joining us. Add-on reviewers get invited to Mozilla events and earn cool gear with their work. Visit our wiki page for more information.Firefox 38 Compatibility
The Firefox 38 compatibility blog post is up. The automatic AMO validation was already run. There’s a second blog post covering the upcoming 38.0.5 release and in-content preferences, which were an oversight in the first post.Firefox 39 Compatibility
The Firefox 39 compatibility blog post is up. I don’t know when the compatibility validation will be run yet.
As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition (formerly known as Aurora) to make sure that they continue to work correctly. End users can install the Add-on Compatibility Reporter to identify and report any add-ons that aren’t working anymore.Extension Signing
We announced that we will require extensions to be signed in order for them to continue to work in release and beta versions of Firefox. A followup post was published recently, addressing some of the reasons behind this initiative.
A couple notable things are happening related to signing:
- Signing will be enabled for AMO-listed add-ons. This means that new versions will be automatically signed, and the latest versions of all listed add-ons will also be signed. Expect this to happen within a week or so (developers will be emailed when this happens). Signing for unlisted (non-AMO) add-ons is still not enabled.
- The signature verification code is now active on Developer Edition, in case you want to try it out with unsigned extensions. The preference is set to warn about unsigned extensions, but still accept and install them. You can use Developer Edition to test your extensions after we let you know they’ve been signed.
- A new Developer Agreement will be published on AMO. This is a significant update over the current years-old agreement, covering signing, listed and unlisted add-ons, themes, and other developments that have happened since. Developers will be notified when the new agreement is up.
Electrolysis, also known as e10s, is the next major compatibility change coming to Firefox. In a nutshell, Firefox will run on multiple processes now, running each content tab in a different one. This should improve responsiveness and overall stability, but it also means many add-ons will need to be updated to support this.
We will be talking more about these changes in this blog in the future. For now we recommend you start looking at the available documentation.
The LogView add-on for Fennec now lets you copy the logcat to clipboard or post the logcat to pastebin.mozilla.org. Simply go to the about:logs page from Menu → Tools → Logs and tap on “Copy” or “Pastebin”. This feature is very useful if you encounter a bug and need the logs, but you are not next to a computer or don't have the Android SDK installed.
Last modified: 2015/05/20 15:49
Появилось обновление Mozilla Thunderbird для Linux
Ни для кого не секрет, что приставка Mozilla в имени продукта сейчас вовсе не говорит о причастности к релизу разработчика известного веб-браузера, а лишь напоминает об истоках возникновения приложения. Компания уже довольно давно ...
Duration: 10 minutes This is a weekly status meeting, every Wednesday, that helps coordinate the shipping of our products (across 4 release channels) in order...
Watch mconley livehack on Firefox Desktop bugs!
Rust 1.0, the programming language behind Mozilla's new Web engine Servo, is ...
But what separates the open-source and openly developed Rust 1.0 is that Mozilla chose and backed it for building the company's crazy-fast new Web browsing engine, Servo. Here, from a working developer's point of view, I'll explain the characteristics ...
Last week I wrote some notes about re-triggering jobs to find a root cause. This week I decided to look at the orange factor email of the top 10 bugs and see how I could help. Looking at each of the 10 bugs, I had 3 worth investigating and 7 I ignored.
- Bug 1163911 – test_viewport_resize.html – new test which was added 15 revisions back from the first instance in the bug. The sheriffs had already worked to get this test disabled prior to my results coming in!
- Bug 1081925 – browser_popup_blocker.js – previous test in the directory was modified to work in e10s 4 revisions back from the first instance reported in the bug, causing this to fail
- Bug 1118277 – browser_popup_blocker.js (different symptom, same test pattern and root cause as bug 1081925)
- Bug 1073442 – Intermittent command timed out; might not be code related and >30 days of history.
- Bug 1096302 – test_collapse.html | Test timed out. >30 days of history.
- Bug 1151786 – testOfflinePage. >30 days of history. (and a patch exists).
- Bug 1145199 – browser_referrer_open_link_in_private.js. >30 days of history.
- Bug 1073761 – test_value_storage.html. >30 days of history.
- Bug 1161537 – test_dev_mode_activity.html. resolved (a result from the previous bisection experiment).
- Bug 1153454 – browser_tabfocus.js. >30 days of history.
Looking at the bugs of interest, I jumped right in in retriggering. This time around I did 20 retriggers for the original changeset, then went back to 30 revisions (every 5th) doing the same thing. Effectively this was doing 20 retriggers for the 0, 5th, 10th, 15th, 20th, 25th, and 30th revisions in the history list (140 retriggers).
I ran into issues doing this, specifically on Bug 1073761. The reason why is that for about 7 revisions in history the windows 8 builds failed! Luckily the builds finished enough to get a binary+tests package so we could run tests, but mozci didn’t understand that the build was available. That required some manual retriggering. Actually a few cases on both retriggers were actual build failures which resulted in having to manually pick a different revision to retrigger on. This was fairly easy to then run my tool again and fill in the 4 missing revisions using slightly different mozci parameters.
This was a bit frustrating as there was a lot of manual digging and retriggering due to build failures. Luckily 2 of the top 10 bugs are the same root cause and we figured it out. Including irc chatter and this blog post, I have roughly 3 hours invested into this experiment.
Software-update: Mozilla Thunderbird 31.7.0
Mozilla Thunderbird logo (90 pix) De Mozilla Foundation heeft versie 31.7.0 van Thunderbird uitgebracht. Mozilla Thunderbird is een opensourceclient voor e-mail en nieuwsgroepen, met features als ondersteuning voor verschillende mail- en newsaccounts, ...
As all the release of this special 38.0.5 cycle, we took mostly patches for the Pocket integration, some reader view improvements and stability fixes.
The next version should be 38.0.5 rc1 (go to build Thursday, go live Friday).
- 21 changesets
- 38 files changed
- 393 insertions
- 132 deletions
ExtensionOccurrences js6 jsm5 cpp5 properties4 ini3 html3 txt2 inc2 h2 xul1 sh1 nsi1 mk1 dtd1 css1
ModuleOccurrences browser21 dom7 testing3 widget2 mobile2 toolkit1 editor1 config1
List of changesets:Gijs KruitboschBug 1160775 - fix reader mode detection to force 1 flush so we don't think the entire page is invisible, r=margaret a=lmandel - 93b96d846d47 Margaret LeibovicBug 1152412 - Handle errors downloading and parsing documents for reader view. r=bnicholson a=lmandel - 964442785c00 Gijs KruitboschBug 1134501 - add way for UITour'd page to force-show the reader mode button, r=margaret a=lmandel - 5741ccc7bb74 Kartikaya GuptaBug 1163640 - Fix the test for Bug 417418 to not leave the widget in a drag session. r=ehsan, a=test-only - df02fefaa438 Mike ShalBug 1122746 - Ignore *.pyc in zip instead of removing them. r=ted, a=test-only - 06cc113b476f James GrahamBug 1135515 - Fix relevant mutations tests to avoid intermittent issues. a=test-only - 82e59df1da4e Martin ThomsonBug 1158296 - Allow ECDSA key export in WebCrypto. r=rbarnes, a=sledru - 1a8cd9f5bdad Karl TomlinsonBug 1159456 - Finish and exit from Flush() even if MFTManager rejects sample. r=cpearce, a=sledru - 825e8ac4ab29 Jan-Ivar BruaroeyBug 1150539 - getUserMedia: default to aPrefs.mFPS, not aPrefs.mMinFPS. r=jesup, a=lizzard - cfa10b9f0f9d Jan-Ivar BruaroeyBug 1162412 - Part 1: Don't treat plain facingMode constraint as required. r=jesup, a=lmandel - c14434ed2197 Jan-Ivar BruaroeyBug 1162412 - Part 2: Order devices by shortest fitness distance. r=jesup, a=lmandel - 9c1d3c0257ec Jan-Ivar BruaroeyBug 1162412 - Part 3: Treat plain values as exact in advanced. r=jesup, a=lmandel - e3045256cb27 Jeff MuizelaarBug 1157784 - Avoid compositing at the same time as WM_SETTEXT. r=bas, f=jimm, a=sledru - ecbce7532a0a Jared WeinBug 1162713 - Implement "Save Link to Pocket" context menu item. r+a=dolske, l10n=dolske - e13a7a312aa5 Gijs KruitboschBug 1164940 - Lazily create iframe. r=jaws, a=sledru - 24524667128b Gijs KruitboschBug 1164426 - Build reader mode blocklist. r=margaret, a=sledru - 6ec85b777880 Robert StrongBug 1165135 - Distribution directory not removed on pave over install. r=spohl, a=sledru - 4bfd19d00ed4 Jared WeinBug 1163917 - Remove the widget from its area if the conditionalDestroy promise is resolved truthy. r=gijs, a=sledru - f9328a6ea6bd Nate WeinerBug 1165416 - Update Pocket code to latest version (May 15th code drop). r=dolske, r=jaws, a=sledru - e6f89a184268 Jared WeinBug 1160407 - Redirect links within the Pocket panel to open in non-private windows when temporary Private Browsing is used. r=dolske, a=sledru - f5828f333524 Gijs KruitboschBug 1147487 - Don't try to reader-ize non-HTML documents. r=margaret, r=jaws, a=lmandel - f44dff585598
Keeping Firefox zippy involves running performance tests on each push to make sure we’re not making Firefox slower.
How does that even work? This used to be a mystery. NO LONGER. jmaher lets you peek behind the curtain here in the first episode of Lost in Data!
Yesterday, Audrey announced that we’re going create a podcast version of The Recompiler!
Some of you may have listened to In Beta, which I co-hosted last year. Doing that podcast was great fun and I’m so looking forward to hosting this supplement to The Recompiler. The podcast will enhance the written version of the magazine with tech news, criticism & commentary plus interviews with our authors.
If you’re craving awesome, insightful conversation on technical topics from fresh, less-heard-from voices, then The Recompiler podcast is for you!
Get involved and support The Recompiler today by purchasing a subscription and look for the first written issue and episode this summer!
I started contributing to Mozilla nearly 11 years ago, in 2004, and joined as a full-time employee over 8 years ago. Suffice it to say, Mozilla has been a big part of my life in a lot of ways. I’ve dedicated essentially my entire career so far to Mozilla, and it introduced me to my wife, just to name a couple.
Mozilla’s in a great place now – still a tough challenge ahead, but plenty of great people willing and able to tackle it. Firefox has new leadership, the team is being re-organized and groups merged together in what I think are the right ways, and I’m optimistic about their prospects. But it’s time for me to move on and find The Next Thing – that I have no idea what it is now is both exciting and a little bit terrifying, but I feel good about it.
It will probably take me a while to figure out what exactly a post-Mozilla Gavin-life looks like, given the various ways Mozilla’s been injected into my life. I won’t disappear entirely, certainly, and I know the many relationships I’ve built through Mozilla will continue to be a huge part of my life.
I’m looking forward to what’s next!
Mozilla veröffentlicht Thunderbird 31.7
Während Thunderbird 38 noch ein paar Tage auf sich warten lässt, hat Mozilla Thunderbird 31.7 veröffentlicht und behebt damit mehrere Sicherheitslücken. Download Mozilla Thunderbird 31.7 für Windows, OS X und Linux. Thunderbird 38 ist nicht zeitgleich ...
Join Joel Maher in a livehacking session where he is triaging and investigating Firefox performance alerts.
Mozilla Advocacy — Our 2015 Plan for Protecting and Advancing the Open Web
Advocacy is a relatively new area of focus for Mozilla. Our increased emphasis on advocacy is born out of the recognition that, like code, public policy has an impact on the shape and health of the open web — and that a vital force protecting the web will be the millions of people who consider themselves to be citizens of the web.
Over the next few weeks, the Mozilla Advocacy team — including Andrea Wood, Director of Digital Advocacy and Fundraising; Melissa Romaine, Advocacy Manager; Chris Riley, Head of Public Policy; Stacy Martin, Senior Manager of Privacy and Engagement; Jochai Ben-Avie, Internet Policy Manager; and, Alina Hua, Senior Data Privacy Manager — will lay out our latest thinking about how we’re developing public policy and creating advocacy initiatives.
Our goal with Mozilla Advocacy is to advance the Mozilla mission by empowering people to create measurable changes in public policy to protect the Internet as a global public resource, open and accessible to all. Our three strategies to achieve this goal are:
Leadership Development — Grow a global cadre of leaders — activists, technologists, policy experts — who advance the free and open web.
Community — Assist, grow, and enable the wider policy & advocacy community.
Grassroots Advocacy — Run issue-based campaigns to grow mainstream engagement with Mozilla and open web issues.
Each of these strategies ties directly to the goal of empowering people. Yet, as we execute there are still open questions that need input and more thought from the community. For instance, how can we create better scale and participation, recognizing that real impact happens when the community is empowered to take action on policy and advocacy initiatives. A key to this is making our own policy positions and advocacy efforts easier for people to understand and engage with.
We need you to play an active role. Because the web is growing in markets where we are not experts, the Mozilla community will play a central role in scaling efforts to protect the open web throughout the world. We invite you to help shape our thinking by reading the 2015 Policy & Advocacy Plan and offering input through this thread in the Mozilla Advocacy Community.
–Dave Steer, Director of Advocacy, Mozilla