Mozilla developers continue moving along with their support for the GTK3 tool-kit inside the Firefox web-browser.
Firefox Nightlies/Aurora are built with GTK3+ on Linux. While there's been the basic GTK+ 3 support, other items relating to this new tool-kit support still need to be finished up. One of the items now complete is handling touch events of this latest GTK+ version.
At Mozilla, community participation creates a dynamic that values transparency, drives the relationship with users, and produces a clear sense of mission.
To learn more, I invited Mozilla's Chief Marketing Officer, Jascha Kaykas-Wolff, to appear as a guest on CXOTalk. The conversation is important to anyone interested in open source, principled marketing, and the power of community participation in product development.
Rust is a systems programming language that got its start in 2010 with Mozilla Research. Today, one of Rust's most ardent developers and guardians is Steve Klabnik, who can you find traveling the globe touting it's features and teaching people how to use it.
At All Things Open 2015, Steve will give attendees all they need to know about Rust, but we got an exclusive interview prior to his talk in case you can't make it.
Mozilla has released a new report — mzl.la/localcontent — co-authored with the GSMA. Titled “Approaches to local content creation: realising the smartphone opportunity,” our report explores how the right tools, coupled with digital literacy education, can empower mobile-first Web users as content creators and develop a sustainable, inclusive mobile Web.
With the upcoming releases of the Mozilla Firefox and Google Chrome web-browsers is support for the W3C Subresource Integrity (SRI) specification.
The Subresource Integrity feature allows web developers to ensure that externally-loaded scripts/assets from third-party sources (e.g. a CDN) haven't been altered. The SRI specification adds a new "integrity" HTML attribute when loading such assets where you can specify a hash of the file source expected -- the loaded resource must then match the hash for it to be loaded.
Content is not inherently good or bad – with some notable exceptions, such as malware. So these principles aren’t about what content is OK to block and what isn’t. They speak to how and why content can be blocked, and how the user can be maintained at the center through that process.
At Mozilla, our mission is to ensure a Web that is open and trusted and that puts our users in control. For content blocking, here is what we think that means.