Mozilla Nederland LogoDe Nederlandse

Zamrzla vám Mozilla Firefox? Nebohá liška v ledu hitem internetu! -

Nieuws verzameld via Google - fr, 13/01/2017 - 16:29

Zamrzla vám Mozilla Firefox? Nebohá liška v ledu hitem internetu!
... mnoho lidí na internetu pobavil. „Takhle to vypadá, když vypadá, když vám zamrzne prohlížeč Mozilla Firefox,“ napsal jeden z uživatelů Facebooku. „Copak, zamrzla vám Mozilla Firefox?“ svezl se na stejné notě další. Firefox znamená totiž ohnivá liška.

en meer »
Categorieën: Mozilla-nl planet

Zamrzla vám Mozilla Firefox? Nebohá liška v ledu hitem internetu! -

Nieuws verzameld via Google - fr, 13/01/2017 - 16:29

Zamrzla vám Mozilla Firefox? Nebohá liška v ledu hitem internetu!
... mnoho lidí na internetu pobavil. „Takhle to vypadá, když vypadá, když vám zamrzne prohlížeč Mozilla Firefox,“ napsal jeden z uživatelů Facebooku. „Copak, zamrzla vám Mozilla Firefox?“ svezl se na stejné notě další. Firefox znamená totiž ohnivá liška.

en meer »
Categorieën: Mozilla-nl planet

Mozilla experimentiert mit Google-Ersatz für Firefox -

Nieuws verzameld via Google - fr, 13/01/2017 - 16:06

Mozilla experimentiert mit Google-Ersatz für Firefox
Mozilla hat sein “Pilot” gennantes Testprogramm jetzt auch in Deutsch nutzbar gemacht. Zum Start wurden Funktionen des deutschen Browser-Anbieters Cliqz integriert. An dem Münchner Unternehmen hatte sich Mozilla im vergangenen Jahr beteiligt.
Firefox Test Pilot bringt Cliqz und weitere experimentelle
"Firefox Test Pilot": Deutsche Version gestartetHeise Newsticker
Neues Firefox-Experiment: Der Browser bekommt eine eigene SuchmaschineCHIP Online
alle 9 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Mozilla откажется от поддержки Windows XP и Vista - МИР NVIDIA

Nieuws verzameld via Google - fr, 13/01/2017 - 08:01


Mozilla откажется от поддержки Windows XP и Vista
У пользователей устаревших систем будет возможность задуматься над обновлением, поскольку выпускать обновления безопасности Mozilla будет лишь «до сентября 2017 года». Таким образом промышленные пользователи обозревателя ...

Google Nieuws
Categorieën: Mozilla-nl planet

Missing from the Trump Cabinet Nominee Hearings: Cybersecurity for Everyday Internet Users

Mozilla Blog - wo, 11/01/2017 - 20:14

This week, the U.S. Senate is assessing a slate of cabinet nominees for the incoming Trump administration. If confirmed, these nominees are some of the people who will shape public policy for the next several years on critical issues — including civil liberties and national security.

Members of the Senate asked a range of essential and direct questions. But cybersecurity questions were not a significant part of the discussion in the hearing for potential Attorney General Jeff Sessions, who will lead the Department of Justice, including law enforcement investigations that involve technology.

At the recent Sessions’ Senate hearings, cybersecurity was discussed chiefly in regard to government-sponsored cyberattacks. Discussion about robust cybersecurity for everyday Internet users — through practices like strong encryption — was largely absent.

Mozilla is disappointed that cybersecurity — and the stances from appointees who will need to work on it regularly — was not a priority at the Senate hearings. It would have been helpful if the Senate asked Sessions to clarify his position, and even better if they asked him to clarify that privacy and security are important for all Americans and a healthy Internet.

We need a government that openly discusses — and values — a more secure Internet for all users.

Protecting users’ privacy and security online is a crucial issue for all of us. Security protects elections, economies and our private online and offline lives. And many recent events (cyber attacks, hacks and threats by foreign governments) show that a secure Internet is currently under threat.

I recently wrote about how cybersecurity is a shared responsibility. Governments, technology companies and users need to work together to strengthen cybersecurity. Mozilla knows that even one weak link — be it technical or legislative — can break the chain of security and put Internet users at risk. The chain only remains strong if technology companies, governments and users work together to keep the Internet as secure as it can be.

You can help Mozilla stand up for a more secure Internet. We’re asking readers to pen a Letter to the Editor to their local newspaper in response to this week’s Senate hearings, and support personal security and privacy online. Get started here.

Categorieën: Mozilla-nl planet

Mozilla's Holiday Brand Project Was a Data Privacy Pop-up in NYC -

Nieuws verzameld via Google - wo, 11/01/2017 - 13:02

Mozilla's Holiday Brand Project Was a Data Privacy Pop-up in NYC
During prime holiday shopping season, a tech company lured unsuspecting passersby into a brightly lit storefront on Mulberry Street in Lower Manhattan. It had the familiar, sparse design of a hip gadget store -- white walls, long white tables and ...

Categorieën: Mozilla-nl planet

Firefox: Mozilla und Cliqz starten Test Pilot-Experiment -

Nieuws verzameld via Google - wo, 11/01/2017 - 10:18

Firefox: Mozilla und Cliqz starten Test Pilot-Experiment
Unter dem Namen Test Pilot führt Mozilla Experimente durch, welche es Firefox-Nutzern ermöglichen, potentielle neue Funktionen vorab zu testen und Feedback zu geben. Nun hat man gemeinsam mit Cliqz ein neues Experiment für deutschsprachige ...

Categorieën: Mozilla-nl planet

Taki będzie Firefox? Mozilla ogłasza harmonogram prac nad Servo w roku 2017 - dobreprogramy

Nieuws verzameld via Google - ti, 10/01/2017 - 17:30


Taki będzie Firefox? Mozilla ogłasza harmonogram prac nad Servo w roku 2017
Miniony rok na rynku przeglądarek upłynął pod znakiem niezmiennej dominacji Chrome'a, sporych nowości w Operze oraz rosnącego zainteresowania nowym graczem, Vivaldim. Na tym tle blado wypada Firefox, któremu wielu – mimo sentymentu ...

Categorieën: Mozilla-nl planet

Jared Wein: eslint updates for Firefox developers

Mozilla planet - ti, 10/01/2017 - 16:26

In the past week there has been quite a lot of progress made on the eslint front.

Last week I enabled the following rules for the default mozilla-central eslint configuration (/toolkit/.eslintrc.js):

Mark Banner has continued to work on fixing the remaining no-undef errors. This work is on-going and is being tracked by a meta bug.

Florian Quèze just landed a patch yesterday to simplify calls to so the two trailing arguments are optional. Previously 99% of the calls to the function passed in null for the trailing arguments. Florian is planning on cleaning up some addEventListener code as well and I am pushing for him to implement special eslint rules along with them to help enforce these changes going forward.

I enabled most of the rules for eslint and gathered counts of the number of errors related to each rule. The following list shows each disabled rule along with the number of associated errors as of mozilla-central revision f13abb8ba9f3:

  • array-callback-return = 3
  • no-new-func = 13
  • no-useless-concat = 14
  • no-void = 14
  • no-multi-str = 15
  • no-new-wrappers = 18
  • no-array-constructor = 20
  • no-eval = 20
  • no-await-in-loop = 21
  • no-sequences = 22
  • no-inner-declarations = 23
  • no-unmodified-loop-condition = 24
  • wrap-iife = 25
  • no-constant-condition = 28
  • no-template-curly-in-string = 39
  • no-loop-func = 44
  • no-fallthrough = 51
  • no-new = 56
  • no-throw-literal = 134
  • no-prototype-builtins = 158
  • no-caller = 165
  • no-unused-expressions = 171
  • no-useless-escape = 194
  • complexity = 208
  • no-case-declarations = 238
  • guard-for-in = 284
  • radix = 342
  • no-shadow = 356
  • no-eq-null = 442
  • dot-notation = 459
  • default-case = 485
  • block-scoped-var = 749
  • no-empty-function = 1144
  • dot-location = 2327
  • no-extra-parens = 2464
  • no-invalid-this = 2947

If you would like to work on fixing any of these, please file a bug in the Toolkit :: General component of Bugzilla and request review from myself, Mossop, or Standard8.

If you’d like eslint to run on a directory that you work in, remove the reference to it from the .eslintignore file located at the mozilla-central root and add a .eslintrc.js file. This will now allow eslint to scan that directory.

Also, another project that someone can pick up is to help us move towards a single rule definition. We would like to move to a single set of rules which will help for consistent coding styling. You can look at this listing of .eslintrc.js files to see the differences between them. Some define globals that are unique to the directory or have different include paths to the root configuration, but some also define extra rules. We would like to get those rules added to the root configuration, though we haven’t determined how to settle rule conflicts yet.

Tagged: eslint, firefox, mozilla, planet-mozilla
Categorieën: Mozilla-nl planet

David Lawrence: Happy BMO Push Day!

Mozilla planet - ti, 10/01/2017 - 16:07

the following changes have been pushed to

  • [1328665] Two issues with Project Review form for RRAs
  • [1307478] Elasticsearch Indexer / Bulk Indexer
  • [1328650] Update HRBP list in Recruiting Product
  • [1209242] Can’t locate object method “_reverseoperator” via package “Bugzilla::Search” at /data/www/ line 3134.
  • [1280388] [a11y] Make the bug summary a heading level 1

discuss these changes on

Categorieën: Mozilla-nl planet

Mozilla Reps Community: Rep of the Month – December 2016

Mozilla planet - ti, 10/01/2017 - 15:09

Join us to congratulate Srushtika as Rep of the month for December.

Srushtika is an undergraduate student in her final year. She describes herself as “Tech-Speaker at Mozilla that loves speaking and advocating new technologies that could change the way we spend our lives.” But she is so much more than that. During the last few months she has been working along with Ram on building the local Indian WebVR community. She has also created MozActivate best practices while she is also working on an intro guide for newbies in WebVR events based on Rust guides.

Srushtika with a VR headset on her head

Moreover, she is heavily involved on shaping the Campus program and suggesting activities for campus students. All the above gained her a mention on the VR/AR inspirations of 2016 blogpost. When she is not studying or contributing to VR, Srushtika is helping the privacy month team from India on advocating about privacy in social media. Check them out on #privacymonth.

Congratulations Srushtika, you’re a true inspiration to all of us. Keep on rocking! Please join us in congratulating her over at Discourse!

Categorieën: Mozilla-nl planet

Gervase Markham: Modern Communications

Mozilla planet - ti, 10/01/2017 - 12:33

I just sent something very like the following to someone buying a house from me:

This text is to tell you that I just emailed you a PDF copy of the fax my solicitor just sent your solicitor, containing the email he originally sent last week which your solicitor claimed he didn’t get, plus the confirmation that the fax was received.

Categorieën: Mozilla-nl planet

Techbedrijven steunen Facebook in strijd tegen zwijgbevelen VS -

Nieuws verzameld via Google - ti, 10/01/2017 - 10:46

Techbedrijven steunen Facebook in strijd tegen zwijgbevelen VS
Dit zou inhouden dat bedrijven zoals Mozilla onrechtmatige bevelen niet kan aanvechten. En omdat zwijgbevelen ervoor zorgen dat wij gebruikers niet kunnen waarschuwen, kunnen ook deze gebruikers ze niet aanvechten. Onrechtmatige bevelen worden ...

Categorieën: Mozilla-nl planet

Brian Birtles: Web animation in 2017

Mozilla planet - ti, 10/01/2017 - 09:11

Happy new year! As promised I thought I’d share a few of the Web animation things I’m looking forward to in 2017. I’m terrible at predicting the future (I used to be a believer in BeOS and VRML) so this is mostly based on what is already in motion.


  1. CSS transitions – this should move to CR status soon. Part of that involves splitting off a separate Timing Functions spec. That separate spec would give us:
    • Level 1: An additional frames() timing function to do what step-end and step-start should have done in the first place.
    • Level 2: Low-level syntax for export of complex timing functions (multi-segment béziers?), spring timing functions, script-defined timing functions, and perhaps even timing functions that affect the duration of animations.
  2. CSS animations – this too should move to CR soon. All that is really missing is some clarification about the liveness of values and some text about how @keyframes rules cascade. Then we can start work on new things in level 2 like animation-composition.
  3. Web animations – this too is approaching CR and I hope we can ship (most of) the remainder of the API in the first half of this year in Firefox and Chrome. For that we still need to:
    • Add a FillAnimation concept to allow browsers to compact finished but filling animations so they don’t keep consuming memory. This is a bit hard, but seems do-able.
    • Simplify the timing interfaces to use fewer live objects and make the interface consistent with keyframe interfaces. I hope this will simplify the implementation for Edge and Safari too.
    • Add compositeBefore and compositeAfter methods to control how animations combine and overlap.
    • Replace SharedKeyframeList with StylePropertyMaps from Houdini.
    • Integrate a few tweaks to making specifying keyframes more flexible.

    I’m looking forward to shipping additive animation soon since it helps with a lot of use cases, but it really needs FillAnimation first.

    getAnimations is also exciting—being able to inspect and manipulate CSS animations and transitions from the same API—but probably won’t ship until the second half of the year when we have the mapping between CSS and Web Animations clearly specified.

    Being able to ship the finished and ready promise would be great but was blocked on cancelable promises being realized and now it’s not clear what will happen there.

  4. Scroll-driven animations – This is going to take quite a bit of work to get right, but hopefully within this year we can start shipping parts of it so you can create hidey bars and parallax effects that run smoothly on the compositor.
  5. AnimationWorklet – This is also going to take time to make sure it plays well with the other animation pieces in the platform but fortunately the Chrome folks pushing it have been very responsive to feedback and admirable in their willingness to rethink ideas.

At Mozilla, apart from editing and implementing the above specs, some of the bigger animation items I anticipate this year include:

  1. Making our current animation features work with Quantum CSS (introduction), i.e. Servo’s style engine. This involves a lot of tricky plumbing but it means Firefox gets faster and Servo gets more spec compliant.
  2. CSS offset (aka CSS motion). We’ve been putting this off for a while as the spec stabilizes but I hope this year we will actually do it.
  3. Promoting various SVG attributes to properties. Tackling this and the previous item would significantly narrow the gap between CSS and SVG’s (SMIL) animation features and let us simplify the SMIL code a lot.
  4. Animation of CSS custom properties. There are patches written but they need some work before they land.
  5. DevTools. We have plenty of ideas here but most of all we want to make our animation DevTools the place to go not just to debug all the above features, but also to author for them!

If any of those items sound interesting to you, please get involved!

Categorieën: Mozilla-nl planet

This Week In Rust: This Week in Rust 164

Mozilla planet - ti, 10/01/2017 - 06:00

Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community News & Blog Posts Other Weeklies from Rust Community Crate of the Week

This week's Crate of the Week is trust, a Travis CI and AppVeyor template to test your Rust crate on 5 architectures and publish binary releases of it for Linux, macOS and Windows. Thanks to Vikrant for the suggestion!

Submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from Rust Core

112 pull requests were merged in the last week. This contains a good number of plugin-breaking changes.

New Contributors
  • derekdreery
  • F001
  • Kyle Aleshire
  • Mina Naguib
  • Yamakaky
Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

Final Comment Period

Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are:

New RFCs Style RFCs

Style RFCs are part of the process for deciding on style guidelines for the Rust community and defaults for Rustfmt. The process is similar to the RFC process, but we try to reach rough consensus on issues (including a final comment period) before progressing to PRs. Just like the RFC process, all users are welcome to comment and submit RFCs. If you want to help decide what Rust code should look like, come get involved!

Ready for PR:

There's a lot of them right now, contributions here would be very welcome. If you want advice or help getting started, please ping nrc, or any other member of the style team, in #rust-style.

Issues in final comment period:

Upcoming Events

If you are running a Rust event please add it to the calendar to get it mentioned here. Email the Rust Community Team for access.

fn work(on: RustProject) -> Money

Tweet us at @ThisWeekInRust to get your job offers listed here!

Quote of the Week

This is the first version to have Rust code in it. The public API remains unchanged. Apologies in advance to distros who will have to adjust their build systems for Rust - it's like taking a one-time vaccine; you'll be better off in the end for it.

Federico Mena Quintero announcing librsvg 2.41.0.

Thanks to Zbigniew Siciarz for the suggestion.

Submit your quotes for next week!

This Week in Rust is edited by: nasa42, llogiq, and brson.

Categorieën: Mozilla-nl planet

James Long: A Prettier JavaScript Formatter

Mozilla planet - ti, 10/01/2017 - 01:00

Today I am announcing prettier, a JavaScript formatter inspired by refmt with advanced support for language features from ES2017, JSX, and Flow. Prettier gets rid of all original styling and guarantees consistency by parsing JavaScript into an AST and pretty-printing the AST. Unlike eslint, there aren't a million configuration options and rules. But more importantly: everything is fixable. I'm excited to have time for my own open-source work now that I've left Mozilla, so this is my way of kicking off 2017.

Here's a live demo. Note the JSX and Flow support. You can type anything into the editor below and it will format it automatically. The maximum line length here is 60. The top editor is the raw source and the bottom is the formatted version.

(The above demo is running with prettier version )

Many of you know that I usually don't use JSX when writing React code. Over a month ago I wanted to try it out, and I realized one of the things holding me back was poor JSX support in Emacs. Emacs has great support for automatically indenting code; I never manually indent anything. But this doesn't work with JSX, and when I looked around at other editors, I found similar problems (other editors are generally worse at forcing correct indentation).

Around the same time I had been using Reason which provides a refmt tool which automatically formats code. I was hooked. It removes all the distractions of writing code; you can write it however you like and instantly format it correctly. I realized this would not only solve my JSX problem, but provide a tool for enforcing consistent styles across teams no matter what editor is used.

If computers are good at anything, they are good at parsing code and analyzing it. So I set out to make this work, and prettier was born. I didn't want to start from scratch, so it's a fork of recast's printer with the internals rewritten to use Wadler's algorithm from "A prettier printer".

Why did I choose this algorithm? First lets look at why none of the existing style tools really work.

There's an extremely important piece missing from existing styling tools: the maximum line length. Sure, you can tell eslint to warn you when you have a line that's too long, but that's an after-thought (eslint never knows how to fix it). The maximum line length is a critical piece the formatter needs for laying out and wrapping code.

For example, take the following code:

foo(arg1, arg2, arg3);

That looks like the right way to format it. However, we've all run into this situation:

foo(reallyLongArg(), omgSoManyParameters(), IShouldRefactorThis(), isThereSeriouslyAnotherOne());

Suddenly our previous format for calling function breaks down because this is too long. What you would probably do is this instead:

foo( reallyLongArg(), omgSoManyParameters(), IShouldRefactorThis(), isThereSeriouslyAnotherOne() );

This clearly shows that the maximum line length has a direct impact on the style of code we desire. The fact that current style tools ignore this means they can't really help with the situations that are actually the most troublesome. Individuals on teams will all format these differently according to their own rules and we lose the consistency we sought after.

Wadler's algorithm described in the paper is a simple constraint-based layout system for code. It "measures" code and will break it across lines if it cross the maximum line width.

Even if we disregard line widths, it's too easy to sneak in various styles of code in all other linters. The most strict linter I know happily lets all these styles happen:

foo({ num: 3 }, 1, 2) foo( { num: 3 }, 1, 2) foo( { num: 3 }, 1, 2 )

Prettier bans all custom styling by parsing it away and re-printing the parsed AST with its own rules that take the maximum line width into account, wrapping code when necessary.

Respecting Patterns

A lot of work has been put into making prettier actually viable. The output is already very good, and I'm sure there are more tweaks we can make to make everyone happy.

We make sure to tailor code to specific patterns. For example, this is a popular style in JavaScript:

myPromise .then(() => { // ... }) .then(() => { // ... }) .catch(() => { // .. });

A naive printer would collapse it into something like this:

myPromise.then(() => { // ... }).then(() => { // ... }).catch(() => { // .. });

However, we detect this "chaining" pattern and specifically output the original code where each .then is on its own line.

If you are using a pattern that prettier does not format well, please open an issue and we can talk about ways to detect this and specialize it for your case.

Frictionless Teams

When working in a team, reducing friction is important. This is especially true on large teams. While it's impossible to avoid friction entirely, the more we can leverage tools to make it easier to work together the better.

You might think configuring eslint doesn't take much time, or that teams won't spend much time arguing about syntax. In my experience, that's not true. Even if you've configured eslint out the wazoo, it doesn't actually catch a whole range of style differences. Teams still struggle to enforce a consistent style and it's a big distraction.

The minutiae of syntax does not matter. Let it go. Let a tool like prettier just do it's job and focus on the real problems.


It turns out that a tool like prettier actually makes it easier to write code however you want, because you can instantly format it correctly afterwards!

Don't care about writing semicolons? Sure! Go ahead and write this:

function foo() { var x = 5 var y = 6 var z = 7 return x + y + z }

Paste that into the demo at the top and you'll see prettier happily inserts the semicolons for you.

Working on a really complex problem and just want to focus on writing some dirty code? Sure! Put it all on one line. Indulge yourself in dirty syntax. Formatting it correctly is just one keystroke away.

Check out prettier!

Thanks to:

  • Christopher Chedeau for pushing me to make this actually viable and setting up the Jest test suite
  • Pieter Vanderwerff for discussing solutions as he works on a similar project
  • Jordan Walke for writing refmt in the first place and inspiring this

Categorieën: Mozilla-nl planet

Christian Heilmann: 7 tricks to have very successful conference calls

Mozilla planet - ti, 10/01/2017 - 00:07

Conference Call

I work remotely and with a team eight hours away from me. Many will be in the same boat, and often the problem with this is that your meetings are late at night your time, but early for the others. Furthermore, the other team meets in a room early in the morning. This either means that they are fresh and bushy tailed or annoyed after having been stuck in traffic. Many different moods and agendas at play here. To avoid this being a frustrating experience, here are seven tips any team in the same situation should follow to ensure that everyone involved gets the most out of the conference call:

  • Be on time and stick to the duration – keep it professional – of course things go wrong, but there is no joy in being in a hotel room at 11pm listening to 6 people tell each other that others are still coming as they are “getting a quick coffee first”. It’s rude to waste people’s time. The meeting time should be information and chats that apply to all, regardless of location and time. You can of course add a social part before or after the meeting for the locals.
  • Have a meeting agenda and stick to it – that way people who have a hard time being part of the meeting due to time difference can decline to come to the meeting and this may make it shorter
  • Have the agenda editable to everyone available during the meeting – this way people can edit and note down things that have been said. This is beneficial as it acts as a script for those who couldn’t attend and it also means that you can ensure people remotely on the call are on the ball and not watching TV
  • Introduce yourself when you speak and go close to the mic – for people dialing in, this is a feature of the conference call software, but when 10 people in a room speak, remote employees who dialed in have no no idea what’s going on.
  • Avoid unnecessary sounds – as someone dialing in, mute your microphone. Nobody needs your coughing, coffee sipping, or – at worst – typing sounds – on the conference call. As someone in the room, don’t have conversations with others next to the microphone. Give the current presenters the stage they deserve.
  • Have a chat window open – this allows people to post extra info or give updates when something goes wrong. It is frustrating to speak when nobody hears you and you can’t even tell them that it doesn’t work. A text chat next to the conf call hardly ever fails to work and is a good feedback mechanism
  • Distribute presenter materials before the call – often presenting a slide deck or web product over Skype or others fails for various reasons or people dialing in are on a very bad connection. If they have the slide deck locally, they can watch it without blurs and delays

Using these tricks you end up with a call that results in a documented agenda you can send to those who couldn’t attend. You can also have an archive of all your conf calls for reference later on. Of course, you could just record the sessions, but it is much more annoying to listen to a recording and it may be tough to even download them for remote attendees on bad connections. By separating the social part of the meeting from the official one you still have the joy of meeting in the mornings without annoying the people who can’t be part of it.

Photo Credit: quinn.anya Flickr cc

Categorieën: Mozilla-nl planet

Firefox 52: Mozilla entfernt Unterstützung für Adobe Primetime -

Nieuws verzameld via Google - mo, 09/01/2017 - 19:02

Firefox 52: Mozilla entfernt Unterstützung für Adobe Primetime
Firefox lädt seit Version 38 Adobe Primetime als Content Decryption Module für die Wiedergabe DRM-geschützter Inhalte im Web herunter. In Firefox 52 entfernt Mozilla die Unterstützung für Adobe Primetime. Für die Nutzung von Streaming-Plattformen wie ...

Categorieën: Mozilla-nl planet

Mozilla Calls for "Responsible IoT" - OStatic (blog)

Nieuws verzameld via Google - mo, 09/01/2017 - 17:18

Mozilla Calls for "Responsible IoT"
OStatic (blog)
As the Internet of Things (IoT) gains momentum, there is a need for collaboration, open and interoperable tools, and governance. In fact, all the way back in 2015, Philip DesAutels, the AllSeen Alliance's leader, told us that: “In five years, I think ...

en meer »
Categorieën: Mozilla-nl planet

Switching from Internet Explorer to Mozilla Firefox - Austin Monthly

Nieuws verzameld via Google - mo, 09/01/2017 - 16:35


Switching from Internet Explorer to Mozilla Firefox
Austin Monthly
So it is basic for some clients to search for a superior web program like Mozilla Firefox. On the off chance that you are looking for an approach to change from Internet Explore to Mozilla Firefox, you can either counsel the specialists of Internet ...
Google Chrome topples Internet Explorer as the most popular internet browser ...Financial Express

alle 8 nieuwsartikelen »
Categorieën: Mozilla-nl planet