Mozilla Nederland LogoDe Nederlandse

Abonneren op feed Mozilla planet
Planet Mozilla -
Bijgewerkt: 2 weken 2 dagen geleden

The Mozilla Blog: How Do You Feel About Facebook? Take the Survey.

di, 03/04/2018 - 19:38

There’s been a lot in the news lately about how 50 million Facebook users had their information used by Cambridge Analytica, a private company, without their knowledge.


The conversation since — both online and off — has been all over the board. Some people were not at all surprised by the story, saying this has been common practice for a while. Others were shocked, worried their personal information could be used for nefarious purposes. And still others seem not to really notice the news at all.

Which left us wondering, how do most people feel about this news and about Facebook in general? We put together a fun, quick survey to try and find out how people are feeling right now. It’ll take about three minutes of your day.


We’ll use this survey to understand how we can better support and advocate for you and your personal information online. We promise not to use any of your personally identifying information on targeted ads. We promise not to sell this data to any third parties. And we promise to share the results of this survey back with you in a transparent and open way.

The post How Do You Feel About Facebook? Take the Survey. appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

Mozilla GFX: WebRender newsletter #17

di, 03/04/2018 - 18:32

Bonsoir ! WebRender’s seventeenth newsletter is here. The biggest highlight of this couple of weeks is without hesitation the landing of Jeff’s blob image invalidation work. Months of hard work went into what grew into a reimplementation of a decent portion of FrameLayerBuilder for blob images and will improve SVG rendering performance quite a bit in WebRender as soon as it will be enabled by default. See the first item in the list of Gecko changes for more details.

Notable WebRender changes
  • Glenn fixed a shadow clipping bug.
  • fschutt made compiling the debug render shaders optional to improve startup time.
  • Josh updated the freetype dependency.
  • Botond implemented taking backface-visibility into account during hit-testing.
  • Kvark improved the frame capture tool.
  • Martin fixed a border clipping issue.
  • Simon updated serde.
  • Glenn unified the text-shadow and blur filter implementation.
  • Glenn implemented handling box shadow stretch modes per-axis to avoid allocating huge render tasks for very long/thin elements.
  • Kvark prevented incorrectly reusing frame ids from previous frames in render tasks.
  • Glenn made mipmap generation optional (it can be very slow and it is on the critical path so we are better off downscaling on the image decoder side).
  • Nical fixed a bug causing elements to disappear under certain conditions.
  • Martin added hit-testing support in wrench.
  • fschutt sped up allocating images in wrench.
  • Nical removed an old scrolling workaround in wrench made unnecessary by the transaction API.
  • Sotaro fixed the way TEXTURE_RECT sampling is handled in the shader (important for some video code paths).
  • Glenn removed the brush line shader and converted line decorations to use clip sources (fixes some edge cases and improves batching).
  • Glenn implemented rendering text shadows in screen space.
  • TyOverby and Kats updated the bincode dependency.
Notable Gecko changes
  • Jeff landed blob image invalidation.

    This gives us the ability to do proper invalidation and layerization for inline SVG with blob images. For example, the animation on can now run asynchronously. It also means that we further avoid some the performance problems that FrameLayerBuilder has (this site runs much better with blob invalidation, and this site as well for example).

  • Sotaro implemented presenting through direct composition in some cases.

  • Sotaro enabled skia-gl canvas on Mac.
  • Sotaro enabled D2D canvas on Windows.
  • Kats reduced the number of WebRenderScrollLayerData item created for transformed items (perf improvement) and fixed a followup bug.
  • Kats enabled more tests.
  • Sotaro fixed a rendering bug when ANGLE is disabled on Windows.
  • Andrew fixed an intermittent crash happening under memory pressure.
  • Martin fixed a hit-testing bug with fixed-position elements.
  • Jeff fixed a crash with zero-sized blob images.
  • Jeff fixed another crash.
  • Lee fixed a crash related to the memory management of fonts.
  • Kats disabled WebRender-side mipmap generation.
  • Kats disabled QR tests on beta since WebRender isn’t available there yet.
  • Kats ensured crash reports properly tell whether WebRender is enabled.
  • Nical improved the memory management of images.
  • Jeff avoided computing a scale for 3d-transformed elements. and fixed a followup bug.
  • Jeff fixed uninitialized app-units-per-dev-pixels scale factor.
Enabling WebRender in Firefox Nightly

In about:config, just set “gfx.webrender.all” to true and restart the browser. No need to toggle any other pref.

Note that WebRender can only be enabled in Firefox Nightly. We will make it possible to enable it on other release channels as soon as we consider it stable enough to reach a broader audience.

Reporting bugs

The best place to report bugs related to WebRender in Gecko is the Graphics :: WebRender component in bugzilla. It is possible to log in with a github account.

Categorieën: Mozilla-nl planet

Mozilla VR Blog: Firefox Reality: Bringing the Immersive Web to Mixed Reality Headsets

di, 03/04/2018 - 15:03
 Bringing the Immersive Web to Mixed Reality Headsets

Today we are proud to announce Firefox Reality, a new web browser designed from the ground up for stand-alone virtual and augmented reality headsets. We took our existing Firefox web technology and enhanced it with Servo, our experimental web engine. From Firefox, we get decades of web compatibility as well as the performance benefits of Firefox Quantum. From the Servo team (who recently joined the Mixed Reality team), we will gain the ability to experiment with entirely new designs and technologies for seeing and interacting with the immersive web. This is the first step in our long-term plan to deliver a totally new experience on an exciting new platform.

Here’s an early video of our web engine and test UI:

In the coming weeks, we will release regular updates on our work, including:

  • Details of the design process, from paper sketches to headset prototyping
  • Sneak peeks of Firefox Reality running on a variety of pre-release headsets
  • New capabilities for artists, designers, and developers of immersive experiences
  • Integration of Servo, along with experimental extensions to the WebGL graphics APIs
  • An experimental computer-vision pipeline using WebAssembly
  • Device, gesture, and voice-interaction features

And much more!

Firefox Reality is designed and engineered specifically for the next generation of standalone VR and AR headsets, but during initial development our source code will also run in Developer Mode on Daydream and Gear VR devices. As of today, we’re releasing source code and developer builds for a variety of platforms. Updates will continue to be published here on the blog, as well as our Twitter account. If you are interested in learning more about or contributing to Firefox Reality, then reach out.

Categorieën: Mozilla-nl planet

The Mozilla Blog: Mozilla Brings Firefox to Augmented and Virtual Reality

di, 03/04/2018 - 15:00

Today, we primarily access the Internet through our phones, tablets and computers. But how will the world access the web in five years, or in ten years, and how will the web itself grow and change?

We believe that the future of the web will be heavily intertwined with virtual and augmented reality, and that future will live through browsers. That’s why we’re building Firefox Reality, a new kind of web browser that has been designed from the ground up to work on stand-alone virtual and augmented reality (or mixed reality) headsets.

(If you love mixed reality – or even if you are just a curious bystander – you can read our announcement post here.)

So why are we creating a browser for mixed reality?

Here at Mozilla, it’s our mission to ensure that the Internet is an open and accessible resource that puts people first. Currently, the world can browse the open web using our fast and privacy-focused Firefox browser, but continuing that mission in a rapidly changing world means constantly investing our time and resources into new and emerging technologies – and realities.

Mozilla has always been on the frontlines of virtual and augmented reality (see our work with WebVR, WebAR and A-Frame), and this is a mixed reality browser that is specifically built to tackle the new opportunities and challenges of browsing the immersive web.

Why is this important?

This is the first cross-platform browser for mixed reality.

Other solutions for browsing and accessing the web on stand-alone headsets exist, but they are closed, and platform specific. Firefox Reality will be independent and will work on a wide variety of devices and platforms.

This is the only open source browser for mixed reality.

Just like our Firefox browser for the desktop, all of Firefox Reality is open source. Not only does this make it easier for manufacturers to add the browser to their platform, but it provides a level of transparency that our users have come to know and expect from Mozilla.

This is a browser that is built by a company that respects your privacy.

We take privacy very seriously at Mozilla. Mixed reality is still new. We don’t yet have all the answers for what privacy looks like in this new medium, but we are committed to finding the solution. We will continue to build on the proven permissions model of the web platform, which provides even more protection than native apps provide. The Mozilla values will guide us as we create Firefox Reality, just as they do with every product we create.

This is a browser that will be fast.

We know fast. We have decades of experience with web compatibility and last year we released Firefox Quantum – a browser that was rebuilt for speed. All of that knowledge, technology, and experience will allow us create a best-in-class browser for mixed reality headsets.

This is a browser that is built for the future.

Mixed reality is the wild west. How do you type? How do you express emotion? How do you view the billions of existing 2D web pages as well as new 3D content? How do you communicate? Who maps the world and who controls what you see? Can we build on our work with voice recognition and connected devices to create a better browsing experience? We love tackling these questions. Everything is new again, and we are constantly building and experimenting to find the right answers.

Browsers are the future of mixed reality.

The future of mixed reality is about delivering experiences, not about building applications.  There shouldn’t be friction moving from one experience to another. Firefox was the first browser to implement WebVR – an open standard for sharing and enjoying virtual reality content through a web URL. This lays the groundwork for creating and delivering immersive experiences using a method that is as simple as opening a web page.

If you’d like to learn more, or view a demo of Firefox Reality running on the HTC Vive Focus, check out our Mixed Reality Blog. You can also follow us on Twitter, where we will provide updates on when Firefox Reality will be available on headsets. Until then, stay tuned. Exciting things are coming.


The post Mozilla Brings Firefox to Augmented and Virtual Reality appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

Air Mozilla: Mozilla Weekly Project Meeting, 02 Apr 2018

ma, 02/04/2018 - 20:00

Mozilla Weekly Project Meeting The Monday Project Meeting

Categorieën: Mozilla-nl planet

Air Mozilla: Mozilla Weekly Project Meeting, 02 Apr 2018

ma, 02/04/2018 - 20:00

Mozilla Weekly Project Meeting The Monday Project Meeting

Categorieën: Mozilla-nl planet

Mozilla Addons Blog: Extensions in Firefox 60

ma, 02/04/2018 - 16:59

Many people read this blog because they’ve written extensions for Firefox in the past. Others, though, know some HTML, CSS, and JavaScript and have been thinking about writing their first extension. Either way, now is the perfect time to jump into the WebExtensions ecosystem.

That’s because we’re having a contest! Develop an extension for Firefox and enter it into the Firefox Quantum Extensions Challenge by April 15, 2018. Your extension could win you a brand-new Apple iPad Pro or a $250 gift card to Amazon.

And if you want to make your extension even better, consider using some of the new WebExtensions API discussed below. These new and improved API are available in Firefox 60, recently released to the Beta Channel.

A Profusion of Theme Properties

Since “Best Dynamic Theme” is one of the award categories for the Firefox Quantum Extension Challenge, let’s start with improvements to Themes. Release 60 adds a pile of new items to the list of elements that can be themed, doubling the number of individual components.  These include:

  • tab_line – Line color of the selected tab.
  • tab_selected – Background color of the selected tab.
  • popup – The background color of popups (such as the arrow panels).
  • popup_border – The border color of popups.
  • popup_text – The text color of popups.
  • tab_loading – The color of the tab loading indicator and the tab loading burst.
  • icons – The color of toolbar icons.
  • icons_attention – The color of toolbar icons in attention state such as the starred bookmark icon or finished download icon.
  • frame_inactive – The same as “accentcolor”, but only applied to inactive windows, provided for Chrome compatibility.
  • button_background_active – The color of the background of pressed toolbar buttons.
  • button_background_hover – The color of the background of toolbar buttons on hover.
  • toolbar_field_separator – The color of separators inside the URL bar (also available in Firefox 59; note that in Firefox 58 it was implemented under toolbar_vertical_separator)
  • toolbar_vertical_separator – The color of the separator next to the application menu icon (also available in Firefox 59; note that in Firefox 58 it corresponds to the color of separators inside the URL bar).

Also new for Firefox 60, the headerURL property is no longer mandatory, removing a somewhat arbitrary condition that made themes a bit clunky in the past.

Remember, the contest awards a prize for the best Dynamic Theme, so use the theme API to control and change the various UI elements in creative ways. Want an awesome tutorial that talks about Dynamic Themes? Check out the video below.

More Tab Features

Consistent with each release since Quantum 57, tabs remain a focus of WebExtension growth and improvement. Several bigger features will land in release 61 (expert Bugzilla miners are likely aware of them already), but Firefox 60 still offers a number of important items:

Improving Debugging and Development

Several new additions landed that make the debugging and development of extensions easier, including:

Proxy Improvements

The proxy API is quickly maturing, and Firefox 60 adds more functionality by adding the asynchronous proxy.onRequest API.  This API is ideal for extensions looking to deal with proxy requests in a background script.  Details are still being documented on MDN at the time of this writing but should be available soon.

Network Extensions Get DNS

Extensions now have access to Firefox’s DNS service to resolve hostnames. The new browser.dns() API takes a hostname string (with optional parameters) and resolves it to a DNS record for that hostname. To use this new API, your extension must declare the “dns” permission.

Dynamic Keyboard Shortcuts

Two new API were added to the Commands namespace that allow extensions to change their keyboard shortcuts at runtime. The first, commands.update, allows an extension to change the shortcut key and/or description associated with a command, while the second, commands.reset, reverts a command back to the keyboard shortcut and description originally specified in the manifest file.

Keeping Users Informed

In keeping with our mission to ensure that users are always informed and in control of what extensions are doing, a few new messages have been added to the browser interface:

Enhancing All the Action

The browserAction, pageAction, and sidebarAction are three of the most commonly used WebExtension features, and all three get some improvement in Firefox 60:

Other Improvements

The items mentioned above highlight some of the bigger and/or more visible changes that appear in Firefox 60. As always, though, many other minor or less visible improvements to WebExtensions also landed, including:

Thank You

A total of 63 features or improvements were landed for WebExtensions as part of Firefox 60 Beta. Thank you to our many contributors for this release, especially our community volunteers including: Tim Nguyen, Oriol Brufau, Richard Marti, Prathiksha Guruprasad, Vinicius Costa e Silva, Vivek Dhingra, Zhengyi Lian, Connor Masini, DW-dev, Bogdan Podzerca, and Dylan Stokes. As always, we sincerely appreciate you helping ensure that individuals have the ability to shape the Internet and their own experiences on it. If you are interested in contributing to the WebExtensions ecosystem, please take a look at our wiki.

This post is going up a bit later than normal and there are already several additions and changes to the WebExtensions API in progress for Firefox 61, so continue watching this space for more information. In the meantime, please continue to send us your feedback.

An earlier version of this article incorrectly stated that the theme properties popup_highlight and popup_highlight_text were available in Firefox 60, and that popup and popup_text could be used to style the URL and search bar autocomplete panels. All four of those things will actually appear in Firefox 61 (which is available in the Firefox Nightly channel right now).

The post Extensions in Firefox 60 appeared first on Mozilla Add-ons Blog.

Categorieën: Mozilla-nl planet

The Mozilla Blog: Announcing $280,000 for Creative Gigabit Projects Across the U.S.

ma, 02/04/2018 - 15:03
Mozilla is supporting 14 tech-for-good initiatives in Oregon, Texas, Tennessee, and beyond


Today, Mozilla is awarding $280,000 to community technologists who are leveraging gigabit internet for good.

We’re providing grants to 14 projects in five American cities: Lafayette, LA; Eugene, OR; Chattanooga, TN; Austin, TX; and Kansas City. Grants range from $10,000 to $30,000.

The projects are diverse: they include a virtual reality experience that shows first-hand the drastic effects of climate change; an interactive Python curriculum for students in low-income school districts; and a program that empowers high school students as environmental watchdogs with the help of advanced mapping software.

What all these projects have in common: they tap into high-speed fiber networks to improve local education and workforce opportunities.

“Each of these promising projects leverages lightning-fast internet to make a positive impact in their communities,” says Lindsey Frost Dodson, who directs Mozilla’s gigabit initiative. “This work — being led by school districts, nonprofits, and for-profits — can create more connected, open, and innovative U.S. cities.”

These 14 grants are part of the Mozilla Gigabit Community Fund, a partnership between Mozilla, the National Science Foundation, and U.S. Ignite. The Fund has granted more than $1.2 million to over 90 projects during its six-year history. Learn more about the Fund in the short film at the bottom of this post.

The Projects


Lafayette Gigabot Coding Initiative | Lafayette, LA This project trains elementary and middle school teachers in connected robotics and cloud-based programming. Teachers then integrate these topics into their curriculum. Led by Lafayette Parish Public Schools


Virtual Reality Ecoliteracy Curriculum | Lafayette, LA This project uses virtual reality to show students the real-world impacts of climate change and coastal erosion. It spotlights the plight of “climate refugees” — a displaced Native American tribe in coastal Louisiana. Led by University of Louisiana at Lafayette


A Community In Motion | Lafayette, LA This project trains high school students in livestream, broadcast and 4K technology, positioning them as community journalists and storytellers. Led by Youth Literacy Foundation of Acadiana


New Hope STEM Club Gigabot Project | Lafayette, LA For this project, middle school students will receive cloud-based programming lessons from members of the Black Male Leadership project at University of Louisiana. Led by New Hope Community Development of Acadiana


Giga-Scapes | Eugene, OR Using internet-connected board games, this project allows people hundreds of miles apart to play together. It also features STEM workshops for local students, taught by game-industry experts. Led by Tech Tone Graphix


Gigabit Residencies | Eugene, OR This project provides virtual reality and video game development training to teachers at low-income schools. Led by Lane Arts Council


Real Time Wetland Restoration Mapping and Analysis | Eugene, OR This project empowers at-risk students as environmental watchdogs — teens will use Geographic Information Systems (GIS) to track land restoration initiatives. Led by Bethel Education Foundation


Educational Equity VR | Eugene, OR This projects uses virtual reality training to help eliminate teachers’ unconscious biases — and, as a result, mitigate disproportionate suspensions and expulsions for minority students. Led by Treadwell Ventures LLC


Opening Access to Virtual Worlds | Eugene, OR This project provides training in the fields of virtual reality and video game development for community members. Led by Eugene Public Library


Cross-Community Kvasir-VR | Lafayette, LA and Chattanooga, TN This project allows middle and high school students to take interactive virtual reality field trips to solar energy plants. Led by University of Louisiana at Lafayette


Networking the Classroom of the Future | Chattanooga, TN and Austin, TX This project uses 4K streaming to bring content from museums and research facilities into classrooms. Led by The Enterprise Center


Path to Python | Austin, TX and Eugene, OR This project provides an interactive Python curriculum to students in low-income schools. Led by Kiwi Compute, LLC


LOLA-Enabled Puppet Theaters | Chattanooga, TN and Kansas City This project uses internet-connected robotic puppets, 3D printing, and other emerging technologies to teach history in local classrooms. LOLA stands for “low latency audio visual streaming.” Led by Red Bank High School


LOLA in Lafayette Pilot Program | Lafayette, LA and Chattanooga, TN This project uses low latency audio visual streaming to create a cross-city learning day on Make Music Day in June 2018. The two cities will share their musical traditions. Led by Acadiana Center for the Arts

A photo from the Mozilla-funded Gigabots project in Kansas City

The post Announcing $280,000 for Creative Gigabit Projects Across the U.S. appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

Justin Dolske: Foxkeh Dance 2.0

ma, 02/04/2018 - 07:49

It’s time for some new Foxkeh dance!


10 years ago, when Mozilla was just 10, Alex Polvi made the original

I resurrected it a few years ago, after the original site was lost to domain squatters.

Well, since Mozilla is currently celebrating its 20th anniversary, it felt right to release an update… Foxkeh Dance 2.0!

Now with more and larger GIFs! Fresher but still annoying background music! And, uhh, a bigger version number! That’s basically it. See you in another 10 years!

Categorieën: Mozilla-nl planet

The Servo Blog: This Week In Servo 110

ma, 02/04/2018 - 02:30

In the last week, we merged 66 PRs in the Servo organization’s repositories.

Planning and Status

Our roadmap is available online, including the overall plans for 2018.

This week’s status updates are here.

Notable Additions
  • mrobinson made certain kinds of borders clippable by WebRender.
  • ysimonson ensured that JSON parsing exceptions from the fetch API are propagated.
  • nupurbaghel added support for typed array bodies in XMLHttpRequest.
  • talklittle implemented support for the streaming TextDecoder API.
  • aeweston98 improved the memory reporting for DOM objects that are not part of the DOM tree.
  • modal17 added memory reporting for the HTTP memory cache.
  • csmoe tracked measurements of how long it takes for layout queries to be serviced.
  • marmistrz made handles to GC values safer by including lifetimes in their types.
  • emilio added support for percentage values in column-gap CSS properties.
New Contributors

Interested in helping build a web browser? Take a look at our curated list of issues that are good for new contributors!

Categorieën: Mozilla-nl planet

The Rust Programming Language Blog: Increasing Rust’s Reach 2018

ma, 02/04/2018 - 02:00

The Rust team is happy to announce that we’re running our Increasing Rust’s Reach program again this year. Increasing Rust’s Reach is one of several programs run by the project to grow Rust’s community of project collaborators and leaders.

We’re looking for people inside and outside Rust’s current community from groups and backgrounds that are underrepresented in the Rust world and the technology world more generally. We want to partner with you to make Rust a more inclusive, approachable, and impactful project, while supporting your success on personal goals.

This program matches Rust team members from all parts of the project with individuals who are underrepresented in Rust’s community and the tech industry for a partnership of three (3) months, from mid-May to mid-August. Each partnership agrees to a commitment of 3-5 hours per week collaborating on a Rust project.

By way of thanks for participating in the program, we offer a fully paid conference ticket, travel, and accomodations for every participant to a Rust Conference of their choice:

Learn more about the upcoming 2018 Rust Conferences here.

Last year we had 12 participants working on several projects, from contributing to foundational ecosystem libraries like Diesel, to discovery work on a new Rust website, to helping find developer experience and usability holes in the ecosystem. You can read more about previous participants’ experiences on the brand new Increasing Rust’s Reach website!

Many of the projects we have for this year build on the work that was accomplished last year. However, the primary focus of this year’s project is the 2018 edition release; in particular, the domain working groups that we kicked off with our 2018 Roadmap.

We believe the 2018 edition is a great opportunity, not only to simply get new people involved in the Rust project, but to also demonstrate the huge impact that even newcomers to the project can make. Rust is committed to being a friendly and inclusive project that welcomes new contributors from all sorts of backgrounds—we actively want to be a project that you want to work on, and we’re excited to learn about how we can do that better.

Applications for the program open today, and will run until April 20th. We will announce the recipients on April 30th, and the program will run from May 15th to August 17th. For more details on the timeline, check out the website.

We’re super excited to get your applications! If you have any questions, feel free to reach out to the program committee at

Categorieën: Mozilla-nl planet

Mozilla Reps Community: Reps of the Month – February 2018

zo, 01/04/2018 - 16:36

Please join us in congratulating Ziggy Maes and Anthony Maton, our Reps of the Month for February 2018!


Ziggy is a long time Mozillian that is involved in organizing our presence at FOSDEM or managing the volunteers at the Mozilla Festival. Together with Anthony he started working on both finding speakers for the DevRoom but also to be sure we have a good presence at the booth too. This work was spread around 3 months so we are definitely grateful for their effort.


Anthony is pretty fresh in the Reps role but he has been a Mozillian for a long time now. Part of he Belgium community, he engages with the Francophone community at the same. His latest big effort was organizing Mozilla’s activities at FOSDEM together with Ziggy, both the call for speakers for the DevRoom and our presence at the booth during those two days.


Thank you Ziggy and Anthony, keep rocking the open Web!

Join us in congratulating them on Discourse!

Categorieën: Mozilla-nl planet

Gervase Markham: Happy Birthday, Mozilla

za, 31/03/2018 - 23:17

Mozilla is 20 today. Most of what can be said about that has been ably said by others, some of whom have been involved for even longer than the 18 years I managed. Asa and I started at roughly the same time, but at least Mitchell, Myk and dmose have been around longer and are still involved. (Apologies if I’ve forgotten someone.)

As most of you know, I probably won’t be around to see much more of it, but (this will seem trite if it’s not to seem big-headed!) Mozilla is much more than one or even a few people. There will always be a Mozilla as long as there is an Internet and people who care about people on it. In that vein, let me also say that I’m absolutely delighted with the final outcome of the worldview project. The four items in the addendum to the Manifesto are admirable goals to aim for, and ones I endorse wholeheartedly.

Categorieën: Mozilla-nl planet

The Mozilla Blog: Mozilla Turns Twenty

za, 31/03/2018 - 18:29

It’s the morning of March 31, 1998, and the Netscape campus is chock-full of engineers, hours earlier than on a normal day. It’s a Tuesday and it’s known universally in the Netscape browser world as “three thirty-one” and written as 3/31. It’s the day the Mozilla code is open-sourced to the world, and the day the Mozilla Project is formally launched.

Three thirty-one was the result of a massive amount of work in two short months. The intent to make open source the code for “Netscape Navigator” had been announced on January 22. On that date the code was not ready, we didn’t know which free software / open source license we would use, and we didn’t have a structure for running an open source project. That was pure Netscape style.

(For those who came online anytime this century, Netscape Navigator was the product that gave consumers access to the internet for the very first time starting in 1994. Scientists used a command line interface, early adopters used the first browser called Mosaic, and everyone else used Netscape Navigator to access what we called “the World Wide Web.”)

By 3/31 the code had been cleansed of proprietary code owned by others that Netscape couldn’t open source, a new open source license (the Mozilla Public License) had been created and approved by the Open Source Initiative (, and a small band had created “” as the governance body for the new open source project. Here’s the earliest image of the site I can find, from December of 1998:

Mozilla was not originally intended to create consumer products. It was expected to be a technology development organization that would make technology available to Netscape and others who would build consumer products. Over time we found people liked the development version Mozilla was shipping and we began moving towards producing products rather than technology.

We’ve come a long way since then!

In my wildest dreams I could not have imagined how many people would be drawn to the Mozilla mission and would choose to affiliate with Mozilla in some way. This includes employees, volunteer contributors, “friends of Mozilla” and an ever broader range of people who recognize what Mozilla stands for and want more of this in the world. For me, this is the richest legacy.

There is plenty to do going forward to build a healthier internet that has better human experiences. There’s no detailed map — we’ll build that together. We’ll go forwards, sideways, and in circles. It’s an adventure, and probably not for the faint-hearted. But for those who love the adventure, thrive on change, and want to be remembered for building decent values into great products and programs – for us, there’s no better place to be.

The post Mozilla Turns Twenty appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

Asa Dotzler: is 20 years old

za, 31/03/2018 - 09:33

[This is a copy of from launch day]

our mission

Netscape Communications made two important announcements on January 23rd, 1998:

  • First, that the Netscape Communicator product would be available free of charge;
  • Second, that the source code for Communicator would also be free.

On March 31st, the first developer release of the source code to Communicator was made available.

But what now? For the product to grow and mature and continue to be useful and innovative, the various changes made by disparate developers across the web must be collated, organized, and brought together as a cohesive whole.

A group exists within Netscape that is chartered to act as a clearing-house for the newly-available Netscape source. That group is We will provide a central point of contact and community for those interested in using or improving the source code:

  • We will collect changes, help authors synchronize their work, and periodically make new source releases which incorporate the best work of the net as a whole.
  • We will operate discussion forums (mailing lists, newsgroups, or whatever seems most appropriate.)
  • We will coordinate bug lists, keep track of and publicize works in progress, and generally attempt to provide “roadmaps” to the code, and to projects based on the code.
  • And we will, above all, be flexible and responsive. We realize that if we are not perceived as providing a useful service, we will become irrelevant, and someone else will take our place.
  • We are not the primary coders. Most of the code that goes into the distribution will be written elsewhere, both within the Netscape Client Engineering group, and, increasingly, out there on the net, at other companies and other development organizations.
  • We are code integrators. And, through our forums, we will try to help people reach consensus, and thereby provide direction and coordination for future improvements.

It can be observed that all successful open-source software projects follow this model of distributed development and centralized integration. One of the fears that open-source software software neophytes often express is that open availability of the source will lead to balkanization, that there will eventually be thousands of different descendants of the original software, and confusion and chaos will result. But, in reality that doesn’t happen; organizations like tend to appear. Eric Raymond tries to explain why in his excellent paper, The Cathedral and the Bazaar. We hope to operate in the “Bazaar” style, and be to the public Netscape source code as Linus Torvalds is to Linux.


“Mozilla” was the original code name for the product that came to be known as Netscape Navigator, and later, Netscape Communicator.

Later, it came to be the name of Netscape Communications Corporation’s dinosaur-like mascot.

Now, we intend to use the name Mozilla as the generic term referring to web browsers derived from the source code of Netscape Navigator.

Netscape Communications Corporation holds trademarks on the names Netscape, Navigator, and Communicator; it has not yet been decided what, if any, restrictions Netscape will place on the use of those names. However, a generic term for browsers is still needed, and “Mozilla” is as good a name as any.

So, Mozilla is a family of web browsers, but not a specific web browser (in biologic terms, Mozilla is a genus; Netscape Communicator is a species.) And (pronounced “Mozilla Dot Org” or “The Mozilla Organization”) is this group of people, the coordinators of the project.

Categorieën: Mozilla-nl planet

The Mozilla Blog: A Healthy Internet Needs Trust & Diversity

za, 31/03/2018 - 01:04

Today, Mozilla joined 115 companies in filing a friend of the court brief with the United States Supreme Court to demonstrate our continued opposition to the U.S. travel ban in State of Washington v. Trump.

As we’ve said from the outset, this travel ban threatens the free flow of ideas and innovation across borders that is an essential part of our DNA as a technology company. It also puts in jeopardy our mission to protect and advance the internet as a global public resource that is open and accessible to all.

In a similar filing with the lower circuit court, we outlined these objections along with broader concerns about the disturbing way in which the executive order at the heart of this case erodes trust in U.S. immigration law. We cannot afford to have such a dangerous precedent set that could damage the international cooperation required to develop and maintain the open internet.

Ultimately, we would like the Court to hold that blanket bans targeted at people of particular religions or nationalities are unlawful under the U.S. Constitution and harmfully impact families, businesses, and the global community. We will continue to follow this case and advocate for the free flow of information and ideas across borders, of which travel is a key part.

The post A Healthy Internet Needs Trust & Diversity appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

Cameron Kaiser: Stuff spotted in Ready Player One

vr, 30/03/2018 - 13:33
Saw Ready Player One tonight with my wife and the bro-and-sis-in-law in 3D. Capsule review: if you loved the 80s, you'll love this movie, but if you only liked the 80s you'll feel like you're being subtly manipulated. But, despite being silly and overly gamer-y, it's cute and fun, and looks pretty good. It's worth at least a matinee.

We spent a lot of time spotting old hardware in it. An Atari VCS is a major part of the plot, but we also saw a ColecoVision, though both were simulated. There were a number of old arcade cabinets, notably a Pinball 2000 Revenge From Mars. In the Macintosh world, a possibly anachronistic Macintosh LC series machine (we couldn't determine the model) turns up along with an unknown early PC which sort of resembles a Tandy 1000 of some kind. However, the real oddball was what I'm pretty sure was a Commodore 1570 disk drive. These are rather unusual and it wouldn't make sense for one to be in the United States around that time period. Watch for it in Halliday's bedroom with the unknown LC near the end of the film.

Categorieën: Mozilla-nl planet

The Firefox Frontier: Meet the Add-ons Manager

do, 29/03/2018 - 20:04

Ever wanted to fancy up your Firefox experience but weren’t sure how to do it? Are you familiar with the Add-ons Manager in Firefox? If not, please allow us to … Read more

The post Meet the Add-ons Manager appeared first on The Firefox Frontier.

Categorieën: Mozilla-nl planet

Hacks.Mozilla.Org: Hack on MDN: Building useful tools with browser compatibility data

do, 29/03/2018 - 20:00

From Friday, March 16 to Sunday, March 18, 2018, thirty-four people met in Mozilla’s Paris office to work on improving MDN’s Browser Compat Data. The amazing results included 221 pull requests that improved the quality of our data and created, prototyped, and improved tools and dashboards.

People clustered around 3 tables working on their computers in a gorgeous 19th century Parisian ballroom.<figcaption>People at work during Hack on MDN Paris 2018 in the gorgeous Garnier ballroom.</figcaption> Hack on MDN events

Hack on MDN evolved from the documentation sprints the MDN team organized between 2010 and 2013, which brought together a core team of volunteers to write and localize MDN content over a weekend. In 2014, we expanded the scope of the sprints by inviting people with different backgrounds; not just technical writers and wordsmiths, but also people who like to code or have UX design skill.

The first two Hack on MDN events happened in Paris in 2014 and Berlin in 2015. We took a break for a few years but missed the events and the community spirit they embody. This Hack on MDN in Paris was the first of two planned for this year (the next will take place in the autumn). For March, we decided to bring together an emerging MDN community and maximize productivity by focusing on a single theme with a broad scope: browser compatibility data.

The Hack on MDN format is a combination of unconference and hackathon; participants pitch projects and commit to working on concrete tasks (rather than meetings or long discussions) that can be completed in three days or less. People choose projects in which a group can make significant progress over a weekend.

Browser Compatibility Data

The web platform is unique in that it aims to create a consistent experience on top of different tools, browsers or servers. You create your website once, and it works in every browser, regardless of device, OS, or tool choice.

In an ever-evolving connected world, this is incredibly hard to achieve, and browsers implement the platform at different paces and with different priorities. Even if they aim for the same goals, it’s unlikely that a new feature is implemented by all major actors at the same time. Knowing the level of support in each browser helps developers make informed decisions about which technologies are mature enough to use, and which to avoid (e.g. unstable, non-standard, or obsolete ones).

MDN has collected this kind of browser compatibility information for the last decade and we use it to improve our reference pages. Integrating this info directly into MDN pages has had its own drawbacks: it’s been difficult to maintain, and next to impossible to reuse elsewhere. A few years ago, we decided to move this information into a machine-readable format so that it can be reused.

A BCD table containing example browser information for an unspecified "browser status"<figcaption>A typical Browser Compatibility Data (BCD) table as found on MDN Web docs.</figcaption>

Under Florian Scholz‘s lead, we are now migrating browser compatibility data into a JSON database, and we are about 60% done (including all of HTTP, HTML, JS, and even WebExtensions). We are working hard on getting all the Web APIs in it, as well as SVG, WebDriver, and MathML information.

At the same time, we are experimenting with reusing compatibility information in new tools, some developed internally and some externally. We publish our data weekly in the form of an npm package that is guaranteed to stay up-to-date as MDN itself uses it. We are our own first customer!

Our goal this year is to have 100% of the MDN compatibility info in the JSON database, as well as to start reusing this data in tools beyond our inline compatibility tables.

The 2018 Paris event

The level of interest around browser compatibility data (BCD) and the sheer amount of work left to do on it made it a natural candidate for the theme of the March event. The BCD community on Github is active and the event provided a great opportunity for contributors to meet in person.

Some code displayed on a giant screen of the Paris office during the MDN Paris Event<figcaption>When demoing, we weren’t afraid to dig deep in the code.</figcaption>

Thirty-four people from different backgrounds and organisations gathered in the splendid Mozilla Paris office: Mozilla employees (developers, writers, and even managers) from several different teams (MDN, Open Innovation, Web Compat, and WebDriver/Marionette), volunteers, and representatives from Google, Samsung, Microsoft, and the W3C (both on-site and remote).

On the first morning, Florian Scholz presented BCD and everyone introduced themselves, so people were not afraid to talk to each other during the event and got an overview of the skills available in the room. After the project pitching, people clustered into groups and the work began. It was interesting to watch people interact with others who’d either pitched an idea or had specific skills. In a quarter of an hour, everybody was already deep into hacking.

At the end of each afternoon, we gathered to demo the work that had been done. Saturday and Sunday morning we also held a set of lightning talks, where anyone could present anything, with the goal of opening our minds to other ideas.

We finished on Sunday with a final set of demos, and the outcome was truly amazing…


221 PRs were made to our repository by the participants of Hack on MDN. So many projects have been worked on that it is impossible to be exhaustive, but here are a few highlights.

Visualisation tools

Mozilla Tech Speaker and JavaScript hacker Istvan ‘Flaki’ Szmozsanszky created a tool that displays a compatibility table without the help of the server: it reads the BCD file and constructs the table directly in the browser. This is a fundamental piece of code that will allow us to easily embed compatibility tables everywhere, starting with our own pull requests on Github. Flaki went further by coding a feature to edit the JSON in the page and generate a PR from it, as well as studying how to display the differences between the current data and the new one in a visual way.

An example output of Flaki's tool, generating a local inline BCD table.<figcaption>An example output of Flaki’s tool, generating a local inline BCD table.</figcaption>

John Whitlock (from MDN’s Dev team) and Anthony Maton worked on creating a bot for GitHub requests: they focused on the back-end groundwork that will allow easy code maintenance. They created a new repository and moved the rendering code into plain JS.

Will BambergEduardo Bouças, and Daniel Beck worked on a new macro displaying aggregate data in one table, like all animation-* CSS properties.

Data migration

The more data we have in our JSON format, the more accurate the MDN pages and tools using it will be. We had just over 60% of our original data migrated before the event and made significant progress on the remaining 40% over the weekend.

Under the lead of Jérémie Patonnier from Mozilla, Maxime Lo Re and Sebastian Zartner migrated most of the SVG element data, and that of their attributes during the weekend. Chris Mills, David Ross and Bruno Bruet did the same with a lot of Web APIs. The amount of data migrated is more or less equivalent to a quarter’s worth of work and is a significant step in our migration work. Well done!

Andreas Tolfsen, one of Mozilla’s WebDriver specialists, worked, with the help of Chris Mills, to bring basic WebDriver browser compatibility info to our repository, as well as to start documenting WebDriver on MDN.

Data quality

Our data is not perfect: we have some data errors (usually this involves features marked as not supported when they have been supported), missing data (we have a way of marking unknown data differently), and of course some real code errors.

Several projects were conducted in order to improve the quality of our dataset.

Mark Dittmer from Google worked to bridge the Confluence tool with MDN. He created a tool, mdn-confluence that allows cross-checking of the information between both repositories.

Ada Rose Cannon and Peter O’Shaughnessy from Samsung created a tool that produces an initial set of data for Samsung Internet, which brings this important mobile browser to our repository. What makes this dataset even more interesting is that it has been designed to be repurposed for any Chromium-based browser, so we may be able to include QQ or UC browser info in our repository one day.

Erika Doyle, Libby McCormick, and Matt Wojciakowski from Microsoft participated remotely from the Seattle area and worked on some Edge-related data: updated EdgeHTML release dates and added Edge compat data to WebExtensions.

Scraping tools

Several people worked on taking existing data, on MDN or elsewhere, and using it to generate BCD JSON, totally or partially. These tools are valuable time-savers and will allow us to migrate data at a quicker pace.

Dominique Hazaël-Massieux from the W3C worked on a tool that takes a WebIDL as input and generates the skeleton of our BCD. This is extremely useful for all new APIs that we will want to document, as we only have to modify the values afterwards. Several PRs that Dominique submitted have been generated using this tool.

Kayce Basques from Google created a tool, MDN Crawler, which takes an MDN page and reads the browser compatibility data from it. Even if not all the data can be read correctly (the manually crafted tables do not always follow the same structure), it is able to extract a lot of information that can be manually tweaked afterwards. This is a big time saver for the migration. Kayce also published this tool as a service (with instructions).

External tools reusing the data

Eduardo Bouças worked on improving his add-on, compat-report, that produces a visual compatibility report inside Firefox Dev Tools.

Screenshot of compat-report fromEduardo Bouças.<figcaption>Screenshot of compat-report from Eduardo Bouças.</figcaption>

Julien Gattelier fixed several problems with his tool, compat-tester, adding support for global HTML attributes. He also added a contribute mode that lists features that are not in the browser compatibility dataset, allowing a user or potential contributor to detect missing features!

Dennis Schubert from Mozilla’s Web Compat team, along with Julien Gattelier and Kayce Basques, brainstormed about a new tool reusing Julien’s compat-tester tool to produce a report about the state of web compatibility, by crawling significant websites.

Other projects

Kadir Topal created a dashboard enabling us to visualize the quality of our data and measure improvements we are making.

Example of output of the data quality dashboard.<figcaption>Example of output of the data quality dashboard.</figcaption> What’s next?

There is a lot of follow-up work to do: we need to review all the PRs and do some work to integrate new prototypes and tools into our codebase or workflow. It is a good problem to have!

Overall, we will continue to migrate our browser compat data and improve its quality: the better the data is, the better the tools using it – and MDN Web docs itself – will be.

The most important outcome of this event is human: by working together we created new bonds and the relationships between participants will hopefully continue and grow, bringing extra awesomeness into the future of MDN Web Docs and the Browser Compatibility Data project.

Want to get involved? Not sure where to begin? Visit the MDN community on Discourse to learn about what we do and how you can make MDN more awesome with your contribution.

Categorieën: Mozilla-nl planet

The Mozilla Blog: Mozilla marks 20th anniversary with commitment to better human experiences online

do, 29/03/2018 - 16:00

This coming Saturday — March 31 — is Mozilla’s 20th anniversary. We’ve accomplished a fair amount in the first 20 years. We aim to accomplish even more in the next 20 years. To do this, we’ve modernized nearly every aspect of Mozilla, from Firefox to the many ways we connect people and technology.

We’re making our first major addition to the key principles that form the foundation for Mozilla’s work. These principles are set out in the Mozilla Manifesto, which was launched in 2007. The Mozilla Manifesto identifies ten principles that we work to build into Firefox and online life generally. The internet should be a global public resource, open and accessible to all. Individuals should have control of their experience. Safety is critical. Private commercial profit and social benefit should coexist in a healthy fashion. We use these principles regularly to describe Mozilla’s identity and inform our decision-making. You can see the Manifesto here.

Today we add four topics to the Mozilla Manifesto. We do this to explicitly address the quality of people’s experiences online.

  • We are committed to an internet that includes all the peoples of the earth — where a person’s demographic characteristics do not determine their online access, opportunities, or quality of experience.
  • We are committed to an internet that promotes civil discourse, human dignity, and individual expression.
  • We are committed to an internet that elevates critical thinking, reasoned argument, shared knowledge, and verifiable facts.
  • We are committed to an internet that catalyzes collaboration among diverse communities working together for the common good.

The full addendum is available on our website, where you are invited to share your support for these new principles via Twitter.

The Manifesto and the addendum will continue to guide our work everyday — how we design products, build technology, build communities and work with others. We hope to encourage, create, lead and support many experiments in bringing these goals to life, and we hope to join with many others pursuing similar ideas.

The post Mozilla marks 20th anniversary with commitment to better human experiences online appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet