Security/Anti tracking policy - MozillaWiki
This document describes the online tracking practices that Mozilla believes, as a matter of policy, should be blocked by default by web browsers. These practices are potentially harmful to users and cannot be meaningfully understood or controlled by users. We intend to implement technical protections in Firefox to block all tracking practices included in this policy. If we discover additional trac
Project Fission - MozillaWiki
Fission is Mozilla's implementation of Site Isolation in Firefox. Site Isolation is a security feature that offers additional protection in case of large classes of security bugs. Site Isolation safely sandboxes web pages and web frames, isolating them from each other, further strengthening Firefox security. Why? Web security is designed in such a way that websites or webframes cannot access each
Security/Tracking protection - MozillaWiki
Tracking Protection is a new platform-level technology that blocks HTTP loads at the network level. It is based on the Safe Browsing technology that powers our phishing and malware protection. This feature was part of the Polaris initiative. browser.contentblocking.enabled: master switch for all content blocking features (includes tracking protection, but excludes tracking annotations) browser.saf
Mozilla 2 - MozillaWiki
Project Status See the latest status meeting notes. Work List A detailed list of items that we are working on can be found here: Mozilla 2 Work List Ends Current thinking on goals, initially pitched in Brendan's Mozilla 2 blog item, consists of these major bullet items: Clean up our APIs to be fewer, better, and "on the outside" of Gecko, with symbol visibility strictly limited to public APIs. Bas
Services/Sync/Getting Started - MozillaWiki
Hacking Source Code Once you have a copy of the Mozilla source tree (read below for how to obtain a copy), you can find the core Sync source code in: /services/sync/ You can view this online at https://hg.mozilla.org/mozilla-unified/file/default/services/sync This is just the core JavaScript APIs and logic. Additional Sync code for integration with Firefox lives in: /browser/base/content Look for
ES6 plans - MozillaWiki
This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution. Visit SpiderMonkey.dev for more up to date information. New and improved builtin APIs Most of this stuff does not need to touch a lot of code. None of it requires a Harmony opt-in. This is great stuff for new contributors to start work on.
Servo/StyleUpdateOnDOMChange - MozillaWiki
Handling of style updates when the DOM changes In what cases are style updates needed? Throughout, we use the terms "selector" and "sequence of simple selectors" as defined in CSS3 Selectors. In addition, we use the term "subject sequence of simple selectors" to describe the sequence of simple selectors that must match elements that the full selector matches. In Selectors Level 3 this is the right
Security/Bug Approval Process - MozillaWiki
This page was last modified on 30 April 2020, at 11:37. Privacy policy About MozillaWiki Mobile view
Windows Service Silent Update - MozillaWiki
Overview Before this feature, when a user installs into the default Program Files directory, updates cannot be applied without us first prompting the user for elevated permissions with a User Account Control (UAC) dialog. Now that this feature is implemented, Firefox uses a service to execute updates so that UAC prompts are not displayed. The service is run "on demand" and will remain stopped unti
Labs/JS Modules - MozillaWiki
The modules described here have been superseded by the Addon-SDK. What is described on this page is now out of date. Here you'll find a collection of modules which you can import into your extension. The goal is to make extension development easier by implementing common functionality as reusable libraries. If you would like to contribute a new module, get in touch with us at #labs! Usage The modu
WebAppSec/Secure Coding Guidelines - MozillaWiki
Introduction The purpose of this page is to establish a concise and consistent approach to secure application development of Mozilla web applications and web services. The information provided here will be focused towards web based applications; however, the concepts can be universally applied to applications to implement sound security controls and design. This page will largely focus on secure g
Gecko:FullScreenAPI - MozillaWiki
Requirements Scripts should be able to initiate and terminate full-screen Allows custom, in-page, discoverable UI to active full-screen Arbitrary Web content should be visible full-screen <video>, <canvas>, multicolumn text, etc Required for scripted video controls Entering and exiting full-screen must trigger events To allow scripted changes to content, e.g. resizing of canvas content Scripts sho
Labs/Jetpack/Reboot/Style Guide - MozillaWiki
Code style bikeshedding is great, let's do it, here we go. From bug 541622: > Looks like we are using javadoc/jsdoc style comments to document functions. Oh, meant to mention that. I'm more concerned about documenting functions in the first place than the style we use to do it. Javadoc is definitely widely used in Mozilla for both C++ and JS, so considering that one day other people will be mainta
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Security/Fusion - MozillaWiki
FxSiteCompat - MozillaWiki
Jetpack/Release Notes/1.0 - MozillaWiki
Remote Debugging Protocol - MozillaWiki
Features/Platform - MozillaWiki
Debugger - MozillaWiki
Platform/Memory Reporting - MozillaWiki