Mozilla Firefox gets better search bar, dev tools
Mozilla has rolled out a new version of Firefox, giving it the ability to natively handle certain types of files and adding a search field on the New Tab page. Firefox Version 31 has variants for desktop and mobile platforms, including Microsoft's ...
New Firefox 31 focuses on improving developer toolsVentureBeat
alle 7 nieuwsartikelen »
Firstly, a screenshot:
I wish there was more dark green
Now, let's have a look at the commit that made the streak reach 200. That's right, it's a merge commit to Servo — something which is created for the collaborator who merges the pull request1. Which is a great segue into the second half of this post:
I now have commit/collaborator access to Servo. :D
It happened around a week back. Ms2ger needed a reviewer, Lars mentioned he wanted to get me more involved, I said I didn't mind reviewing, and in a few minutes I was reviewing a pull request for the first time. A while later I had push access.
This doesn't change my own workflow while contributing to Servo; since everyone still goes through pull requests and reviews. But it gives a much greater sense of belonging to a project. Which is saying something, since Mozilla projects already give one a sense of being "part of the team" rather early on, with the ability to attend meetings, take part in decision-making, and whatnot.
I also now get to review others' code, which is a rather interesting exercise. I haven't done much reviewing before. Pull requests to my own repos don't count much since they're not too frequent and if there are small issues I tend to just merge and fix. I do give feedback for patches on Firefox (mostly for the ones I mentor or if asked on IRC), but in this situation I'm not saying that the code is worthy to be merged; I'm just pointing out any issues and/or saying "Looks good to me".
With Servo, code I review and mark as OK is ready for merging. Which is a far bigger responsibility. I make mistakes (and style blunders) in my own code, so marking someone else's code as mistake free is a bit intimidating at first. Yes, everyone makes mistakes and yet we have code being reviewed properly, but right now I'm new to all this, so I'm allowed a little uncertainty ;) Hopefully in a few weeks I'll be able to review code without overthinking things too much.
In other GitHub-ish news, a freshman of my department submitted a very useful pull request to one of my repos. This makes me happy for multiple reasons: I have a special fondness for student programmers who are not from CS (not that I don't like CS students), being one myself. Such students face an extra set of challenges of finding a community, learning the hard stuff without a professor, and juggling their hobby with normal coursework (though to be fair for most CS students their hobby programming rarely intersects with coursework either).
Additionally, the culture of improving tools that you use is one that should be spread, and it's great that at least one of the new students is a part of this culture. Finally, it means that people use my code enough to want to add more features to it :)
1. I probably won't count this as part of my streak and make more commits later today. Reviewing is hard, but it doesn't exactly take the place of writing actual code so I may not count merge commits as part of my personal commit streak rules.
Mozilla's Operations Security team (OpSec) protects the networks, systems, services and data that power the Mozilla project. The nature of the job forces us to keep a lot of our activity behind closed doors. But we thrive to do as much as possible in the open, with projects like MIG, Mozdef, Cipherscan, OpenVPN-Netfilter, Duo-Unix or Audisp-Json.
Opening up security discussions to the community, and to the public, has been a goal for some time, and today we are making a step forward with the OpSec mailing list at
This mailing list is a public place for discussing general security matters among operational teams, such as public vulnerabilities, security news, best practices discussions and tools. We hope that people from inside and outside of Mozilla will join the discussions, and help us keep Mozilla secure.
So join in, and post some cool stuff!
If you haven't seen the release notes WebVTT has finally been released in Firefox 31. I'm super excited about this as it's the culmination of a lot of my own and countless others' work over the last two years. Especially since it has been delayed for releases 29 and 30.
That being said, there are still a few known major bugs with WebVTT in Firefox 31:
- TextTrackCue enter, exit, and change events do not work yet. I'm working on getting them done now.
- WebVTT subtitles do not show on audio only elements yet. This will probably be what is tackled after the TextTrackCue events (EDIT: To clarify, I meant audio only video elements).
- There is no support for any in-band TextTrack WebVTT data yet. If your a video or audio codec developer that wants in-band WebVTT to work in Firefox, please help out :-).
- Oh, and there is no UI on the HTML5 Video element to control subtitles... not the most convenient, but it's currently being worked on as well.
Mozilla veröffentlicht Firefox 31, Firefox Mobile 31 und Thunderbird 31
Mozilla hat neue Versionen von Firefox und Thunderbird veröffentlicht. Beide neuen Programmversionen sind von besonderer Bedeutung, so stellt Firefox 31 die Basis für die nächsten 54 Wochen Firefox ESR dar, Thunderbird 31 ist das erste Major-Update ...
Things have to be scheduled when there’s so much to ‘ship’ at an organization like Mozilla. So we’re still a couple of weeks away from a landing page for all of the badges at webmaker.org. This post has a link to all of the Web Literacy badges now available.
We’ve just finished testing the 15 Web Literacy ‘maker’ badges I mentioned in a previous post. Each badge corresponds to the ‘Make’ part of the resources page for the relevant Web Literacy Map competency. We’re not currently badging ‘Discover’ and ‘Teach’. If this sounds confusing, you see what I mean by viewing, as an exmaple, the resources page for the Privacy competency.
Below is a list of the Web Literacy badges that can apply for right now. Note that you might want to follow this guidance if and when you do!EXPLORING
- Composing for the Web: Maker
- Remixing: Maker
- Design and Accessibility: Maker
- Coding / Scripting: Maker
Why not set yourself a challenge? Can you:
- Collect one from each strand?
- Collect all the badges within a given strand?
- Collect ALL THE BADGES?
Mozilla Thunderbird 31.0
De Mozilla Thunderbird logo (90 pix) Mozilla Foundation heeft na een lange tijd met updates met versienummer 24.6.x nu versie 31 van Thunderbird uitgebracht en trekt daarmee het versienummer gelijk met de browser Firefox. Mozilla Thunderbird is een ...
en meer »
Mozilla Firefox 31.0
Mozilla Firefox 2013 logo (75 pix) Mozilla heeft versie 31 van zijn webbrowser Firefox uitgebracht. In versie 31 is Firefox onder meer in Windows in staat om .ogg mediabestanden, en pdf-documenten te openen. Verder krijgen nieuwe tabbladen een zoekveld ...
I am happy to announce that Lightning 3.3, a new major release, is out of the door. Here are a few release highlights:
- Various components have been made asynchronous, allowing for better perceived performance. This means less hanging when Lightning is busy.
- Improved invitation processing, as well as a few new features:
- Restrict sending invitations to newly added attendees
- Send one invitation email per attendee, not disclosing other attendees
- Consider default BCC and CC of configured email identity when sending invitations
- More actions when viewing invitations, e.g. tentative accept, accepting only occurrences.
- When accessing Google Calendar via CalDAV, the authentication dialog doesn’t constantly reappear.
There have also been a lot of changes in the backend that are not visible to the user. This includes better testing framework support, which will help avoid regressions in the future. A total of 103 bugs have been fixed since Lightning 2.6.
When installing or updating to Thunderbird 31, you should automatically receive the upgrade to Lightning 3.3. If something goes wrong, you can get the new versions here:
Should you be using Seamonkey, you will have to wait for the 2.28 release, which is postponed as per this thread.
If you encounter any major issues, please comment on this blog post. Support issues are handled on support.mozilla.org. Feature requests and bug reports can be made on bugzilla.mozilla.org in the product Calendar. Be sure to search for existing bugs before you file them.
Browser-based gaming gets a push with Mozilla's plugin-free technology
Mozilla has been pushing the idea of using web apps instead of native apps on mobile phones with its Firefox OS operating system for phones and tablets. At the same time, the folks at Mozilla have been working to make games you run in a desktop web ...
A friend of a friend asked this morning:
— Jenny Molloy (@jenny_molloy) July 22, 2014
I suggested Wikimedia Commons, but it turns out she wanted something like Slideshare’s embedding. So here’s a test of how that works (timely, since soon Wikimanians will be uploading dozens of slide decks!)
This is what happens when you use the default Commons “Use this file on the web -> HTML/BBCode” option on a slide deck pdf:
Not the worst outcome – clicking gets you to a clickable deck. No controls inline in the embed, though. And importantly nothing to show that it is clickable :/
Compare with the same deck, uploaded to Slideshare:
Some work to be done if we want to encourage people to upload to Commons and share later.
Update: a commenter points me at viewer.js, which conveniently includes a wordpress plugin! The plugin is slightly busted (I had to move some files around to get it to work in my install) but here’s a demo:
Mozilla's Asm.js Technology Makes Its Commercial Debut With Dungeon ...
en meer »
Yunier José Sosa Vázquez: Nueva verificación de certificados, depuradores y funcionalidades para Firefox
Los navegadores hoy en día son parte esencial de nuestra vida, con ellos podemos navegar en Internet, jugar, hacer compras, oír música, ver videos, etc. Un video puede estar grabado en un idioma que no entendemos y necesitamos subtítulos para entender lo que se dice. Para la web, estos archivos están regidos por el formato para mostrar texto en pistas WebVTT a través del elemento <track> y ser utilizados en <video> para añadir subtítulos. De ahora en adelante los usuarios de Firefox podremos disfrutar de subtítulos en los videos de la web y los desarrolladores podrán emplearlos.
Una nueva librería para verificar la veracidad de los certificados e incrementar la seguridad de los usuarios finales está siendo usada por esta nueva versión de Firefox. mozilla::pkix — como es llamada, es más robusta, fácil de mantener y mejora el consumo de memoria. Su código puede ser visto por cualquier persona desde aquí.
Para realizar búsquedas más fácil se agregó el campo de búsqueda en la página Nueva pestaña, desde allí puedes elegir el motor de búsqueda a utilizar en Firefox.
Los complementos son una de las características de Firefox que más te gustan, con ellos puedes agregar funcionalidades que no se encuentran por defecto en el navegador y personalizarlo a tu modo. Por esa razón, se ha implementado un depurador para complementos que permitirá a los desarrolladores contar con una herramienta que les ayude a localizar errores y probar sus creaciones.
Las Firefox Hub APIs permiten a los desarrolladores de complementos que sus creaciones incorporen contenidos propios a la página de inicio — donde los usuarios pueden encontrar marcadores, sitios más visitados, etc — e incrementar la interacción de los usuarios con estos. Para más detalles puedes visitar la documentación en MDN y ver algunos complementos de ejemplos.
También se suman las mejoras de estabilidad y rendimiento de la APK Factory, las cuales proveen una mejor “experiencia nativa” para aplicaciones Web en Android. Usando APK Factory los desarrolladores de aplicaciones para Firefox OS pueden portar a millones de usuarios de Android sus desarrollos sin tener que cambiar una línea de código. El APK Factory también asegura que las aplicaciones corran en un ambiente de ejecución actualizado, por lo que no presentarán problemas de degradación o compatibilidad.
- Se ha añadido la posibilidad de reordenar los paneles existentes en about:home.
- Soporte para más lenguajes: Asamés [as], Bengali [bn-IN], Gujarati [gu-IN], Hindi [hi-IN], Kannada [kn], Maithili [mai], Malayalam [ml], Marathi [mr], Oriya [or], Panjabi [pa-IN], Tamil [ta], Telugu [te].
- Botón para actualizar manualmente en la página de pestañas sincronizadas.
- Preferencia navigator.sendBeacon habilitada por defecto.
- Los archivos .PDF y .OGG son manejados por Firefox sino se especifica una aplicación para hacerlo.
- Mejoras en el editor de código (Herramientas para desarrollo).
- Implementación parcial de las tablas matemáticas OpenType (ver documentación).
- Implementadas y habilitadas las variables CSS3.
- Nueva herramienta “Eyedropper“ para obtener el color fácilmente (Herramientas para desarrollo).
- Modelo de caja editable al analizar los elementos HTML (Herramientas para desarrollo).
- Un depurador para Canvas (Herramientas para desarrollo).
- Muchos cambios más.
Si deseas conocer más, puedes leer las notas de lanzamiento.
Puedes obtener esta versión desde nuestra zona de Descargas en español e inglés para Linux, Mac, Windows y Android. Recuerda que para navegar a través de servidores proxy debes modificar la preferencia network.negotiate-auth.allow-insecure-ntlm-v1 a true desde about:config.
the following changes have been pushed to bugzilla.mozilla.org:
-  Field name is still “Bug #” for the Bug Created field
-  Change all bugs with firstname.lastname@example.org assignee to email@example.com
-  Please add FlagTypeComments for tracking/approval flags
-  Change Several Bugs at Once Does Not Allow Modification of the QA Whiteboard
-  update FlagDefaultRequestee extension to use object hooks
-  Bugzilla detects Firefox OS device as Hardware:Other, OS:Other
-  “blocks” field is present as empty string when empty, rather than null or 
-  Provide good error message when people can’t use form.legal
-  A few more “Bugmail filtering” fields need to be excluded from the prefs UI
-  “Please wait while your bugs are retrieved” shown above menu header for search error pages
-  Move OS: Windows 8 Metro to Windows 8.1
discuss these changes on mozilla.tools.bmo.
Filed under: bmo, mozilla
Broadband Roundup: Comcast Seeks Lighter Regulation on Net Neutrality ...
The open sources software company Mozilla, however, wants Title II reclassification. It said in its own comments that Title II is “essential to the maintenance of the 'virtuous cycle' of innovation and investment that powers communications on the ...
en meer »
Firefox 31: Der neue Mozilla-Browser zum Download
Der Webbrowser Mozilla Firefox zählt zu den beliebtesten Internetbrowsern der Welt! Über 100 Millionen Nutzer sprechen für Mozilla Firefox, einen Browser, der besonders durch seine Schnelligkeit und einfache Handhabe besticht. Die gemeinnützig ...
Firefox 31 mit automatischem Müll-Sammler verfügbarPC-Welt
Mozilla Firefox: Veraltete Versionen des Browsers erhalten automatische UpdatesSoftonic DE
Browser - Mozilla veröffentlicht Firefox 31Ad-Hoc-News (Pressemitteilung)
soeren-hentzschel.at -Futurezone -WinFuture
alle 12 nieuwsartikelen »
Jennie Rose Halperin: Numbers are not enough: Why I will only attend conferences with explicitly enforceable Codes of Conduct and a commitment to accessibility
I recently had a bad experience at a programming workshop where I was the only woman in attendance and eventually had to leave early out of concern for my safety.
Having to repeatedly explain the situation to a group of men who promised me that “they were working on fixing this community” was not only degrading, but also unnecessary. I was shuttled to three separate people, eventually receiving some of my money back approximately a month later (which was all I asked for) along with promises and placating statements about “improvement.”
What happened could have been prevented: each participant signed a “Code of Conduct” that was buried in the payment for the workshop, but there was no method of enforcement and nowhere to turn when issues arose.
At one point while I was attempting to resolve the issue, this community’s Project Manager told me, “Three other women signed up, but they dropped out at the last minute because they had to work. It was very strange and unexpected that you were the only woman.” I felt immediately silenced. The issue is not numbers, but instead inviting people to safe spaces and building supportive structures where people feel welcomed and not marginalized. Increasing the variety of people involved in an event is certainly a step, but it is only part of the picture. I realize now that the board members of this organization were largely embarrassed, but they could have handled my feelings in a way where I didn’t feel like their “future improvements” were silencing my very real current concerns.
Similarly, I’ve been thinking a lot about a conversation I had with some members of the German Python community a few months ago. Someone told me that Codes of Conduct are an American hegemonic device and that introducing the idea of abuse opens the community up for it, particularly in places that do not define “diversity” in the same way as Americans. This was my first exposure to this argument, and it definitely gave me a lot of food for thought, though I adamantly disagree.
In my opinion, the open-source tech community is a multicultural community and organizers and contributors have the responsibility to set their rules for participation. Mainstream Western society, which unfortunately dictates many of the social rules on the Internet, does a bad job teaching people how to interact with one another in a positive and genuine way, and going beyond “be excellent to one another, we’re all friends here!” argument helps us participate in a way in which people feel safe both on and off the Web.
At a session at the Open Knowledge Festival this week, we were discussing accessibility and realized that the Code of Conduct (called a “User Guide”) was not easily located and many participants were probably not aware of its existence. The User Guide is quite good: it points to other codes of conduct, provides clear enforcement, and emphasizes collaboration and diversity.
At the festival, accessibility was not addressed in any kind of cohesive manner: the one gender-neutral bathroom in the huge space was difficult to find, sessions were loud and noisy and often up stairs, making it impossible for anyone with any kind of hearing or mobility issue to participate, and finally, the conference organizers did not inform participants that food would not be free, causing the conference’s ticket price to increase dramatically in an expensive neighborhood in Berlin.
In many ways, I’m conflating two separate issues here (accessibility and behavior of participants at an event.) I would counter that creating a safe space is not only about behavior on the part of the participants, but also on the part of the conference organizers. Thinking about how participants interact at your event not only has to do with how people interact with one another, but also how people interact with the space. A commitment to accessibility and “diversity” hinges upon more than words and takes concerted and long term action. It may mean choosing a smaller venue or limiting the size of the conference, but it’s not impossible, and incredibly important. It also doesn’t have to be expensive! A small hack that I appreciated at Ada Camp and Open Source Bridge was a quiet chill out room. Being able to escape from the hectic buzz was super appreciated.
Ashe Dryden writes compellingly about the need for better Codes of Conduct and the impetus to not only have events be a reflection of what a community looks like, but also where they want to see them go. As she writes,
I worry about the conferences that are adopting codes of conduct without understanding that their responsibility doesn’t end after copy/pasting it onto their site. Organizers and volunteers need to be trained about how to respond, need to educate themselves about the issues facing marginalized people attending their events, and need to more thoughtfully consider their actions when responding to reports.
Dryden’s Code of Conduct 101 and FAQ should be required reading for all event organizers and Community Managers. Codes of Conduct remove the grey areas surrounding appropriate and inappropriate behavior and allow groups to set the boundaries for what they want to see happening in their communities. In my opinion, there should not only be a Code of Conduct, but also an accessibility statement that collaboratively outlines what the organizers are doing to make the space accessible and inclusive and addresses and invites concerns and edits. In her talk at the OKFestival, Penny pointed out that accessibility and inclusion actually makes things better for everyone involved in an event. As she said, “No one wants to sit in a noisy room! For you, it may be annoying, but for me it’s impossible.”
Diversity is not only about getting more women in the room, it is about thinking intersectionally and educating oneself so that all people feel welcome regardless of class, race, physicality, or level of education. I’ve had the remarkable opportunity to go to conferences all over the world this year, and the spaces that have made an obvious effort to think beyond “We have 50% women speakers!” are almost immediately obvious. I felt safe and welcomed at Open Source Bridge and Ada Camp. From food I could actually eat to lanyards that indicated comfort with photography to accessibility lanes, the conference organizers were thoughtful, available, and also kind enough that I could approach them if I needed anything or wanted to talk.
From now on, unless I’m presented a Code of Conduct that is explicit in its enforcement, defines harassment in a comprehensive manner, makes accessibility a priority, and provides trained facilitators to respond to issues, you can count me out of your event.
We can do better in protecting our friends and communities, but change can only begin internally. I am a Community Manager because we get together to educate ourselves and each other as a collaborative community of people from around the world. We should feel safe in the communities of practice that we choose, whether that community is the international Python community, or a local soccer league, or a university. We have the power to change our surroundings and our by extension our future, but it will take a solid commitment from each of us.
Events will never be perfect, but I believe that at least in this respect, we can come damn close.