From a065e04d529da1d847b5062a12c46d916408bf32 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 21:46:22 -0500 Subject: update based on https://github.com/mdn/yari/issues/2028 --- .../b2g_os/b2g_desktop_client_gebruiken/index.html | 216 ----- .../building_and_installing_firefox_os/index.html | 60 -- .../b2g_os/gebruik_van_de_app_manager/index.html | 239 ----- files/nl/archive/b2g_os/index.html | 234 ----- files/nl/archive/b2g_os/introduction/index.html | 85 -- files/nl/archive/b2g_os/quickstart/index.html | 49 -- .../b2g_os/quickstart/je_eerste_app/index.html | 205 ----- files/nl/archive/b2g_os/simulator/index.html | 246 ------ files/nl/archive/css3/index.html | 976 --------------------- files/nl/archive/index.html | 20 - .../examples/alternate_license_block/index.html | 16 - files/nl/archive/meta_docs/examples/index.html | 17 - files/nl/archive/meta_docs/index.html | 12 - .../mdn_content_on_webplatform.org/index.html | 21 - files/nl/archive/mozilla/index.html | 223 ----- .../xul/how_to_quit_a_xul_application/index.html | 38 - files/nl/archive/mozilla/xul/index.html | 79 -- files/nl/archive/themes/index.html | 11 - files/nl/archive/web/index.html | 81 -- .../ecmascript_7_support_in_mozilla/index.html | 72 -- files/nl/archive/web/javascript/index.html | 12 - 21 files changed, 2912 deletions(-) delete mode 100644 files/nl/archive/b2g_os/b2g_desktop_client_gebruiken/index.html delete mode 100644 files/nl/archive/b2g_os/building_and_installing_firefox_os/index.html delete mode 100644 files/nl/archive/b2g_os/gebruik_van_de_app_manager/index.html delete mode 100644 files/nl/archive/b2g_os/index.html delete mode 100644 files/nl/archive/b2g_os/introduction/index.html delete mode 100644 files/nl/archive/b2g_os/quickstart/index.html delete mode 100644 files/nl/archive/b2g_os/quickstart/je_eerste_app/index.html delete mode 100644 files/nl/archive/b2g_os/simulator/index.html delete mode 100644 files/nl/archive/css3/index.html delete mode 100644 files/nl/archive/index.html delete mode 100644 files/nl/archive/meta_docs/examples/alternate_license_block/index.html delete mode 100644 files/nl/archive/meta_docs/examples/index.html delete mode 100644 files/nl/archive/meta_docs/index.html delete mode 100644 files/nl/archive/meta_docs/mdn_content_on_webplatform.org/index.html delete mode 100644 files/nl/archive/mozilla/index.html delete mode 100644 files/nl/archive/mozilla/xul/how_to_quit_a_xul_application/index.html delete mode 100644 files/nl/archive/mozilla/xul/index.html delete mode 100644 files/nl/archive/themes/index.html delete mode 100644 files/nl/archive/web/index.html delete mode 100644 files/nl/archive/web/javascript/ecmascript_7_support_in_mozilla/index.html delete mode 100644 files/nl/archive/web/javascript/index.html (limited to 'files/nl/archive') diff --git a/files/nl/archive/b2g_os/b2g_desktop_client_gebruiken/index.html b/files/nl/archive/b2g_os/b2g_desktop_client_gebruiken/index.html deleted file mode 100644 index 11b2e965d9..0000000000 --- a/files/nl/archive/b2g_os/b2g_desktop_client_gebruiken/index.html +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: De B2G OS-simulator bouwen -slug: Archive/B2G_OS/B2G_desktop_client_gebruiken -tags: - - B2G OS - - Device - - Firefox OS - - Gaia - - Mobile - - simulator -translation_of: Archive/B2G_OS/Building_the_B2G_OS_simulator ---- -

Met de Firefox OS desktop client, ook wel de B2G desktop client genoemd,  kunt u Gaia en Web apps in een Gecko-gebaseerde omgeving wat lijkt op een echt apperaat. It doesn't emulate device hardware, so it's not adequate for testing device APIs, and isn't a replacement for testing on actual hardware. However, it does have a several APIs enabled that aren't available on Firefox such as the Contacts and Settings APIs. It can therefore be useful during the development of your application, or while working on the Gaia user interface itself.

- -

This article covers downloading or building the Firefox OS desktop client, as well as how to use it.

- -
-

Note: The easiest way to use the Firefox OS desktop client is to use the Firefox OS Simulator. It does not require you to build the desktop client yourself.

-
- -

Download a nightly build

- -
-

Note: Firefox OS version 1.0 is based on a branch of Gecko 18. There are also nightly builds based on mozilla-central here:
- http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/

-
- -

Just like Firefox Nightlies, the Firefox OS desktop client is built every day from the latest source code. The latest build is available from the Mozilla FTP server. Be sure to pick the latest version and the right archive for your operating system. This lets you bypass having to build it yourself. In addition, you don't have to download Gaia on your own either.

- -

Be sure to install the application in a writeable location; the application needs to be able to update included the Gaia profile.

- -

You can now skip ahead to Running the desktop client, unless you actually want to build it for yourself.

- -

Building the desktop client

- -

The first thing we need to do is set up a standard Mozilla build environment. Once we have that, we can pull down the code we'll need and configure to build the Firefox OS desktop client.

- -

Downloading the code for the first time

- -

In a directory where we'd like the source code to go, let's clone the mozilla-central repository that contains all of Gecko:

- -
 hg clone http://hg.mozilla.org/mozilla-central
-
- -

Updating the code

- -

When we do subsequent builds later, we'll want to make sure we have the latest code. Here's how to pull the latest changes:

- -
cd mozilla-central
-hg pull -u
-
- -

Create a mozconfig

- -

Next, we need to create a mozconfig file in the mozilla-central directory to configure the build system to build the Boot to Gecko client instead of Firefox:

- -
. "$topsrcdir/b2g/config/mozconfigs/common"
-
-mk_add_options MOZ_OBJDIR=../build
-mk_add_options MOZ_MAKE_FLAGS="-j9 -s"
-
-ac_add_options --enable-application=b2g
-ac_add_options --disable-libjpeg-turbo
-
-# This option is required if you want to be able to run Gaia's tests
-ac_add_options --enable-tests
-
-# turn on mozTelephony/mozSms interfaces
-# Only turn this line on if you actually have a dev phone
-# you want to forward to. If you get crashes at startup,
-# make sure this line is commented.
-#ac_add_options --enable-b2g-ril
- -

Building

- -

Now we're ready to build the desktop client with the following command issued from the mozilla-central directory:

- -
make -f client.mk
-
- -

The built client will be placed in the ../build/dist directory (based on the value you specify for MOZ_OBJDIR in the mozconfig file).

- -

Downloading Gaia

- -

By default the desktop client will show an empty screen because it doesn't know which Web app to load initially as the system app. The collection of system apps and default apps that come with Firefox OS is called Gaia.

- -

To download Gaia for the first time, let's clone the source code repository on GitHub:

- -
git clone https://github.com/mozilla-b2g/gaia
-cd gaia
- -

To update an already existing clone of Gaia, we can pull in the latest changes from GitHub:

- -
cd gaia
-git pull
-
- -

Generating a profile

- -

Next we need to set up Gaia's apps for the desktop client. This includes packaging the Gaia apps in the same way like they would be installed on the device, as well as setting up the permissions for the privileged system apps. We do this by generating a profile. The following command (run in the gaia directory) will take care of that:

- -
make
-
- -

This should create a profile directory below the gaia directory. The new profile contains a customized extension and other configuration needed to make B2G run properly.

- -

Running the desktop client

- -

Once you've built the client and downloaded Gaia (or downloaded and installed the nightly desktop application), you're ready to fire up the Firefox OS desktop client.

- -

Running on Linux

- -

To run the desktop client on Linux using the embedded Gaia profile, just run the b2g executable. If you want to specify a different Gaia profile, you need to bypass the b2g wrapper program and run the b2g-bin binary. The binary is in the archive you downloaded earlier or in the ../build/dist/bin directory if you built the client yourself.

- -
.../b2g-bin -profile gaia/profile
-
- -

You may experience annoying rendering problems. To avoid them, add the following line to your gaia/profile/user.js file:

- -
user_pref("layers.acceleration.disabled", true);
-
- -

Running on Mac

- -

If you downloaded the nightly build, you can simply launch it from the Finder as usual. Any console output is visible by running the standard Console utility program included with your Mac.

- -

If you want to specify a different Gaia profile, you need to bypass the b2g wrapper program and run the b2g-bin binary. The command line is slightly more complicated due to the location of the b2g-bin binary and the need for absolute paths when specifying the profile directory:

- -
.../B2G.app/Contents/MacOS/b2g-bin -profile /full/path/to/gaia/profile
-
- -

Running on Windows

- -

Running the nightly build on Windows is as simple as launching b2g.exe. If you want to customize the execution, you can do so by running the b2g-bin.exe executable instead; this bypasses the wrapper program that automatically uses the bundled Gaia.

- -

Command line options

- -

There are a number of command line options you can use to adjust the runtime experience while using the desktop client. You can get a list by using the -help option. This section covers some of the particularly interesting ones.

- -

Specifying the screen size

- -

You can specify the screen size of the device you want to simulate using the --screen option:

- -
b2g --screen=<width>x<height>[@<dpi>]
- -

Where <width>, <height>, and <dpi> are fairly self-explanatory parameters: the width and height of the device's screen in pixels and the device resolution in DPI. For example:

- -
b2g --screen=320x480
-b2g --screen=320x480@160
-
- -

Optionally, you can specify certain devices by name to simulate their screen size and resolution:

- - - -

Opening the JavaScript console

- -

You can open the JavaScript console when launching the desktop B2G client by launching it from the command line with the -jsconsole flag. After building, just do:

- -
.../b2g -jsconsole -profile /path/to/your/profile
- -

If you've installed the nightly build on a Mac, you can do the following:

- -
/Applications/B2G.app/Contents/MacOS/b2g-bin -jsconsole -profile /path/to/your/profile
- -
-

Note: On production builds of Firefox OS, console logging (such as by {{domxref("console.log()")}}) is disabled by default. In order to enable it, open the Settings app and navigate down through Device Information->More Information->Developer, then toggle on the "Console Enabled" preference.

-
- -

Launching a specific application at startup

- -

You can now specify an application to be launched automatically when b2g starts up in the desktop client. This is done as soon as the rest of the system is done loading up. To do this, just use the --runapp option, which takes as a parameter the name of the application to run. For example:

- -
 .../b2g-bin -profile /path/to/your/gaia/profile --runapp email
- -

Before looking for an app to launch, the specified name is normalized by converting it to all lower case and removing all dashes and spaces. This normalized name is then compared to similarly normalized names from the manifests of available apps' manifests.

- -

For example, the name of the email app is currently "E-mail", but --runapp email will work because of this normalization.

- -

If you specify the --runapp option without an argument, or with an empty argument, the b2g client will output to your terminal a list of the known applications as well as a brief usage message.

- -
-

Note: Using the --runapp option disables the lock screen as a side effect and does not re-enable it. It's assumed that you won't use this command on a profile on which you will be testing the lock screen, or you will turn it back on manually in Settings application. Feel free to contribute a patch to change this behavior if it's a problem.

-
- -

Usage tips

- -

This section provides a few helpful tips to using the B2G desktop client.

- - - -

Next steps

- -

Now that you have a desktop build of Boot to Gecko running, you can do testing, development, and other work in it:

- - diff --git a/files/nl/archive/b2g_os/building_and_installing_firefox_os/index.html b/files/nl/archive/b2g_os/building_and_installing_firefox_os/index.html deleted file mode 100644 index 98220c79c8..0000000000 --- a/files/nl/archive/b2g_os/building_and_installing_firefox_os/index.html +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Het compileren en installeren van Firefox OS -slug: Archive/B2G_OS/Building_and_installing_Firefox_OS -translation_of: Archive/B2G_OS/Building_and_installing_B2G_OS ---- -

Omdat Firefox OS op dit moment aan hevige ontwikkelingen onderhevig is en zich in een pre-release fase bevindt, is de best mogelijke manier om er zeker van te zijn een up-to-date versie van het OS te draaien het zelf compileren en installeren van een image. De artikelen welke hieronder zijn verzameld zullen een complete handleiding zijn tijdens het proces van compileren en installeren van Firefox OS in een emulator danwel op een ondersteund apparaat, of bij het installeren van de Gaia gebruiksinterface in de Firefox-browser.

- - - - - - - -
-

het verkrijgen en compileren van FIREFOX OS

-
-
- Firefox OS compilatiebenodigdheden
-
- Wat heb je nodig (en wat moet je doen) om voor de eerste keer een Firefox OS image te compileren.
-
- Voorbereiden op het bouwen van de eerste image
-
- Alvorens je de eerste image kunt bouwen, moet je de de repository clonen en de bestanden configureren. Dit artikel kan hierbij van hulp zijn.
-
- Het compileren van Firefox OS
-
- Hoe moet je Firefox OS compileren.
-
-

Alle bekijken...

- 		-

Installing FIREFOX OS and/or Gaia

-
-
- Choosing how to run Gaia or Firefox OS
-
- You can use Gaia within Firefox, or you can run Firefox OS on a mobile device or in a desktop-based simulator. This guide will help you decide which is best for your needs.
-
- Using Gaia in Firefox
-
- How to use Gaia within a desktop Firefox browser.
-
- Using the Firefox OS desktop client
-
- A guide to running and using the Firefox OS desktop client; this simulates the Gaia environment in a desktop application. It's more accurate than running Gaia in Firefox but not as accurate as the emulators.
-
- Using the Firefox OS emulators
-
- A guide to building and using the Firefox OS emulators, and when to use which emulator.
-
- Installing Firefox OS on a mobile device
-
- How to install Firefox OS on a real mobile device.
-
- Dual boot of Firefox OS and Android on SGS2
-
- How to set up a Firefox OS/Android dual boot environment on a Samsung Galaxy S2.
-
-
-

 

diff --git a/files/nl/archive/b2g_os/gebruik_van_de_app_manager/index.html b/files/nl/archive/b2g_os/gebruik_van_de_app_manager/index.html deleted file mode 100644 index 2162bdecf1..0000000000 --- a/files/nl/archive/b2g_os/gebruik_van_de_app_manager/index.html +++ /dev/null @@ -1,239 +0,0 @@ ---- -title: Gebruik van de App Manager -slug: Archive/B2G_OS/Gebruik_van_de_App_Manager -translation_of: Archive/B2G_OS/Using_the_App_Manager ---- -
 
- -
 
- -
-

De App Manager is een nieuwe tool beschikbaar voor Firefox op de desktop welke een aantal handige funcionaliteiten biedt voor het helpen met testen, uitvoeren en testen van HTML5 web applicaties op het Firefox OS telefoons en Firefox OS simulator, direct vanuit de browser.

-
- -

{{EmbedYouTube("z1Bxg1UJVf0")}}

- -

De App Manager bestaat uit:

- - - -

Snelle setup:

- -

This section is designed to get you up and running as soon as possible; if you need some more detail please skip forward to the {{ anch("Device and system configuration") }} section and start reading from there.  Also see the {{ anch("Troubleshooting") }} section for help if you are having trouble.

- -
    -
  1. Make sure you have Firefox Desktop 26+ installed
    2. -
  2. Open the App Manager (in the URL bar, type about:app-manager)
    3. -
  3. If you don't have a real device: -
      -
    1. Install the Firefox OS Simulator
      2. -
    2. In App Manager's bottom toolbar, click on Start Simulator, then click on the name of the installed simulator, which should appear there.
      3. -
    -
    4. -
  4. If you have a real device: -
      -
    1. Make sure your device is running Firefox OS 1.2+
      2. -
    2. In the Settings of your device, disable Screen Lock (Settings > Screen Lock) and enable Remote Debugging (Settings > Device information > More information > Developer)
      3. -
    3. Install the ADB Helper add-on in Firefox Desktop
      4. -
    4. Connect your device to your machine via a USB cable
      5. -
    5. You should see the name of your device in the App Manager's bottom bar. Click on it.
      6. -
    -
    5. -
  5. The bottom bar should show "Connected to: xxx"
    6. -
  6. Click on the Apps panel and add an app (packaged or hosted)
    7. -
  7. The Refresh button validates your app and installs it on the Simulator/Device
    8. -
  8. The Debug button connects the developer tools to the running app
    9. -
- -

Device and system configuration

- -

The first thing you'll need to do when using the App Manager is make sure your system and phone are set up correctly. This section will run thrugh all the steps required.

- -

Firefox 1.2+ required

- -

Make sure your device is running Firefox OS 1.2/Boot2Gecko 1.2 or higher. To check which version of Firefox OS the device is runing, go to Settings > Device Information > Software.

- -

If you don't have a high enough version installed, depending on what phone you have you will need to either install an available nightly build of Firefox 1.2+, or configure and build it yourself from source.

- -

Builds available:

- - - -

To build your own Firefox OS 1.2+ distribution, follow the instructions located at Building and installing Firefox OS, starting with Firefox OS build prerequisites.

- -

Remote debugging

- -

Next, you need to enable remote debugging in Firefox OS. To do so, go to Settings > Device information > More information > Developer and check the Remote Debugging checkbox.

- -

ADB or ADB helper

- -

The process uses the Android Debug Bridge (ADB) to handle the device-computer connection and communication. There are two options for running ADB:

- - - -
-

Note: There's no need to run this command if you installed the ADB Helper Add-on.

-
- -

Connecting your device to the App Manager

- -

With all your configuration done, it's now time to plug your device into your computer and start the App Manager:

- -
    -
  1. Plug the device into your computer via USB.
    2. -
  2. Disable Screen lock on your device by going to Settings > Screen Lock and unchecking the Lock Screen checkbox. This is a good idea because when the screen gets locked, the phone connection gets lost, meaning it is no longer available for debugging.
    3. -
  3. Start the App Manager — In Firefox Desktop select the Tools > Web Developer > App Manager menu option, or type about:app-manager in the URL bar.
    4. -
  4. At the bottom of the App Manager tab, you will see a connection status bar (see screenshot below). You should be able to connect your device by clicking the "Connect to localhost:6000" button.
    5. -
  5. If this works successfully, a prompt should appear on your device: "An incoming request to permit remote debugging connection was detected. Allow connection?". Tap the OK button (You may also have to press the power button on the phone so you can see the prompt.) The connection status bar should update to say "Connected to B2G", with a Disconnect button available to press if you want to cancel the connection.
    6. -
- -

- -
-

Note that the other controls in the connection status bar allow you to connect a simulator to the App Manager, which we cover in the next section, below, and change the port that the connection happens on. If you change the port, you'll also need to enable port forwarding for this port as well, as instructed in the {{anch("Enable port forwarding")}} section, above.

-
- -

Using a Firefox OS Simulator Add-on

- -

If you haven't got a real device available to use with App Manager, you can still try it out using a Firefox OS Simulator Add-on. To start off, install the appropriate simulator for your operating system:

- -

Install Simulator

- -
-

Note that currently there is only a Firefox OS 1.2 simulator available, although more may appear in the future.

-
- -

Once you've installed the simulator, you need to go to the connection status bar at the bottom of the App Manager tab, and click the "Start simulator" button. Three buttons will appear:

- - - -

Apps panel

- -

Now everything is working, let's review the functionality available inside the App Manager, starting with the Apps Panel. From here, you can import an existing app to push onto your device and debug:

- - - -

Information about your app should appear on the right hand side of the window, as seen below:

- -

- -

Clicking on "Update" will update (install) the app on the device. Clicking on "debug" will connect a toolbox to the app, allowing you to debug its code directly:

- -

- -
-

Note: You'll enjoy playing around with the toolbox — try altering the DOM, CSS etc. and you'll see the updates reflected on the device in realtime. Such updates will be saved on the installed app code; you'll see them next time you open the app on the device.

-
- -

If an app was not added successfully — for example if the URL was incorrect, or you selected a packaged app folder — an entry will be added to the page for this app, but this will include error information.

- -

- -

You can also delete an app from this view, by hovering over the App name/description on the left of the window, and pressing the "X" button that appears in each case. This however doesn't remove the app from the device. To do that you need to manually remove the app using the device itself.

- -

Device panel

- -

The Device tab displays information about the connected device. From the "Installed Apps" window, apps on the device can be started and debugged.

- -

- -
-

Note: Certified Apps are not listed by default. See how to debug certified apps.

-
- -

The "Permissions" window shows the required priviledges for different Web APIs on the current device:

- -

- -

Finally, you can take a screenshot of the current device display by clicking the "Screenshot" button. The screenshot appears in a new tab on Firefox, and from there you can save or discard it as you wish.

- -

Debugging Certified Apps

- -

Currently only devices running a development build of Firefox OS 1.2 are capable of debugging certified apps. If you have a development build, you can enable certified app debugging by changing the pref devtools.debugger.forbid-certified-apps to false in your profile. To do this, follow the steps below:

- -
    -
  1. -

    On your computer, enter the following command in Terminal/console to enter your device's filesystem via the shell:

    - - 
    adb shell
    - -

    Your prompt should change to root@android.

    -
    2. -
  2. -

    Next, stop B2G running using the following command:

    - - 
    stop b2g
    -
    3. -
  3. -

    Navigate to the following directory:

    - - 
    cd /data/b2g/mozilla/*.default/
    -
    4. -
  4. -

    Here, update the prefs.js file with the following line:

    - - 
    echo 'user_pref("devtools.debugger.forbid-certified-apps", false);' >> prefs.js
    -
    5. -
  5. -

    After you've finished editing and saving the file, start B2G again using the following command:

    - - 
    start b2g
    -
    6. -
  6. -

    Exit the android filesystem using the exit command; this will return you to your normal terminal prompt.

    -
    7. -
  7. -

    Next, reconnect to the App Manager and you should see certified apps appear for debugging.

    -
    8. -
- -
-

Note: If you want to add this preference to your Gaia build you can run make DEVICE_DEBUG=1 reset-gaia.

-
- -

Troubleshooting

- -

If the device is not recognized:

- - - -

Can't connect your device to the App Manager or start the simulator? Let us know or file a bug.

- -
 
diff --git a/files/nl/archive/b2g_os/index.html b/files/nl/archive/b2g_os/index.html deleted file mode 100644 index 69f87d5aa0..0000000000 --- a/files/nl/archive/b2g_os/index.html +++ /dev/null @@ -1,234 +0,0 @@ ---- -title: B2G OS -slug: Archive/B2G_OS -tags: - - B2G - - Basic - - Beginner - - Firefox OS - - Firefox OS starten - - Gaia - - Overzicht -translation_of: Archive/B2G_OS ---- -
-

Firefox OS is the mobile operating system developed by Mozilla, based on Linux and Firefox's powerful Gecko rendering engine.

-
- -

Firefox OS is open source software that allows developers to harness the power and flexibility of the Web to create advanced end-user applications. The entire user interface is a web app, which can display and launch other apps. A Firefox OS web app is made with HTML, CSS, and JavaScript. In addition, Firefox OS web apps have access to the device hardware and services via an Application Programing Interface (API).

- -

From a product perspective, Firefox OS is Mozilla's (and our OEM partners') branding and support services applied on top of Boot to Gecko (B2G), which is the operating system's engineering codename. Boot to Gecko is developed by a team of engineers inside Mozilla plus many external contributors from the wider Mozilla/open source community.

- -
-

Develop apps for Firefox OS

- -

Head over to our App Center for all the information you could possibly need on building open web apps that can be installed on Firefox OS !

-
- -
-
-

Platform guides

- -

Guides for platform developers on how the different components of the Firefox OS platform fit together and work.

- - -
- -
-

Build & install

- -

Guides covering building and installing Firefox OS on an emulator, compatible device, or desktop simulator.

- - -
- -
-

Developer phones

- -

Information on specific developer phones, such as tweaking, updating, recovering, and  buying.

- - -
-
- -
-
-

Get started with Firefox OS add-ons

- -

Firefox OS add-ons are new in Firefox OS 2.5! To start developing add-ons and getting involved in the add-ons community, read Getting started with Firefox OS add-ons.

-
- -
-

Other useful pages

- - -
-
- -
-

Note: We are keeping track of ongoing work on Firefox OS documentation on our Firefox OS documentation status page. If you want to help contribute to Firefox OS documentation, please have a look at this page to see what work needs tweaking!

-
- - - -
    -
  1. Introduction
    2. -
  2. Platform guide -
      -
    1. Platform guide overview
      2. -
    2. Architecture overview
      3. -
    3. Apps architecture
      4. -
    4. Gonk
      5. -
    5. Gecko
      6. -
    6. Gaia
      7. -
    7. Gaia apps guide
      8. -
    8. Security -
        -
      1. The Firefox OS security model
        2. -
      2. System security
        3. -
      3. Application security in Firefox OS
        4. -
      4. Securely installing and updating applications
        5. -
      -
      9. -
    9. Out of memory management on Firefox OS
      10. -
    10. Feature support chart
      11. -
    11. Settings list
      12. -
    -
    3. -
  3. Build and install -
      -
    1. Build and install overview
      2. -
    2. Firefox OS build process summary
      3. -
    3. Build prerequisites
      4. -
    4. Preparing for your first build
      5. -
    5. Building Firefox OS
      6. -
    6. Building Firefox OS for flame on OSX
      7. -
    7. Choosing how to run Gaia or Firefox OS
      8. -
    8. Building the Firefox OS simulator
      9. -
    9. Using the Firefox OS emulators
      10. -
    10. Installing Firefox OS on a mobile device
      11. -
    11. Creating and applying Firefox OS update packages
      12. -
    12. Building and installing FOTA community builds
      13. -
    13. B2G build variables reference sheet
      14. -
    -
    4. -
  4. Developing Firefox OS -
      -
    1. Developing Firefox OS overview
      2. -
    2. Filing bugs against Firefox OS
      3. -
    3. Modifying the hosts file
      4. -
    4. Customization with the .userconfig file
      5. -
    5. Customizing the b2g.sh script
      6. -
    6. Porting Firefox OS
      7. -
    -
    5. -
  5. Developing Gaia -
      -
    1. Developing Gaia overview
      2. -
    2. Running the Gaia codebase
      3. -
    3. Understanding the Gaia codebase
      4. -
    4. Making Gaia code changes
      5. -
    5. Testing Gaia code changes
      6. -
    6. Submitting a Gaia patch
      7. -
    7. Gaia build system primer
      8. -
    8. Customizing build-time apps
      9. -
    9. Market customizations guide
      10. -
    10. Customizing the keyboard in Firefox OS apps
      11. -
    11. Localizing Firefox OS
      12. -
    12. L10n Best Practices
      13. -
    13. Make options reference
      14. -
    14. Gaia tools reference
      15. -
    -
    6. -
  6. Firefox OS add-ons
    7. -
  7. Firefox OS phone guide -
      -
    1. Firefox OS phone guide overview
      2. -
    2. Phone and device specs
      3. -
    3. Geeksphone
      4. -
    4. ZTE OPEN
      5. -
    5. ZTE OPEN C
      6. -
    6. Flame
      7. -
    7. General device features
      8. -
    8. Troubleshooting
      9. -
    9. Best practices for open reference devices
      10. -
    -
    8. -
  8. Firefox OS on TVs and connected devices -
      -
    1. TVs and connected devices overview
      2. -
    2. How to get started with TV apps development
      3. -
    3. How to connect WebIDE to TV (VIERA CX/CR series)
      4. -
    4. TV broadcast streams on Firefox OS products
      5. -
    5. Web animations on large screens
      6. -
    6. Implementing TV remote control navigation
      7. -
    7. Firefox OS for TV UX Overview
      8. -
    -
    9. -
  9. Firefox OS release notes -
      -
    1. Firefox OS release notes overview
      2. -
    2. Firefox OS 2.2 for developers
      3. -
    3. Firefox OS 2.1 for developers
      4. -
    4. Firefox OS 2.0 for developers
      5. -
    5. Firefox OS 1.4 for developers
      6. -
    6. Firefox OS 1.3 for developers
      7. -
    7. Firefox OS 1.2 for developers
      8. -
    8. Firefox OS 1.1 for developers
      9. -
    9. Firefox OS 1.0.1 for developers
      10. -
    -
    10. -
  10. Automated testing -
      -
    1. Firefox OS automated testing overview
      2. -
    2. Running tests on Firefox OS: A guide for developers
      3. -
    3. Gaia UI tests
      4. -
    4. Gaia integration tests
      5. -
    5. Gaia unit tests
      6. -
    6. Gaia performance tests
      7. -
    7. Mochitests
      8. -
    8. Reftests
      9. -
    9. WebAPI tests
      10. -
    10. xpcshell tests
      11. -
    11. MTBF test
      12. -
    12. Marionette
      13. -
    13. Treeherder
      14. -
    -
    11. -
  11. Debugging -
      -
    1. Firefox OS debugging overview
      2. -
    2. Developer settings for Firefox OS
      3. -
    3. Connecting a Firefox OS device to the desktop
      4. -
    4. Setting up to debug Firefox OS using Firefox developer tools
      5. -
    5. On-device console logging
      6. -
    6. Installing and using ADB
      7. -
    7. Taking screenshots
      8. -
    8. Using the WebIDE
      9. -
    9. Firefox OS crash reporting
      10. -
    10. Debugging out of memory errors on Firefox OS
      11. -
    11. Debugging and security testing with Firefox OS
      12. -
    12. Debugging B2G using gdb
      13. -
    13. Debugging B2G using Valgrind
      14. -
    -
    12. -
diff --git a/files/nl/archive/b2g_os/introduction/index.html b/files/nl/archive/b2g_os/introduction/index.html deleted file mode 100644 index 14a29acf84..0000000000 --- a/files/nl/archive/b2g_os/introduction/index.html +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Introductie Firefox OS -slug: Archive/B2G_OS/Introduction -translation_of: Archive/B2G_OS/Introduction ---- -

Firefox OS (ook wel bij zijn  codename "Boot to Gecko" or "B2G" genoemd) is Mozilla's mobile openbron besturings systeem gebaseerd op Linux en Mozilla's Gecko technologie. Firefox OS is een mobiel besturings systeem dat vrij is van eigen technologie. Terwijl het toch nog steeds een platform aan applicatieontwerpers biedt die daardoor uitstekende produkten kan ontwikkelen. Bovendien is het sterk en draagbaar genoeg om de eindgebruiker tevreden te stellen.

-

Voor Web ontwerpers, het belangrijkste om te onthouden is dat de hele user interface een Web app is, een die in staat is om andere Web apps te laten starten en draaien. Elke verandering die je aan de user interface en de aan de applicaties doet, dan creeer je in feite een soort van run van webpagina`s op  Firefox OS, Zei het met een verbeterde toegang tot de hardware en functies van het mobiele apparaat.

-

In onze handige gids leer je hoe Firefox OS moet bouwen en instaleren.

-

Hardware eisen

-

De meeste ARM-based mobiele apparaten zijn sterk genoeg om te kunnen dokken met Firefox OS. Dit gedeelt is genoeg om aan zowel aan de basis hardware eisen te voldoen, als zowel aan de hardware minimale toekomstige eisen.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OnderdeelMinimumAanbevolen
CPUARMv6Cortex A5 klasse of hoger
- ARMv7a met NEON
GPU—Adreno 200 klasse of hoger
Connectivity—WiFi
- 3G
Sensoren—Versneller
- Omgeving
- Ambient light
- A-GPS
-

Voor een goede gebruikers ervaring, is het een goed idee om een toestel te nemen dat een goed kleurenprofiel biedt (uitgevoerd door de grafische driver) en over een hoofdtelefoonaansluiting die over mute beschikt voor het afspelen van media. De smartfones van tegenwoordig beschikken hier allemaal over.

-

Gebruiks tips

-

Dit gedeelte zal je van tips voorzien als je daadwerkelijk Firefox OS gaat gebruiken. Zie dit als een soort van tijdelijke oplossing, tot we daadwerkelijk een handleiding hebben.

-

Telefoon ontgrendelen

-

Als je bouw naar Firefox OS om een code gaat vragen om je toestel te ontgrendelen, is de code 0000. Sommige toestellen zullen hier later omvragen, wanneer we bezig zijn met bouwen en testen van de schermbeveiliging.

-

Nemen van een screenshot

-

Het nemen van een screenshot, is niet meer dan het indrukken van de aan/uitknop en en navigatieknop tegelijkertijd. Het screenshot zal in /sdcard/screenshots op je toestel opgeslagen worden. Je kan er ook bij via de gallerij op je toestel.

-

Als om een of andere reden dit niet werkt. Dan kun je dit ook via de terminal op de Linux or Mac OS X computer doen dat een Firefox OS bouwsysteem heeft geinstaleerd.

-

Zorg dat je ffmpeg hebt geinstaleerd.

-
    -
  1. Op Mac, als je de Macports gebruikt, doe je dat via sudo port install ffmpeg.
    2. -
  2. Voor homebrew, gebruik  brew install ffmpeg
    3. -
  3. Op Linux (Ubuntu/Debian), gebruik je sudo apt-get install ffmpeg.
    4. -
  4. Sluit je telefoon aan via een USB kabel.
    5. -
  5. Doe met je telefoon wat je dan ook wilt doen voor je screenshot.
    6. -
  6. cd in de B2G/gaia directory
    7. -
  7. make screenshot
    8. -
  8. Je hebt nu een screenshot onder de naam screenshot.png.
    9. -
-

Remote debugging met ADB

-

Om USB Debugging via adb mogelijk te maken, open Settings App en navigaeer naar  Toestel Informatie > Meer Informatie > Fabrikant. Van de lijst, list, zet een vinkje bij Remote Debugging. Eindelijk, sluit het toestel via de USB met de computer.

-

Toetsen en knoppen

-

Een typisch Firefox OS toestel heeftr een paar physical hardware knoppen:

-
-
- Home button
-
- Dit is meestal de knop onder je scherm. Als je hier op drukt, zal het je terug brengen naar je app launcher. Ingedrukt houden opent het gedeelte voor het veranderen van je zicht. switching view;Om te stoppen met de app wrijf je omhoog over het scherm.
-
-  
-
- Volume regelaar
-
- Aan de linker kant bevindt volumeknop zich; Druk op de bovenste helft voor harder en druk op de onderste helft van de volumeknop voor zachter.
-
- Aan/uit knop
-
- De aan/uitknop bevindt zich aan de rechter bovenkant van het toestel.
-
diff --git a/files/nl/archive/b2g_os/quickstart/index.html b/files/nl/archive/b2g_os/quickstart/index.html deleted file mode 100644 index ebe1f7c220..0000000000 --- a/files/nl/archive/b2g_os/quickstart/index.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Build -slug: Archive/B2G_OS/Quickstart -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/B2G_OS/Quickstart ---- -
-

Quickstart information on coding open web apps.

-
-
-
- Introduction to open web apps
-
- What are open web apps? How they differ from regular web pages? Why is this significant? This article aims to answer these questions and more.
-
- Your first app
-
- This article takes you through the basic steps and additional knowledge on top of regular web development required to create installable open web apps.
-
- Introduction to Firefox OS
-
- An introduction to Firefox OS, Mozilla's new open web app-based mobile platform.
-
- Introduction to manifests
-
- An FAQ designed to answer any questions you may have about manifests, hosting apps, origins, and other such topics.
-
- App development for web developers
-
- If you're a web developer, how do open web apps differ from what you're used to? This article explains all.
-
- App development for mobile developers
-
- If you're a native mobile application developer, what advantages can open web apps bring to you, and how do they differ from what you are used to? Here are some ideas.
-
- Developing app functionality
-
- This page talks about the kinds of different functionality that you might want to build into your apps, with links to further information.
-
- Payments
-
- How do you build functionality to make people pay for installing your open web apps? Here is the lowdown.
-
- App tools
-
- Last for this section, we provide some links to more information on the tools available to help you develop great open web apps.
-
diff --git a/files/nl/archive/b2g_os/quickstart/je_eerste_app/index.html b/files/nl/archive/b2g_os/quickstart/je_eerste_app/index.html deleted file mode 100644 index a0981402ab..0000000000 --- a/files/nl/archive/b2g_os/quickstart/je_eerste_app/index.html +++ /dev/null @@ -1,205 +0,0 @@ ---- -title: Je eerste app -slug: Archive/B2G_OS/Quickstart/Je_eerste_app -translation_of: Archive/B2G_OS/Quickstart/Your_first_app ---- -
-
-

Open web-apps bieden webontwikkelaars waar ze al jaren op hebben gewacht: een cross-platform-omgeving gericht op installeerbare apps ontwikkelt met alleen HTML, CSS en Javascript — met Firefox OS als het eerste toegewijde, open webapps-platform. Deze handleiding heeft als doel je snel aan de slag te laten gaan met een basale architectuur en bouwinstructies zodat je de volgende succesvolle app kunt maken!

-
-

If you'd like to follow along with this guide, you can download our quick start app template. Find more out about what this contains by reading our Apps template guide.

-

App Structure

-

Packaged vs. Hosted Apps

-

There are two types of open web apps: packaged and hosted. Packaged apps are essentially zip files containing all application assets: HTML, CSS, JavaScript, images, manifest, etc. Hosted apps are run from a server at a given domain, just like a standard website. Both app types require a valid manifest. When it comes time to list your app on the Firefox Marketplace, you will either upload your app as a zip file or provide the URL to where your hosted app lives.

-
-

-
-

Made in partnership with Treehouse: Check them out!

-
-
-

For the purposes of this guide, you'll create a hosted app which will live at your localhost address. Once your app is ready to list on the Firefox Marketplace, you can make the decision to bundle it as a packaged app or launch it as a hosted app.

-

App Manifests

-

Every Firefox app requires a manifest.webapp file at the app root. The manifest.webapp file provides important information about the app, such as version, name, description, icon location, locale strings, domains the app can be installed from, and much more. Only the name and description are required. The simple manifest included within the app template is similar to the following:

- 
{
-  "version": "0.1",
-  "name": "Open Web App",
-  "description": "Your new awesome Open Web App",
-  "launch_path": "/app-template/index.html",
-  "icons": {
-    "16": "/app-template/app-icons/icon-16.png",
-    "48": "/app-template/app-icons/icon-48.png",
-    "128": "/app-template/app-icons/icon-128.png"
-  },
-  "developer": {
-    "name": "Your Name",
-    "url": "http://yourawesomeapp.com"
-  },
-  "locales": {
-    "es": {
-      "description": "Su nueva aplicación impresionante Open Web",
-      "developer": {
-        "url": "http://yourawesomeapp.com"
-      }
-    },
-    "it": {
-      "description": "La tua nuova fantastica Open Web App",
-      "developer": {
-        "url": "http://yourawesomeapp.com"
-      }
-    }
-  },
-  "default_locale": "en"
-}
-
-

-
-

Made in partnership with Treehouse: Check them out!

-
-
-

 

-

A basic manifest is all you need to get started. For more details about manifests, read App Manifest.

-

App Layout & Design

-

Responsive design has become increasingly important as more screen resolutions become standard on different devices. Even if the main target of your app is mobile platforms such as Firefox OS, other devices will likely have access to it as well. CSS media queries allow you to adapt layout to device, as shown in this skeleton CSS example:

- 
/* The following are examples of different CSS media queries */
-
-/* Basic desktop/screen width sniff */
-@media only screen and (min-width : 1224px) {
-  /* styles */
-}
-
-/* Traditional iPhone width */
-@media
-  only screen and (-webkit-min-device-pixel-ratio : 1.5),
-  only screen and (min-device-pixel-ratio : 1.5) {
-  /* styles */
-}
-
-/* Device settings at different orientations */
-@media screen and (orientation:portrait) {
-  /* styles */
-}
-@media screen and (orientation:landscape) {
-  /* styles */
-}
-

There are many JavaScript and CSS frameworks available to aid in responsive design and mobile app development (Bootstrap, etc.) Choose the framework(s) that best fit your app and development style.

-

Web APIs

-

JavaScript APIs are being created and enhanced as quickly as devices are. Mozilla's WebAPI effort brings dozens of standard mobile features to JavaScript APIs. A list of device support and status is available on the WebAPI page. JavaScript feature detection is still the best practice, as shown in the following example:

- 
// If this device supports the vibrate API...
-if('vibrate' in navigator) {
-    // ... vibrate for a second
-    navigator.vibrate(1000);
-}
-

In the following example, the display style of a <div> is modified based on changes in the battery state of the device:

- 
// Create the battery indicator listeners
-(function() {
-  var battery = navigator.battery || navigator.mozBattery || navigator.webkitBattery,
-      indicator, indicatorPercentage;
-
-  if(battery) {
-    indicator = document.getElementById('indicator'),
-    indicatorPercentage = document.getElementById('indicator-percentage');
-
-    // Set listeners for changes
-    battery.addEventListener('chargingchange', updateBattery);
-    battery.addEventListener('levelchange', updateBattery);
-
-    // Update immediately
-    updateBattery();
-  }
-
-  function updateBattery() {
-    // Update percentage width and text
-    var level = (battery.level * 100) + '%';
-    indicatorPercentage.style.width = level;
-    indicatorPercentage.innerHTML = 'Battery: ' + level;
-    // Update charging status
-    indicator.className = battery.charging ? 'charging' : '';
-  }
-})();
-

In the code sample above, once you confirm that the Battery API is supported, you can add event listeners for chargingchange and levelchange to update the element's display. Try adding the following to the quickstart template, and see if you can get it working.

-

Check the WebAPI page frequently to keep up to date with device API statuses.

-

Install API functionality

-

In our sample quickstart app template, we've implemented an install button that you can click when viewing the app as a standard Web page, to install that site on Firefox OS as an app. The button markup is nothing special:

- 
<button id="install-btn">Install app</button>
-

This button's functionality is implemented using the Install API (see install.js):

- 
var manifest_url = location.href + 'manifest.webapp';
-
-function install(ev) {
-  ev.preventDefault();
-  // define the manifest URL
-  // install the app
-  var installLocFind = navigator.mozApps.install(manifest_url);
-  installLocFind.onsuccess = function(data) {
-    // App is installed, do something
-  };
-  installLocFind.onerror = function() {
-    // App wasn't installed, info is in
-    // installapp.error.name
-    alert(installLocFind.error.name);
-  };
-};
-
-// get a reference to the button and call install() on click if the app isn't already installed. If it is, hide the button.
-var button = document.getElementById('install-btn');
-
-var installCheck = navigator.mozApps.checkInstalled(manifest_url);
-
-installCheck.onsuccess = function() {
-  if(installCheck.result) {
-    button.style.display = "none";
-  } else {
-    button.addEventListener('click', install, false);
-  };
-};
-
-

Let's run through briefly what is going on:

-
    -
  1. We get a reference to the install button and store it in the variable button.
    2. -
  2. We use navigator.mozApps.checkInstalled to check whether the app defined by the manifest at http://people.mozilla.com/~cmills/location-finder/manifest.webapp is already installed on the device. This test is stored in the variable installCheck.
    3. -
  3. When the test is successfully carried out, its success event is fired, therefore installCheck.onsuccess = function() { ... } is run.
    4. -
  4. We then test for the existence of installCheck.result using an if statement. If it does exist, meaning that the app is installed, we hide the button. An install button isn't needed if it is already installed.
    5. -
  5. If the app isn't installed, we add a click event listener to the button, so the install() function is run when the button is clicked.
    6. -
  6. When the button is clicked and the install() function is run, we store the manifest file location in a variable called manifest_url, and then install the app using navigator.mozApps.install(manifest_url), storing a reference to that installation in the installLocFind variable. You'll notice that this installation also fires success and error events, so you can run actions dependent on whether the install happened successfully or not.
    7. -
-

You may want to verify the implementation state of the API when first coming to Installable web apps.

-
-

Note: Installable open web apps have a "single app per origin" security policy; basically, you can't host more than one installable app per origin. This makes testing a bit more tricky, but there are still ways around this, such as creating different sub-domains for apps, testing them using the Firefox OS Simulator, or testing the install functionality on Firefox Aurora/Nightly, which allows you to install installable web apps on the desktop. See FAQs about apps manifests for more information on origins.

-
-

WebRT APIs (Permissions-based APIs)

-

There are a number of WebAPIs that are available but require permissions for that specific feature to be enabled. Apps may register permission requests within the manifest.webapp file like so:

- 
// New key in the manifest: "permissions"
-// Request access to any number of APIs
-// Here we request permissions to the systemXHR API
-"permissions": {
-    "systemXHR": {}
-}
-

The three levels of permission are as follows:

- -

For more information on app permission levels, read Types of packaged apps. You can find out more information about what APIs require permissions, and what permissions are required, at App permissions.

-
-

It's important to note that not all Web APIs have been implemented within the Firefox OS Simulator.

-
-

Tools & Testing

-

Testing is incredibly important when supporting mobile devices. There are many options for testing installable open web apps.

-

Firefox OS Simulator

-

Installing and using the Firefox OS Simulator is the easiest way to get up and running with your app. After you install the simulator, it is accessible from the Tools -> Web Developer -> Firefox OS Simulator menu. The simulator launches with a JavaScript console so you can debug your application from within the simulator.

-

App Manager

-

The new kid on the block with regards to testing tools is called the App Manager. This tool allows you to connect desktop Firefox to a compatible device via USB (or a Firefox OS simulator), push apps straight to the device, validate apps, and debug them as they run on the device.

-

Unit Testing

-

Unit tests are extremely valuable when testing on different devices and builds. jQuery's QUnit is a popular client-side testing utility, but you can use any set of testing tools you'd like.

-

Installing Firefox OS on a Device

-

Since Firefox OS is an open source platform, code and tools are available to build and install Firefox OS on your own device. Build and installation instructions, as well as notes on what devices it can be installed on, can be found on MDN.

-

Dedicated Firefox OS developer preview devices are also available: read our Developer preview phone page for more information.

-

App Submission and Distribution

-

Once your app is complete, you can host it yourself like a standard web site or app (read Self-publishing apps for more information), or it can be submitted to the Firefox Marketplace. Your app's manifest will be validated and you may choose which devices your app will support (e.g. Firefox OS, Desktop Firefox, Firefox Mobile, Firefox Tablet). Once validated, you can add additional details about your app (screenshots, descriptions, price, etc.) and officially submit the app for listing within the Marketplace. Once approved, your app is available to the world for purchase and installation.

-

More Marketplace & Listing Information

-
    -
  1. Submitting an App to the Firefox OS Marketplace
    2. -
  2. Marketplace Review Criteria
    3. -
  3. App Submission Video Walkthrough
    4. -
-
diff --git a/files/nl/archive/b2g_os/simulator/index.html b/files/nl/archive/b2g_os/simulator/index.html deleted file mode 100644 index 75fee953e1..0000000000 --- a/files/nl/archive/b2g_os/simulator/index.html +++ /dev/null @@ -1,246 +0,0 @@ ---- -title: Firefox OS Simulator -slug: Archive/B2G_OS/Simulator -translation_of: Archive/B2G_OS/Simulator ---- -
- De Firefox OS Simulator werkt op het moment niet met Mac OS X 10.9 (Mavericks). Zie bug 930511 voor de details. Er is wel een uitweg, je zult Firefox moeten opstarten vanuit de disk image (DMG), dus zonder het eigenlijk te installeren.
-
-

De Firefox OS Simulator is op dit moment nog in een vroeg stadium, en is nog niet zo betrouwbaar en volledig als wij willen dat hij is

-

Als je bugs vind, geef ze dan door op github, heb je vragen, probeer het dan te vragen op de dev-developers-tools mailing list of in #devtools op irc.mozilla.org

-

Lees hoe je verbose logging aanzet en hoe je de laatste voorbeeld build krijgt in het help center.

-
-

The Firefox OS Simulator add-on is een tool die je er bij helpt om je Firefox OS app te testen en te debuggen op je desktop. 

-

De code-test-debug cyclus is veel sneller met de simulator dan met een echt toestel, en je hoeft natuurlijk geen echt toestel te bezitten om het te gebruiken!

-

De simulator bestaat hoofdzakelijk uit:

-

*/ originele pagina vanaf hier, help ons met vertalen /*

- -

The screenshot below shows a debugging session using the Simulator.

-

The Dashboard is on the top-right, running inside a Firefox tab. We've added one app, a packaged app called "Where am I?". At the top-left the app is running in the Simulator. We've also connected the debugging tools, which are in the panel at the bottom. You can see that the Console pane displays messages about the app.

-

-

This guide covers the following topics:

- -
- For a practical walkthrough that shows how to use the Simulator to debug a real web app, see the Simulator Walkthrough page.
-

Installing the Simulator add-on

-

The Simulator is packaged and distributed as a Firefox add-on. To install it:

-
    -
  1. Using Firefox, go to the Simulator's page on addons.mozilla.org.
    2. -
  2. Click "Add to Firefox".
    3. -
  3. Once the add-on has downloaded you will be prompted to install it: click "Install Now".
    4. -
-

Because of the size of the add-on, Firefox may freeze for several seconds while installing it, and a dialog titled "Warning: Unresponsive script" may appear. It it does, click "Continue" to wait for installation to finish. This should not occur from Firefox 27 onwards.
-
- Once you have installed the Simulator add-on, Firefox will periodically check for newer versions and keep it up to date for you.

-

The Dashboard opens automatically when you install the Simulator, and you can reopen it at any time by going to the "Firefox" menu (or the "Tools" menu on OS X and Linux), then "Web Developer", then "Firefox OS Simulator":

-


- The Dashboard is the tool you use to add your app to the Simulator and run it. Here's what it looks like:

-

Adding, removing and refreshing apps

-

Adding apps

-

To add a packaged app to the Simulator, open the Dashboard, click "Add Directory" and select the manifest file for your app.
-
- To add a hosted app, enter a URL in the textbox where it says "URL for page or manifest.webapp", then click "Add URL". If the URL points to a manifest, then that manifest will be used. If it doesn't, the Dashboard will generate a manifest for the URL: so you can add any website as an app just by entering its URL.
-
- When you add an app, the Dashboard will run a series of tests on your manifest file, checking for common problems. See the section on Manifest Validation for details on what tests are run.

-

Unless manifest validation reveals that your app has errors, the Dashboard will then automatically run your app in the Simulator.

-

Managing apps

-

Once you have added an app, it will appear in the Manager's list of installed apps:
-
- Each entry gives us the following information about the app:

- -

It also gives us four commands:

- -
-

Refresh App from the Simulator window: you can update and reload an app directly from the Simulator window using the menubar action or its associated shortcut while the app is running.

-
-

Manifest validation

-

When you supply a manifest, the Manager will run some validation tests on it. It reports three categories of problems:

- -

It summarises the problems encountered in the entry for the app: clicking on the summary provides more details.

-

Manifest errors

-

The Dashboard will report the following conditions as errors, meaning that you won't be able to run your app in the Simulator without fixing them:

- -

Here's the result of trying to add a manifest file with a missing "name":
-

-

Manifest warnings

-

The Dashboard will report the following manifest issues as warnings:

- -

Simulator-specific warnings

-

Finally, the Manager will emit warnings for apps that use features of Firefox OS not yet fully supported by the Simulator:

- -

Running the Simulator

-

There are two different ways the Simulator may be started:

- -

Either way, once the Simulator is running, the button labeled "Stopped" turns green and the label changes to "Running". To stop the Simulator, click this button again.
-
- The Simulator appears as a separate window, sized so the simulated screen area is 320x480 pixels, with a toolbar at the bottom and a menubar at the top that contains some extra features:

-

-

To simulate touch events you can click the mouse button and drag while holding the button down. So by clicking and dragging right-to-left from the Home Screen, you'll see the built-in apps, as well as any apps you have added:

-

-

Simulator toolbar

-

In the bottom toolbar, from left to right, these are the Home button, the Screen Rotation button, and the Geolocation button.

- -

-

Simulator menubar

-

In the top menubar, you can access some useful commands to make development more efficient:

-

- -

The keyboard shortcut for the "App Refresh" command makes it possible to iteratively develop an app much like a web page:

- -
-

"Refresh App and Clear Data" hidden shortcut: sometimes it's useful to clear data that the Simulator has stored for an app, so the Simulator contains a hidden shortcut, Shift - Ctrl/Cmd - R, that will refresh the running app while clearing the following data:

- -
-

Attaching developer tools

-

You can attach developer tools to the Simulator, to help debug your app. At the moment you can only attach the JavaScript Debugger, the Web Console, the Style Editor, the Profiler and the Network Monitor, but we're working on adding support for more developer tools.

-
-

Some of these tools are only available in Beta, Aurora, or Nightly builds of Firefox.

-
-

To attach developer tools to the Simulator, click the "Connect" button for an app:

-

-

The Dashboard will then open a developer toolbox pane at the bottom of the Dashboard tab and connect it to the app:

-

-

Web Console

-

The app can log to this console using the global console object, and it displays various other messages generated by the app: network requests, CSS and JS warnings/errors, and security errors. (Learn more about the Web Console.)

-

Debugger

-

Using the Debugger, you can step through JavaScript code that is running in the connected app, manage breakpoints, and watch expressions to track down errors and problems faster. (Learn more about the Debugger.)

-

Style Editor

-

You can view and edit CSS files referenced in the app using the connected Style Editor. Your changes will be applied to the app in real time, without needing to refresh the app. (Learn more about the Style Editor.)

-

Profiler

-

Using the Profiler tool connected to the app, you can to find out where your JavaScript code is spending too much time. The Profiler periodically samples the current JavaScript call stack and compiles statistics about the samples. (Learn more about the Profiler.)

-

Network Monitor

-

Thanks to the new Network Monitor, you can analyze the status, headers, content and timing of all the network requests initiated by the app through a friendly interface. (Learn more about the Network Monitor.)

-

Receipts

-

If you are developing a paid app, you should test your receipt validation code (e.g. the code that verifies that a user has already purchased the app or has been issued a refund and then informs the user and locks or unlocks app features accordingly) on a valid (cryptographically signed) receipt.

-

Thanks to the "Receipts" menu in each app entry on the Simulator Dashboard, you can install an app with a "Valid", "Invalid", or "Refunded" test receipt. Simply select the type of receipt you wish to test, and the Dashboard will retrieve a test receipt of that type from the Marketplace receipt service and reinstall the app with that receipt in the Simulator:

-

-

Push to device

-

If you have a Firefox OS device you can connect it to the Simulator, and can then push apps from the Dashboard to the device.

-

Connecting a device

-

To connect the device, follow the instructions in the guide to connecting a Firefox OS device to the desktop. Note that you don't have to install ADB, as the Simulator add-on includes it already.

-

Pushing apps to the device

-

Once you've set up the device and desktop, and connected the device to your desktop via USB, you'll see the note "Device connected" appear on the left of the Dashboard, and a new command appear in the entry for each app labeled "Push":

-

-

Click "Push", and the app will be installed on the Firefox OS device.

-
-

Manual Steps:

- -
-

Firefox OS Device Connection Confirmation

-

On every device reboot, the first "Push" request needs to be confirmed on the device:

-

-

Troubleshooting on Linux

-

If you are unable to connect your device after creating udev rules, please see this bug.

-

Limitations of the Simulator

-

Note that the Firefox OS Simulator isn't a perfect simulation.

-

Hardware limitations

-

Apart from screen size, the Simulator does not simulate the hardware limitations of a Firefox OS device such as available memory or CPU speed.

-

Audio/video codecs

-

The following codecs depend on hardware-accelerated decoding and are therefore not yet supported:

- -

This means it isn't possible to use the Simulator to test video playback in apps and on websites like Youtube that rely on these codecs.

-

Unsupported APIs

-

Certain APIs that work on the device won't work on the Simulator, generally because the supporting hardware is not available on the desktop. We've implemented simulations for some APIs such as geolocation, and expect to add more in future releases. However, at the moment the following APIs are not supported. Using them might throw errors or just return incorrect results:

- -

Getting help

-

The Firefox OS Simulator is still at an early stage of development, and isn't yet as reliable and complete as we'd like it to be.

-

If you find any bugs, please file them on GitHub. If you have a question, try asking us on the dev-developer-tools mailing list or on #devtools on irc.mozilla.org.

-

How to enable verbose logging

-

Use about:config to create the preference extensions.r2d2b2g@mozilla.org.sdk.console.logLevel, set it to the integer value 0, and disable/reenable the addon. Additional messages about the Simulator's operation will appear in the Error Console (or Browser Console in newer versions of Firefox).

-

How to get the latest preview build

-

As the section on installing the Simulator explains, you can get the latest release of the Simulator add-on from addons.mozilla.org.

-

Sometimes you might want to try out the very latest features before they're officially released. If so, you can download preview builds from the following URLs:

- -

Be aware that preview builds are less stable and thoroughly tested than release builds.

diff --git a/files/nl/archive/css3/index.html b/files/nl/archive/css3/index.html deleted file mode 100644 index ca57cadba4..0000000000 --- a/files/nl/archive/css3/index.html +++ /dev/null @@ -1,976 +0,0 @@ ---- -title: CSS3 -slug: Archive/CSS3 -tags: - - CSS - - CSS Referentie - - Intermediate -translation_of: Archive/CSS3 ---- -

CSS3 is the latest evolution of the Cascading Style Sheets language and aims at extending CSS2.1. It brings a lot of long-awaited novelties, like rounded corners, shadows, gradients, transitions or animations, as well as new layouts like multi-columns, flexible box or grid layouts. Experimental parts are vendor-prefixed and should either be avoided in production environments, or used with extreme caution as both their syntax and semantics can change in the future.

- -

Modules and the standardization process

- -

CSS Level 2 needed 9 years, from August 2002 to June 2011 to reach the Recommendation status. This was due to the fact that a few secondary features hold back the whole specification. In order to accelerate the standardization of non-problematic features, the CSS Working Group of the W3C, in a decision referred as the Beijing doctrine, divided CSS in smaller components called modules . Each of these modules is now an independent part of the language and moves towards standardization at its own pace. While some modules are already W3C Recommendations, other still are early Working Drafts. New modules are also added when new needs are identified.

- -

CSS Modules and Snapshots as defined since CSS3 Formally, there is no CSS3 standard per se . Each module being standardized independently, the standard CSS consists of CSS2.1 amended and extended by the completed modules, not necessary all with the same level number. At each point of time, a snapshot of the CSS standard can be defined, listing CSS2.1 and the mature modules.

- -

The W3 consortium periodically publishes such snapshots, like in 2007 or 2010.

- -

Though today no module with a level greater than 3 is standardized, this will change in the future. Some modules, like Selectors 4 or CSS Borders and Backgrounds Level 4 already have an Editor's Draft, though they haven't yet reached the First Published Working Draft status.

- -

CSS modules status

- -

Stable modules

- -

A few CSS modules are already fairly stable and have reached one of the three recommendation level of the CSSWG: Candidate Recommendation, Proposed Recommendation or Recommendation. These can be used without prefix and are pretty stable, though a few features can still be dropped at the Candidate Recommendation stage.

- -

These modules extend and amend the CSS2.1 specification which build the core of the specification. Together with it, they are the current snapshot of the CSS specification.

- - - - - - - - - - - -
{{ SpecName("CSS3 Colors", "", "") }}{{ Spec2("CSS3 Colors") }} since June 7th, 2011
-

Adds the {{ cssxref("opacity") }} property, and the hsl(), hsla(), rgba() and rgb() functions to create {{cssxref("<color>")}} values. It also defines the currentColor keyword as a valid color.

- -

The transparent color is now a real color (thanks to the support for the alpha channel) and is a now an alias for rgba(0,0,0,0.0) .

- -

It deprecates the system-color keywords that shouldn't be used in a production environment anymore.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Selectors", "", "") }}{{ Spec2("CSS3 Selectors") }} since September 29th, 2011
-

Adds:

- -
    -
  • Substring matching attribute selectors, E[attribute^="value"], E[attribute$="value"], E[attribute*="value"] .
    • -
  • New pseudo-classes: {{ cssxref(":target") }}, {{ cssxref(":enabled") }} and {{ cssxref(":disabled") }}, {{ cssxref(":checked") }}, {{ cssxref(":indeterminate") }}, {{ cssxref(":root") }}, {{ cssxref(":nth-child") }} and {{ cssxref(":nth-last-child") }}, {{ cssxref(":nth-of-type") }} and {{ cssxref(":nth-last-of-type") }}, {{ cssxref(":last-child") }}, {{ cssxref(":first-of-type") }} and {{ cssxref(":last-of-type") }}, {{ cssxref(":only-child") }} and {{ cssxref(":only-of-type") }},{{ cssxref(":empty") }}, and {{ cssxref(":not") }}.
    • -
  • Pseudo-elements are now characterized by two colons rather then one: :after becomes {{ cssxref("::after") }}, :before becomes {{ cssxref("::before") }}, :first-letter becomes {{ cssxref("::first-letter") }}, and :first-line becomes {{ cssxref("::first-line") }}.
    • -
  • The new general sibling combinator ( h1~pre ).
    • -
-
- -

The next iteration of the Selectors specification is already in progress, though it still hasn't reached the First Public Working Draft stage.

- - - - - - - - - - - -
{{ SpecName("CSS3 Namespaces", "", "") }}{{ Spec2("CSS3 Namespaces") }} since September 29th, 2011
-

Adds the support for the XML Namespaces by defining the notion of CSS qualified name, using the ' | ' syntax and adding the {{ cssxref("@namespace") }} CSS at-rule.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Media Queries", "", "") }}{{ Spec2("CSS3 Media Queries") }} since June 19th, 2012
-

Extends the former media type ( print, screen, … ) to a full language allowing queries on the device media capabilities like only screen and (color) .

- -

Media queries are not only used in CSS document but also in some attributes of HTML Elements, like the {{ htmlattrxref("media","link") }} attribute of the {{ HTMLElement("link") }} element.

-
- -

The next iteration of this specification is in the work, allowing to tailor a Web site regarding the input methods available on the user agent, with new media features like hover or pointer. Detection of EcmaScript support, using the script media features is also proposed.

- - - - - - - - - - - -
{{ SpecName("CSS3 Style", "", "") }}{{ Spec2("CSS3 Style") }} since November 7th, 2013
Formally defines the syntax of the content of the HTML style global attribute.
- - - - - - - - - - - -
{{ SpecName("CSS3 Backgrounds", "", "") }}{{ Spec2("CSS3 Backgrounds") }}
-

Adds:

- -
    -
  • Support, on backgrounds, for any type of {{cssxref("<image>")}}, and not only for uri() defined ones.
    • -
  • Support for multiple background images.
    • -
  • The {{ cssxref("background-repeat") }} space and round values, and for the 2-value syntax of this CSS property.
    • -
  • The {{ cssxref("background-attachment") }} local value.
    • -
  • The CSS {{ cssxref("background-origin") }}, {{ cssxref("background-size") }}, and {{ cssxref("background-clip") }} properties.
    • -
  • Support for curved border corners, with the CSS {{ cssxref("border-radius") }}, {{ cssxref("border-top-left-radius") }}, {{ cssxref("border-top-right-radius") }}, {{ cssxref("border-bottom-left-radius") }}, and {{ cssxref("border-bottom-right-radius") }} properties.
    • -
  • Support for the use of an {{cssxref("<image>")}} as the border with the CSS {{ cssxref("border-image") }}, {{ cssxref("border-image-source") }}, {{ cssxref("border-image-slice") }}, {{ cssxref("border-image-width") }}, {{ cssxref("border-image-outset") }}, and {{ cssxref("border-image-repeat") }} properties.
    • -
  • Support for shadows of the element with the CSS {{ cssxref("box-shadow") }} property.
    • -
-
- -

The CSS4 iteration of the Backgrounds and Borders specification is already in progress, though it still hasn't reached the First Public Working Draft stage, it plans to add the ability to clip a border (with the CSS {{ cssxref("border-clip") }}, {{ cssxref("border-clip-top") }}, {{ cssxref("border-clip-right") }}, {{ cssxref("border-clip-bottom") }}, and {{ cssxref("border-clip-left") }} properties) or to control the shape of the border in a corner (using the CSS {{ cssxref("border-corner-shape") }} property).

- - - - - - - - - - - -
{{ SpecName("CSS3 Multicol", "", "") }}{{ Spec2("CSS3 Multicol") }}
Adds support for easy multi-column layouts using the CSS {{ cssxref("columns") }}, {{ cssxref("column-count") }}, {{ cssxref("column-fill") }}, {{ cssxref("column-gap") }}, {{ cssxref("column-rule") }}, {{ cssxref("column-rule-color") }}, {{ cssxref("column-rule-style") }}, {{ cssxref("column-rule-width") }}, {{ cssxref("column-span") }}, {{ cssxref("column-width") }}, {{ cssxref("break-after") }}, {{ cssxref("break-before") }}, and {{ cssxref("break-inside") }}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Speech", "", "") }}{{ Spec2("CSS3 Speech") }}
Defines the speech media type, an aural formatting model and numerous properties specific for speech-rendering user agents.
- - - - - - - - - - - -
{{ SpecName("CSS3 Images", "", "") }}{{ Spec2("CSS3 Images") }}
-

Defines the {{cssxref("<image>")}} data type.

- -

Extends the url() syntax to support image slices using media fragments.

- -

Adds:

- -
    -
  • The dppx unit to the {{cssxref("<resolution>")}} data type.
    • -
  • The image() function as a more flexible alternative to url() to define an image from an url.
    - At risk : due to insufficient browser support, standardization of the image() function may be postponed to the next iteration of this module .
    • -
  • Support for linear-gradient(), repeating-linear-gradient(), radial-gradient() and repeating-radial-gradient().
    • -
  • The ability to define how a replaced element should fit in its element, using the CSS {{ cssxref("object-fit") }} property.
    - At risk : due to insufficient browser support, standardization of the {{ cssxref("object-fit") }} and property may be postponed to the next iteration of this module .
    • -
  • The ability to override the resolution and orientation of an external image using the CSS {{ cssxref("image-resolution") }} and {{ cssxref("image-orientation") }} properties.
    - At risk : due to insufficient browser support, standardization of the {{ cssxref("image-resolution") }} and {{ cssxref("image-orientation") }} properties may be postponed to the next iteration of this module .
    • -
-
- -

The CSS Image Values and Replaced Content Level 4 which will supersede CSS Image Level 3 is in development and is a {{Spec2("CSS4 Images")}}.

- - - - - - - - - - - -
{{ SpecName("CSS3 Values", "", "") }}{{ Spec2("CSS3 Values") }}
-

Makes initial and inherit keywords usable on any CSS property.

- -

Formally defines the CSS data types of CSS 2.1, that were implicitely defined by their grammar token and some textual precisions.

- -

Adds:

- -
    -
  • Definition for new font-relative length units: rem and ch .
    • -
  • Definition for viewport-relative length units: vw, vh, vmax, and vmin .
    • -
  • Precision about the real size of the absolute length units, which are not really absolute, but defined in relation with the reference pixel .
    • -
  • Definition for {{ cssxref("<angle>") }}, {{cssxref("<time>")}}, {{cssxref("<frequency>")}}, {{cssxref("<resolution>")}}.
    • -
  • Normative value to the definition of {{cssxref("<color>")}}, {{cssxref("<image>")}}, and {{ cssxref("<position>") }}.
    • -
  • Definition for the {{ cssxref("calc", "calc()") }}, {{ cssxref("attr", "attr()")}}, and toggle() functional notations.
    - At risk: due to insufficient browser support, standardization of the calc(), attr(), and toggle() functional notations may be postponed to the next iteration of this module.
    • -
-
- -

Several types definition, like <ident> and <custom-ident>, have been deferred to CSS Values and Units Module Level 4.

- - - - - - - - - - - -
{{ SpecName("CSS3 Flexbox", "", "") }}{{ Spec2("CSS3 Flexbox") }}
Add a flexbox layout to the CSS {{ cssxref("display") }} property and several new CSS properties to control it: {{ cssxref("flex") }}, {{ cssxref("flex-align") }}, {{ cssxref("flex-direction") }}, {{ cssxref("flex-flow") }}, {{ cssxref("flex-item-align") }}, {{ cssxref("flex-line-pack") }}, {{ cssxref("flex-order") }}, {{ cssxref("flex-pack") }}, and {{ cssxref("flex-wrap") }}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Conditional", "", "") }}{{ Spec2("CSS3 Conditional") }}
Adds features for conditional processing of parts of style sheets, conditioned on capabilities of the browser or the document the style sheet is being applied to. It consists mainly in allowing nested at-rules inside {{ cssxref("@media") }} and the adding of a new CSS at-rule, {{ cssxref("@supports") }}, and a new DOM method {{domxref("CSS.supports()")}}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Text Decoration", "", "") }}{{ Spec2("CSS3 Text Decoration") }}
-

Extends:

- -
    -
  • the CSS {{ cssxref("text-decoration") }} property by making it a shorthand for the CSS {{ cssxref("text-decoration-line") }}, {{ cssxref("text-decoration-color") }}, and {{ cssxref("text-decoration-style") }} properties. And adds the {{ cssxref("text-decoration-skip") }}, and {{ cssxref("text-underline-position") }} properties.
    • -
- -

Adds:

- -
    -
  • Support for East-Asian-script emphasis marks with the CSS {{ cssxref("text-emphasis") }}, {{ cssxref("text-emphasis-style") }}, {{ cssxref("text-emphasis-color") }}, and {{ cssxref("text-emphasis-position") }} properties.
    • -
  • Support for script shadows with the CSS {{ cssxref("text-shadow") }} property.
    • -
- -

Precises:

- -
    -
  • The paint order of the decorations.
    • -
- -

At risk: due to insufficient browser support, standardization of the text-decoration-skip, line positioning rules and the ability to place both emphasis marks and ruby above the same base text may be postponed to the next iteration of this module.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Fonts", "", "") }}{{ Spec2("CSS3 Fonts") }}
-

Amends the CSS2.1 Font matching algorithm to be closer to what is really implemented.

- -

Adds:

- -
    -
  • Support for downloadable fonts via the CSS {{ cssxref("@font-face") }} at-rule.
    • -
  • The control of the contextual inter-glyph spacing via the CSS {{ cssxref("font-kerning") }} property.
    • -
  • The choice of language-specific glyphs via the CSS {{ cssxref("font-language-override") }} property.
    • -
  • The choice of glyphs with specific OpenType features via the CSS {{ cssxref("font-feature-settings") }} property.
    • -
  • The control of the aspect ratio to use when fallback fonts are selected via the CSS {{ cssxref("font-size-adjust") }} property.
    • -
  • The choice of alternative font faces using the CSS {{ cssxref("font-stretch") }}, {{ cssxref("font-variant-alternates") }}, {{ cssxref("font-variant-caps") }}, {{ cssxref("font-variant-east-asian") }}, {{ cssxref("font-variant-ligatures") }}, {{ cssxref("font-variant-numeric") }}, and {{ cssxref("font-variant-position") }} properties. It also extends the related CSS {{ cssxref("font-variant") }} shorthand property and introduces the {{ cssxref("@font-feature-values") }} at-rule.
    • -
  • The control of the automatic generation of an oblique or bold face when none are found via the CSS {{ cssxref("font-synthesis") }} property.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Cascade", "", "") }}{{ Spec2("CSS3 Cascade") }}
-

Adds:

- -
    -
  • The initial, unset values for properties.
    • -
  • The CSS {{ cssxref("all") }} property.
    • -
  • The scoping mechanism.
    • -
- -

Precises:

- -
    -
  • Interaction of media-dependent @import statements and style sheet loading requirements.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Writing Modes", "", "") }}{{ Spec2("CSS3 Writing Modes") }}
Defines the writing modes of both horizontal and vertical scripts and precises how the CSS {{ cssxref("direction") }} and {{ cssxref("unicode-bidi") }} properties interact with the new CSS {{ cssxref("text-orientation") }} property, and extends them where needed.
- - - - - - - - - - - -
{{ SpecName("CSS Shapes", "", "") }}{{ Spec2("CSS Shapes") }}
Defines geometric shapes, which can be applied to floats. These shapes describe areas, around which inline content wraps instead of wrapping around the bounding box.
- - - - - - - - - - - -
{{ SpecName("CSS Masks", "", "") }}{{ Spec2("CSS Masks") }}
Defines a way for partially or fully hiding portions of visual elements. It describes how to use another graphical element or image as a luminance or alpha mask.
- -

Modules in the refining phase

- -

Specifications that are deemed to be in the refining phase are already fairly stable. Though changes are still expected, they shouldn't create incompatibilities with current implementations; they should mainly define behavior in edge cases.

- - - - - - - - - - - -
{{ SpecName("Web Animations", "", "") }}{{ Spec2("Web Animations") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Counter Styles", "", "") }}{{ Spec2("CSS3 Counter Styles") }}
 
- - - - - - - - - - - -
{{ SpecName("Compositing", "", "") }}{{ Spec2("Compositing") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Syntax", "", "") }}{{ Spec2("CSS3 Syntax") }}
Precises how charsets are determined; minor changes in parsing and tokenization algorithms.
- - - - - - - - - - - -
{{ SpecName("CSS Will Change", "", "") }}{{ Spec2("CSS Will Change") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Transitions", "", "") }}{{ Spec2("CSS3 Transitions") }}
Allows the definition of transitions effects between two properties values by adding the CSS {{ cssxref("transition") }}, {{ cssxref("transition-delay") }}, {{ cssxref("transition-duration") }}, {{ cssxref("transition-property") }}, and {{ cssxref("transition-timing-function") }} properties.
- - - - - - - - - - - -
{{ SpecName("CSS3 Animations", "", "") }}{{ Spec2("CSS3 Animations") }}
Allows the definition of animations effects by adding the CSS {{ cssxref("animation") }}, {{ cssxref("animation-delay") }},{{ cssxref("animation-direction") }}, {{ cssxref("animation-duration") }}, {{ cssxref("animation-fill-mode") }}, {{ cssxref("animation-iteration-count") }}, {{ cssxref("animation-name") }}, {{ cssxref("animation-play-state") }}, and {{ cssxref("animation-timing-function") }} properties, as well as the {{ cssxref("@keyframes") }} at-rule.
- - - - - - - - - - - -
{{ SpecName("CSS3 Transforms", "", "") }}{{ Spec2("CSS3 Transforms") }}
-

Adds:

- -
    -
  • the support of bi-dimensional transforms to be applied to any element using the CSS {{ cssxref("transform") }} and {{ cssxref("transform-origin") }} properties. The supported transforms are: matrix(), translate(), translateX(), translateY(), scale(), scaleX(), scaleY(), rotate(), skewX(), and skewY().
    • -
  • the support of tri-dimensional transforms to be applied to any element by adding the CSS {{ cssxref("transform-style") }}, {{ cssxref("perspective") }}, {{ cssxref("perspective-origin") }}, and {{ cssxref("backface-visibility") }} properties and extended the {{ cssxref("transform") }} property with the following transforms are: matrix 3d(), translate3d(), translateZ(),  scale3d(), scaleZ(), rotate3d(), rotateX(), rotateY(), rotateZ(), and perspective().
    • -
- -

Note: this specification is a merge of CSS 2D-Transforms, CSS 3D-Transforms and SVG transforms.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Fragmentation", "", "") }}{{ Spec2("CSS3 Fragmentation") }}
Defines how partitions of a Web page should happen, that is page, column breaks, and widows and orphans handling. -

Adds:

- -
    -
  • Support for defining the behavior of decorations, that is borders and background colors or images, when a box is breaked (at a page, column or line-break) with the CSS {{ cssxref("box-decoration-break") }} property.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Text", "", "") }}{{ Spec2("CSS3 Text") }}
-

Extends:

- -
    -
  • the CSS {{ cssxref("text-transform") }} property with the value full-width.
    • -
  • the CSS {{ cssxref("text-align") }} property with the value start, end, start end, and match-parent for a better support of documents with multiple directionalities of text.
    • -
  • the CSS {{ cssxref("text-align") }} property with a {{cssxref("<string>")}} value to align on that character. This is useful to align number on the decimal point.
    • -
  • the CSS {{ cssxref("word-spacing") }} and {{ cssxref("letter-spacing") }} properties with range constraints to control flexibility in justification.
    • -
- -

Adds:

- -
    -
  • Control on how whitespaces are displayed using the CSS {{ cssxref("text-space-collapse") }} and {{ cssxref("tab-size") }} properties.
    • -
  • Control on line breaks and word boundaries using the CSS {{ cssxref("line-break") }}, {{ cssxref("word-break") }}, {{ cssxref("hyphens") }}, {{ cssxref("text-wrap") }}, {{ cssxref("overflow-wrap") }}, and {{ cssxref("text-align-last") }} properties.
    • -
  • Control on how justification is happening, in order to support more type of scripts, using the CSS {{ cssxref("text-justify") }} property.
    • -
  • Control on edge effect using the CSS {{ cssxref("text-indent") }} and {{ cssxref("hanging-punctuation") }} properties.
    • -
-
- -

A few features present in early CSS Text Level 3 draft have being postponed to the next iteration of this module .

- - - - - - - - - - - -
{{ SpecName("CSS3 Variables", "", "") }}{{ Spec2("CSS3 Variables") }}
Defines a mechanism allowing to define variables in CSS.
- - - - - - - - - - - -
{{ SpecName("Compositing", "", "") }}{{ Spec2("Compositing") }}
 
- -

Modules in the revising phase

- -

Modules that are in the revising phase are much less stable than those in the refining phase. Often the syntax is still under scrutiny and may evolve a lot, in a non-compatible way. Alternative syntaxes are tested and often implemented.

- - - - - - - - - - - -
{{ SpecName("CSS3 Basic UI", "", "") }}{{ Spec2("CSS3 Basic UI") }}
-

Adds:

- -
    -
  • The ability to tweak the box model using the CSS {{ cssxref("box-sizing") }} property.
    - At risk: due to insufficient browser support, standardization of the padding-box value may be postponed to the next iteration of this module .
    • -
  • Allow the styling of forms according their content using the CSS {{ cssxref(":indeterminate") }}, {{ cssxref(":default") }}, {{ cssxref(":valid") }}, {{ cssxref(":invalid") }}, {{ cssxref(":in-range") }}, {{ cssxref(":out-of-range") }}, {{ cssxref(":required") }}, {{ cssxref(":optional") }}, {{ cssxref(":read-only") }}, and {{ cssxref(":read-write") }} pseudo-classes and the {{ cssxref("::value") }}, {{ cssxref("::choices") }}, {{ cssxref("::repeat-item") }}, and {{ cssxref("::repeat-index") }} pseudo-elements.
    - At risk: due to insufficient browser support, standardization of the pseudo-elements {{ cssxref("::value") }}, {{ cssxref("::choices") }}, {{ cssxref("::repeat-item") }}, and {{ cssxref("::repeat-index") }} may be postponed to the next iteration of this module .
    • -
  • Support for icons, defined by the CSS {{ cssxref("icon") }} property simultaneously with the new icon value of the CSS {{ cssxref("content") }} property.
    - At risk: due to insufficient browser support, standardization of the {{ cssxref("icon") }} property and the icon value may be postponed to CSS4.
    • -
  • Support for the CSS {{ cssxref("outline-offset") }} property giving more control on the position of the outline.
    • -
  • Support for the CSS {{ cssxref("resize") }} property allowing Web authors to control if and how elements should be resized.
    • -
  • Support for the CSS {{ cssxref("text-overflow") }} property defining how text overflows, if needed.
    - At risk: due to insufficient browser support, the 2-value syntax of this property as well as the support for {{cssxref("<string>")}} values may be postponed to the next iteration of this module .
    • -
  • The ability to define the hotspot of a cursor as well as the new none, context-menu, cell, vertical-text, alias, copy, no-drop, not-allowed, nesw-resize, nwse-resize, col-resize, row-resize, all-scroll, zoom-in, zoom-out, extending the {{ cssxref("cursor") }} property.
    • -
  • The ability to specify the sequential navigation order (that is the tabbing order ) using the CSS {{ cssxref("nav-index") }}, {{ cssxref("nav-up") }}, {{ cssxref("nav-right") }}, {{ cssxref("nav-left") }}, {{ cssxref("nav-down") }} properties.
    - At risk: due to insufficient browser support, standardization of the navigation properties may be postponed to the next iteration of this module .
    • -
  • The ability to control the usage of an IME editor, using the CSS {{ cssxref("ime-mode") }} property.
    - At risk: due to insufficient browser support, standardization of the {{ cssxref("ime-mode") }} property may be postponed to the next iteration of this module .
    • -
-
- -

An early list of what could be in the next iteration of the CSS Basic User Interface Module is available.

- - - - - - - - - - - -
{{ SpecName("CSS3 Grid", "", "") }}{{ Spec2("CSS3 Grid") }}
Add a grid layout to the CSS display property and several new CSS properties to control it: {{cssxref("grid")}}, {{cssxref("grid-area")}}, {{cssxref("grid-auto-columns")}}, {{cssxref("grid-auto-flow")}}, {{cssxref("grid-auto-position")}}, {{cssxref("grid-auto-rows")}}, {{cssxref("grid-column")}}, {{cssxref("grid-column-start")}}, {{cssxref("grid-column-end")}}, {{cssxref("grid-row")}}, {{cssxref("grid-row-start")}}, {{cssxref("grid-row-end")}}, {{cssxref("grid-template")}}, {{cssxref("grid-template-areas")}}, {{cssxref("grid-template-rows")}}, and {{cssxref("grid-template-columns")}}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Box Alignment", "", "") }}{{ Spec2("CSS3 Box Alignment") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Paged Media", "", "") }}{{ Spec2("CSS3 Paged Media") }}
 
- - - - - - - - - - - -
{{ SpecName("CSSOM View", "", "") }}{{ Spec2("CSSOM View") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS4 Selectors", "", "") }}{{ Spec2("CSS4 Selectors") }}
 
- -

Modules in the exploring phase

- - - - - - - - - - - -
{{ SpecName("CSS4 Images", "", "") }}{{ Spec2("CSS4 Images") }}
-

Extends:

- -
    -
  • the image() functional notation to describe the directionality of the image (rtl or ltr), allowing for bidi-sensitive images.
    • -
  • the {{ cssxref("image-orientation") }} property by adding the keyword from-image, allowing to follow EXIF data stored into images to be considered.
    • -
- -

Adds:

- -
    -
  • the image-set() functional notation to allow the definition to equivalent images at different resolution allowing for resolution-negotiated selection of images.
    • -
  • the element() functional notation allowing the use of part of the page as image.
    • -
  • the cross-fade() functional notation allowing to refer to intermediate images when transitioning between two images and defines the interpolation between two images.
    • -
  • the conic-gradient() and repeating-conic-gradient() functional notation describing a new type of gradient.
    • -
  • the {{cssxref("image-rendering")}} property that allow to define how resize of the object should be handled.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Device", "", "") }}{{ Spec2("CSS3 Device") }}
Adds a new at-rule, {{ cssxref("@viewport") }}, allowing to specify the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block.
- - - - - - - - - - - -
{{ SpecName("CSS3 GCPM", "", "") }}{{ Spec2("CSS3 GCPM") }}
Adds the ability to tailor printed version of a document by allowing to control header, footer but also references tables like indexes or tables of content.
- - - - - - - - - - - -
{{ SpecName("CSS Exclusions", "", "") }}{{ Spec2("CSS Exclusions") }}
Extends the floats mechanism to define exclusion regions in any positioning scheme. Adds the notion of shapes, in which content must flows.
- - - - - - - - - - - -
{{ SpecName("CSS3 Lists", "", "") }}{{ Spec2("CSS3 Lists") }}
Extends the list counter mechanism so that list markers can be styled and Web developers can define new list counter schemes.
- - - - - - - - - - - -
{{ SpecName("CSS3 Regions", "", "") }}{{ Spec2("CSS3 Regions") }}
Defines a new mechanism allowing content to flow across, eventually non-contiguous, multiple areas called regions.
- - - - - - - - - - - -
{{ SpecName("CSS3 Device", "", "") }}{{ Spec2("CSS3 Device") }}
Adds a new at-rule, {{ cssxref("@viewport") }}, allowing to specify the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block.
- - - - - - - - - - - -
{{ SpecName("Filters 1.0", "", "") }}{{ Spec2("Filters 1.0") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Template", "", "") }}{{ Spec2("CSS3 Template") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Sizing", "", "") }}{{ Spec2("CSS3 Sizing") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS Line Grid", "", "") }}{{ Spec2("CSS Line Grid") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Positioning", "", "") }}{{ Spec2("CSS3 Positioning") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Ruby", "", "") }}{{ Spec2("CSS3 Ruby") }}
 
- - - - - - - - - - - -
{{ SpecName("CSSOM", "", "") }}{{ Spec2("CSSOM") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Overflow", "", "") }}{{ Spec2("CSS3 Overflow") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Font Loading", "", "") }}{{ Spec2("CSS3 Font Loading") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Display", "", "") }}{{ Spec2("CSS3 Display") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS Scope", "", "") }}{{ Spec2("CSS Scope") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS4 Media Queries", "", "") }}{{ Spec2("CSS4 Media Queries") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS Non-element Selectors", "", "") }}{{ Spec2("CSS Non-element Selectors") }}
 
- - - - - - - - - - - -
{{ SpecName("Geometry Interfaces", "", "") }}{{ Spec2("Geometry Interfaces") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Inline", "", "") }}{{ Spec2("CSS3 Inline") }}
 
- -

Modules in the rewriting phase

- -

Modules that are in the rewriting phase are outdated and require to be rewritten. The syntax is still under scrutiny and may evolve a lot, in a non-compatible way. Alternative syntaxes are tested and often implemented.

- - - - - - - - - - - -
{{ SpecName("CSS3 Box", "", "") }}{{ Spec2("CSS3 Box") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Content", "", "") }}{{ Spec2("CSS3 Content") }}
 
- - - - - - - - - - - -
{{ SpecName("CSS3 Inline Layout", "", "") }}{{ Spec2("CSS3 Inline Layout") }}
 
- -

 

diff --git a/files/nl/archive/index.html b/files/nl/archive/index.html deleted file mode 100644 index 0969ff87c1..0000000000 --- a/files/nl/archive/index.html +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Archive of obsolete content -slug: Archive -translation_of: Archive ---- -

(nl translation)

- -

Here at MDN, we try to avoid outright deleting content that might be useful to people targeting legacy platforms, operating systems, and browsers. Perhaps your target audience is people that are using older hardware, for example, and can't upgrade to the latest and greatest browsers. Or for "reasons," your company is required to use very old software and you need to build Web content that runs on that software. Or perhaps you're just curious about the history of an obsolete feature or API, and how it worked.

- -

There are many reasons older documentation can be useful. So, we've established this area into which we can archive older documentation. Material in this Archived content zone should not be used for building new Web sites or apps for modern browsers. It's here for historical reference only.

- -
-

Note to writers: We need to try to keep the subpages here organized instead of all dumped into one large folder. Try to create subtrees for categories of material. Also, only move pages here that are extremely obsolete. If anyone might realistically need the information in a living product, it may not be appropriate to move it here. In general, it may be best to discuss it in the MDN Web Docs chat room before moving content here.

-
- -

{{SubpagesWithSummaries}}

- - - -

{{ListSubpages("/en-US/docs/Archive", 2, 0, 1)}}

diff --git a/files/nl/archive/meta_docs/examples/alternate_license_block/index.html b/files/nl/archive/meta_docs/examples/alternate_license_block/index.html deleted file mode 100644 index df9f83c450..0000000000 --- a/files/nl/archive/meta_docs/examples/alternate_license_block/index.html +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Alternatief licentieblok -slug: Archive/Meta_docs/Examples/Alternate_License_Block -translation_of: Archive/Meta_docs/Examples/Alternate_License_Block ---- -

 

- -

Het meeste van de MDC-inhoud is beschikbaar onder de voorwaarden van de Creative Commons: Attribution-Sharealike-licentie, met de meeste codevoorbeelden beschikbaar onder de voorwaarden van de MIT-licentie of (wanneer toegevoegd na 20-08-2010) in het publieke domein. Zie MDC:Copyrights voor details.

- -

Als een pagina onder een andere licentie valt dan de Creative Commons: Attribution-Sharealike-licentie, moet er onderaan elke alternatief gelicentieerde pagina een alternatief licentieblok worden toegevoegd.

- -

Een voorbeeld hiervan is:

- -
-

Copyright (c) (Jaar) by (Naam van auteur). Dit materiaal mag alleen worden verspreid onder de voorwaarden uiteengezet in de Open Publication License, v1.0 of later. (De nieuwste versie is momenteel beschikbaar op http://www.opencontent.org/openpub/.)

-
diff --git a/files/nl/archive/meta_docs/examples/index.html b/files/nl/archive/meta_docs/examples/index.html deleted file mode 100644 index a811e7397f..0000000000 --- a/files/nl/archive/meta_docs/examples/index.html +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Examples -slug: Archive/Meta_docs/Examples -tags: - - MDC Project - - NeedsTranslation - - TopicStub -translation_of: Archive/Meta_docs/Examples ---- -

-

The following is a list of examples for MDC Wiki markup and formatting. You are welcome to add more examples here. -

-

Examples

- -{{ languages( { "fr": "Project:fr/Exemples", "pl": "Project:pl/Przyk\u0142ady" } ) }} diff --git a/files/nl/archive/meta_docs/index.html b/files/nl/archive/meta_docs/index.html deleted file mode 100644 index 52de2c8447..0000000000 --- a/files/nl/archive/meta_docs/index.html +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: MDN "meta-documentation" archive -slug: Archive/Meta_docs -tags: - - Archive - - MDN - - NeedsTranslation - - TopicStub -translation_of: Archive/Meta_docs ---- -

Here you'll find archived "meta-documentation"; that is, documentation about how to write documentation on MDN. The articles here are obsolete and should no longer be referenced; we are retaining them here for reference while we migrate some content to new places, but very little of this is useful.

-

{{LandingPageListSubpages}}

diff --git a/files/nl/archive/meta_docs/mdn_content_on_webplatform.org/index.html b/files/nl/archive/meta_docs/mdn_content_on_webplatform.org/index.html deleted file mode 100644 index d897d66aab..0000000000 --- a/files/nl/archive/meta_docs/mdn_content_on_webplatform.org/index.html +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: MDN content op WebPlatform.org -slug: Archive/Meta_docs/MDN_content_on_WebPlatform.org -tags: - - MDN -translation_of: Archive/Meta_docs/MDN_content_on_WebPlatform.org ---- -

Web Platform Docs (WPD) is een site voor documentatie en educatie over Web standards, gerund door W3C en gesupport door Mozilla, onder anderen. Iedereen can content van MDN bijdragen naar WebPlatform.org, Onder de termen van MDN's Creative Commons Share-Alike 2.5 (CC-BY-SA) licentie. Content die vanaf MDN komt moet worden toegeschreven aan MDN, met een link naar het bronartikel. De Web Platform Docs site biedt hulp hierbij door dit in een systematische manier te doen.

- -

Als u een account maakt op WPD en een nieuwe pagina maakt, zal u zien dat er een optie is in het "new page" formulier om aan te geven dat de content die u bijdraagt van MDN af komt, en om de originele URL op MDN bij te voegen. Er is ook een manier om op WPD gedeeltes van artikelen vanaf MDN te markeren, voor gevallen waar ze worden samengevoegd tot CC-BY content. (CC-BY is de standaard licentie voor hergebruik op WPD.) De "External Attribution" pagina op WebPlatform.org Beschrijft hoe men dat doet.

- -

Vragen?

- -
-
Over MDN of zijn content
-
Plaats ze op het MDN discussie forum, of vraag ze op #mdn on irc.mozilla.org.
-
Over de licentievoorwaarden van Mozilla
-
Stuur een e-mail naar licensing@mozilla.org.
-
Over Web Platform Docs, de inhoud, de licentie of de gebruiksvoorwaarden
-
Plaats ze op de "public-webplatform" mail lijst, gerund door W3C, of vraag het op #webplatform on irc.freenode.org.
-
diff --git a/files/nl/archive/mozilla/index.html b/files/nl/archive/mozilla/index.html deleted file mode 100644 index 34a4090d47..0000000000 --- a/files/nl/archive/mozilla/index.html +++ /dev/null @@ -1,223 +0,0 @@ ---- -title: Archived Mozilla and build documentation -slug: Archive/Mozilla -translation_of: Archive/Mozilla ---- -

Translation in progress

- -

These articles are archived, obsolete documents about Mozilla, Gecko, and the process of building Mozilla projects.

- - - -
-
ActiveX Control for Hosting Netscape Plug-ins in IE
-
Microsoft has removed support for Netscape plug-ins from IE 5.5 SP 2 and beyond. If you are a plug-in author, you may find this project saves you a lot of work!
-
ant script to assemble an extension
-
This ant script helps to package an extension
-
Archived SpiderMonkey docs
-
This section contains old SpiderMonkey documentation.
-
Autodial for Windows NT
-
This document is intended to explain how the autodial helper feature implemented for bug 93002 works and why it works that way.
-
Automated testing tips and tricks
-
-
Automatic Mozilla Configurator
-
Ankh8
-
Automatically Handle Failed Asserts in Debug Builds
-
As of 2004-12-8, it is now possible to automatically handle failed asserts in debug builds of Mozilla for Windows.
-
BlackConnect
-
-
Blackwood
-
-
Bonsai
-
It is a tool that lets you perform queries on the contents of a CVS archive; you can: get a list of checkins, see what checkins have been made by a given person, or on a given CVS branch, or in a particular time period. It also includes tools for looking at checkin logs (and comments); doing diffs between various versions of a file; and finding out which person is responsible for changing a particular line of code ("cvsblame").
-
Bookmark Keywords
-
Practically every Web surfer has bookmarks, of course, and power surfers usually have hundreds stuffed into folders within folders. In addition to being handy pointers to useful resources, bookmarks in Mozilla can be used to make the address bar itself a power tool. Searches, lookups, package tracking, and even word definitions can all be retrieved from user-customized bookmarks.
-
Building TransforMiiX standalone
-
-
calICalendarView
-
An object implementing calICalendarView is generally intended to serve as a way of manipulating a set of DOM nodes corresonding to a visual representation of calIEvent and calITodo objects. Because of this close association between methods and attributes on the one hand, and content on the other, calICalendarView implementations are particularly well suited to XBL. There is, however, no practical obstacle to the interface being implemented by any javascript object associated with a group of DOM nodes, even non-anonymous XUL nodes.
-
calICalendarViewController
-
A calICalendarViewController provides a way for a calICalendarView to create, modify, and delete items. Implementing a calICalendarViewController allows for these actions to be performed in a manner consistent with the rest of the application in which the calICalendarView is included.
-
calIFileType
-
The calIFileType interface provides information about a specific file type.
-
Chromeless
-
[This project may not be active — check Github https://github.com/mozilla/chromeless]
-
Creating a Firefox sidebar extension
-
This article describes how to create a registered sidebar for Firefox 2 or greater. See the references section for information on creating extension in earlier browsers.
-
Creating a hybrid CD
-
-
Creating a Microsummary
-
A microsummary generator is a set of instructions for creating a microsummary from the content of a page. Web pages can reference generators via <link rel="microsummary"> elements in their <head> elements. Generators can also be independently downloaded and installed by users if they include a list of pages to which they apply.
-
Creating a Mozilla Extension
-
A Mozilla extension is an installable enhancement to the Mozilla browser that provides additional functionality (for example Linky, which adds an item to the context menu for opening multiple links in a document or selection). This tutorial walks you through the process of building a Mozilla extension that adds an icon to Mozilla's status bar showing the current status of the Mozilla source code (i.e. whether or not the latest version of the code is compiling successfully and passing tests). The extension will access Tinderbox, mozilla.org's webtool for tracking source code status, to get the status of the code.
-
Creating a Skin for Firefox/Getting Started
-
Download the latest version of Firefox and install it. Be sure to install the DOM Inspector extension as well.
-
Creating a Skin for Mozilla
-
In order to create a skin for mozilla, you will need to know three things. How to edit images, extract zip files, and how to modify CSS. Mozilla uses standard gif, png, and jpeg images for the buttons and CSS to style everything else in the interface.
-
Creating a Skin for SeaMonkey 2.x
-
You're going to make a theme for SeaMonkey 2, but don't know how? I hope this manual will help you.
-
Creating regular expressions for a microsummary generator
-
A regular expression is a special kind of string (i.e. a sequence of characters) that matches patterns of characters in other strings. Microsummary generators use them to identify the pages that the generators know how to summarize by matching patterns in those pages' URLs.
-
Dehydra
-
The development focus switched to DXR (where the "D" comes from "Dehydra"), which is based on clang instead of gcc. Try DXR instead, or else try the gcc python plugin: https://fedorahosted.org/gcc-python-plugin/.
-
Developing New Mozilla Features
-
Tips For Contributing New Features To Mozilla.
-
Devmo 1.0 Launch Roadmap
-
Comments, ideas, questions and other discussion should be added on the Devmo talk:1.0 Launch Roadmap page. Further details on smaller tasks being done are available at User:Dria:TODO page. See also Current Events.
-
Download Manager improvements in Firefox 3
-
Firefox 3 offers improvements to the Download Manager that allow multiple progress listeners, use of the Storage API for data management, download resuming, and more. In addition, you can augment or replace the Download Manager's user interface by implementing the new nsIDownloadManagerUI interface.
-
Download Manager preferences
-
There are several preferences used by the Download Manager. This article provides a list of them.
-
Drag and Drop
-
This section describes how to implement objects that can be dragged around and dropped onto other objects.
-
DTrace
-
 DTrace is Sun Microsystem's dynamic tracing framework that allows developers to instrument a program with probes that have little to no effect on performance when not in use and very little when active. Probe data can be collected with scripts written in D (no, not that one). Mozilla DTrace support has been added by the Sun DTrace team and can be used on Solaris 10 and Mac OS X 10.5.
-
Embedding FAQ
-
-
Embedding Mozilla in a Java Application using JavaXPCOM
-
XULRunner ships with the JavaXPCOM component, which allows Java code to interact with XPCOM objects. As you will see in this article, working with XPCOM objects in Java is not that much different than doing so in C++.
-
Error Console
-
The Error Console is a tool available in most Mozilla-based applications that is used for reporting errors in the application chrome and in web pages user opens. It reports JavaScript-related errors and warnings, CSS errors and arbitrary messages from chrome code. In Firefox, the Error Console can be opened from the tools menu or by Ctrl-Shift-J.
-
Exception logging in JavaScript
-
Technical review completed.
-
Existing Content
-
This is a list of existing mozilla.org documentation. It needs to be checked, prioritized, and migrated.
-
Extension Frequently Asked Questions
-
This is quick set of answers to the most common issues with extension development. They are currently written with mostly Firefox in mind, but most if not all should easily translate to SeaMonkey, Thunderbird or any of the other applications. For Thunderbird, you may also find the extension HowTo or FAQ pages helpful.
-
Fighting Junk Mail with Netscape 7.1
-
Summary: Is your mail account drowning in a flood of spam? Netscape 7.1 includes built-in junk mail filtering that you can train to meet your specific needs. Eric Meyer share his experiences with making the junk mail controls more effective, and looks at other preferences you might want to set to keep your account safe.
-
Firefox Sync
-
Sync refers to a family of related components and services which provide synchronization of data between Mozilla application instances. These components and services include:
-
Force RTL
-
(This is a temporary placeholder/stub for the Force RTL page)
-
Gecko Coding Help Wanted
-
Take a look through LXR, and you'll realize that Mozilla's source code is a big place.
-
GRE
-
-
Hacking wiki
-
To be able to hack the MDC wiki software, you'll need a local webserver install, which can run MediaWiki.
-
Help Viewer
-
Help Viewer: Allows information to be shown to the user inside Mozilla.
-
Helper Apps (and a bit of Save As)
-
-
Hidden prefs
-
This page has been flagged by editors or users as needing technical review. Until it is fully reviewed, it may contain inaccurate or incorrect information.
-
How to Write and Land Nanojit Patches
-
Adobe and Mozilla share a copy of Nanojit. This means that landing nanojit patches is a bit complicated, but experience has taught us that this is much better than having separate versions of nanojit.
-
HTTP Class Overview
-
This document provides an overview of the classes used by the Mozilla HTTP implementation. It's meant as a guide to developers wishing to understand or extend the Mozilla HTTP implementation.
-
Introducing the Audio API extension
-
The Audio Data API extension extends the HTML5 specification of the <audio> and <video> media elements by exposing audio metadata and raw audio data. This enables users to visualize audio data, to process this audio data and to create new audio data.
-
Java in Firefox Extensions
-
If you are in need of calling Java code from within a Firefox extension, you can make use of LiveConnect. LiveConnect gives your extension's JavaScript code (linked from or contained in XUL code) access to 2 objects: java and Packages (note that per this thread, although the new documentation for the LiveConnect reimplementation states that these globals will be deprecated (in the context of applets), "Firefox and the Java Plug-In will continue to support the global java/Packages keywords, in particular in the context of Firefox extensions."). These 2 objects let you make use of the standard JDK classes, e.g.,
-
JavaScript crypto
-
Mozilla defines a special JavaScript object to allow web pages access to certain cryptographic-related services. These services are a balance between the functionality web pages need and the requirement to protect users from malicious web sites. Most of these services are available via the DOM window object as window.crypto.
-
Jetpack
-
-
Litmus tests
-
Litmus tests are (non-automated) tests that are documented in the litmus database. See http://litmus.mozilla.org.
-
Makefile.mozextension.2
-
This Makefile is a modification of the Makefile.mozextention, found in Makefile for packaging an extension - MozillaZine Knowledge Base (2005).
-
Microsummary topics
-
To programmatically install a microsummary generator -- for example, in an extension that helps users create custom generators for their favorite sites -- obtain a reference to the nsIMicrosummaryService interface implemented by the nsIMicrosummaryService component, then call its installGenerator() method, passing it an XML document containing the generator.
-
Migrate apps from Internet Explorer to Mozilla
-
When Netscape started the Mozilla browser, it made the conscious decision to support W3C standards. As a result, Mozilla is not fully backwards-compatible with Netscape Navigator 4.x and Microsoft Internet Explorer legacy code; for example, Mozilla does not support <layer> as I will discuss later. Browsers, like Internet Explorer 4, that were built before the conception of W3C standards inherited many quirks. In this article, I will describe Mozilla's quirks mode, which provides strong backwards HTML compatibility with Internet Explorer and other legacy browsers.
-
Monitoring downloads
-
Firefox 3 makes it easier than ever to monitor the status of downloads. Although it was possible to do so in previous versions of Firefox, it was previously only possible for one observer to do so at a time. Firefox 3 introduces new API that allows any number of listeners to observe downloads.
-
Mozilla Application Framework
-
The Mozilla Application Framework: for powerful, easy to develop cross-platform applications
-
Mozilla Crypto FAQ
-
In this document I try to answer some frequently asked questions about the Mozilla web browser and mail/news client and its support for SSL, S/MIME, and related features based on cryptographic technology. Note that this document is for your information only and is not intended as legal advice. If you wish to develop and distribute cryptographic software, particularly for commercial sale or distribution, then you should consult an attorney with expertise in the particular laws and regulations that apply in your jurisdiction.
-
Mozilla Modules and Module Ownership
-
REDIRECT http://www.mozilla.org/hacking/module-ownership.html
-
Mozprocess
-
mozprocess provides python process management via an operating system and platform transparent interface to Mozilla platforms of interest. Mozprocess aims to provide the ability to robustly terminate a process (by timeout or otherwise), along with any child processes, on Windows, OS X, and Linux. Mozprocess utilizes and extends subprocess.Popen to these ends.
-
Nanojit
-
Nanojit is a small, cross-platform C++ library that emits machine code. Both the Tamarin JIT and the SpiderMonkey JIT (a.k.a. TraceMonkey) use Nanojit as their back end.
-
New Skin Notes
-
Devmo has a new skin that is ready for testing. If you go to your user preferences, you can change the skin to "Devmo". This is currently just a preview, but we would appreciate help with testing.
-
Persona
-
Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy. It works on all major browsers, and you can get started today.
-
Plug-n-Hack
-
Plug-n-Hack (PnH) is a proposed standard from the Mozilla security team for defining how security tools can interact with browsers in a more useful and usable way.
-
Plugin Architecture
-
This page contains some notes on how plugins work internally in Gecko. It is mainly of interest to Gecko developers.
-
Porting NSPR to Unix Platforms
-
Last modified 16 July 1998
-
Priority Content
-
Update: I've removed documents from this list that have been migrated into the wiki. The list of completed documents is available through the DevEdge page.
-
Prism
-
Prism is a simple XULRunner-based browser that hosts web applications without the normal web browser user interface. Prism is based on a concept called Site-Specific Browsers (SSB). An SSB is designed to work exclusively with a single web application. It doesn’t have the menus, toolbars and other accoutrements of a traditional web browser. An SSB also offers tighter integration with the operating system and desktop than a typical web application running through a web browser. Applications running in an SSB are therefore able to benefit from many of the advantages of the desktop and of the web at the same time.
-
Proxy UI
-
(Recently Added - some support for reading OS and account settings.)
-
Remote XUL
-
How to use XUL delivered from a webserver, not as part of chrome.
-
Space Manager Detailed Design
-
The Space Manager and related classes and structures are an important of the Gecko Layout system, specifically Block Layout. See the High Level Design document for an overview of the Space Manager, and as an introduction to the classes, structures and algorithms container in this, the Detailed Design Document.
-
Space Manager High Level Design
-
The Space Manager and associated classes and structures are used by Block and Line layout to manage rectangular regions that are occupied and available, for correct handling of floated elements and the elements that flow around them. When elements are floated to the left or right in a layout, they take up space and influence where other elements can be placed. The Space Manager is responsible for keeping track of where space is taken up and where it is available. This information is used by block layout to correctly compute where other floated elements should be placed, and how much space is available to normal in-flow elements that flow around the floated bits.
-
Standalone XPCOM
-
Standalone XPCOM is a tree configuration that builds a minimal set of libraries (shared mostly) that can be used to get all features of XPCOM. The contents of this standalone XPCOM in general are:
-
Stress testing
-
Consume.exe from the Windows Server 2003 Resource Kit Tools can consume various resources: physical memory, CPU time, page file, disk space and even the kernel pool. Although for Win2003, it should install into WinXP fine (Win2000 compatibility is unknown). The only downside is you can't specify how much of the resource to use, only which one to consume. Also be warned: always remember the -time option, or you may be hitting that physical reset button sooner than you would have liked!
-
Structure of an installable bundle
-
XULRunner applications, extensions, and themes all share a common directory structure, and in some cases the same bundle can be used as a standalone XULRunner application as well as an installable application extension.
-
Supporting private browsing mode
-
Firefox 3.5 introduced private browsing mode, in which potentially private information is not recorded. This includes cookies, history information, download information, and so forth.
-
SXSW 2007 presentations
-
Presentations about the Mozilla project given at the SXSW 2007 event in Austin, Texas.
-
Table Cellmap
-
The table layout use the cellmap for two purposes:
-
Table Cellmap - Border Collapse
-
This document describes the additional information that is stored for border collapse tables in the cellmap.
-
Table Layout Regression Tests
-
Changes in layout, parser and content code can have unintended side effects, also known as regressions. It is good style to check for these unwanted regressions and fixing them before checkin rather than causing Bugzilla avalanches.
-
Table Layout Strategy
-
The table layout algorithm is based on two W3C recommendations: HTML 4.01 (Chapter 11) and CSS2.1 (Chapter 17).In CSS2 a distinction between fixed and auto layout of tables has been introduced. The auto-layout mechanism is implemented in BasicTableLayoutStrategy.cpp the fixed-layout in FixedTableLayoutStrategy.cpp. All these files are in the layout/html/table/src subdirectory.
-
Tamarin
-
-
The Download Manager schema
-
The Download Manager uses an SQLite table to keep track of downloads in progress as well as queued and past downloads.
-
The life of an HTML HTTP request
-
-
The new nsString class implementation (1999)
-
This document is intended to briefly describe the new nsString class architecture, and discuss the implications on memory management, optimizations, internationalization and usage patterns.
-
TraceVis
-
TraceVis is a performance visualization system for TraceMonkey. If TraceMonkey is built with TraceVis, and run with TraceVis enabled, then TraceMonkey will output a log of all its activity transitions. The log can be postprocessed into a visualization that can be used to rapidly diagnose many tracing-related performance issues.
-
Treehydra
-
Try the gcc python plugin instead: https://fedorahosted.org/gcc-python-plugin/.
-
URIs and URLs
-
Handling network and locally retrievable resources is a central part of Necko. Resources are identified by URI "Uniform Resource Identifier" (Taken from RFC 2396):
-
URIScheme
-
List of Mozilla supported URI schemes
-
Using addresses of stack variables with NSPR threads on win16
-
This is a cautionary note that may be old information for some of you. However, since it affects the portability of code, it was deemed prudent to include a short memo describing the issue.
-
Using Monotone With Mozilla CVS
-
-
Using SVK With Mozilla CVS
-
When working with Mozilla, you tend to accumulate patches which need to be reviewed, super-reviewed, and/or approved before they can be committed to the trunk. When you have only a few uncommitted patches, you can get by using cvs diff, and just editing the output to remove other patches before submitting. However, this approach quickly becomes unscalable, especially when you have different fixes in the same tree. Using a distributed versioning system like SVK takes out much of the hassle of managing your patches.
-
Venkman
-
Venkman is the code name for Mozilla's JavaScript Debugger. It aims to provide a powerful JavaScript debugging environment for Mozilla based browsers namely Firefox, Netscape 7.x/9.x and SeaMonkey. Note that it is not included in the Gecko-based browsers such as K-Meleon, Galeon and Netscape 8.x. Venkman has been provided as part of the Mozilla install distribution since October 2001, as well as an extension package in XPI format.
-
Video presentations
-
Mozilla is actively working to produce video presentations that can help you learn how the Mozilla codebase works and how to take advantage of its technology in your own applications and extensions. This article is a jumping-off point to help you find those presentations.
-
Why Embed Gecko
-
Gecko - the Smart Embedding Choice
-
xbDesignMode.js
-
-
XML in Mozilla
-
Mozilla has a relatively good support for XML. Several World Wide Web Consortium (W3C) Recommendations and drafts from the XML family of specifications are supported, as well as other related technologies.
-
XPInstall
-
-
XPJS Components Proposal
-
Draft 1.0
-
XRE
-
-
XTech 2005 Presentations
-
-
XTech 2006 Presentations
-
-
XUL Explorer
-
XUL Explorer is a XULRunner application that provides an easy way to experiment with XUL. It’s a simple editor that can preview XUL inline or in a separate popup window. It has a list of code snippets (small fragments of XUL or JavaScript) that can be quickly inserted into the editor. The XUL can be loaded from and saved to files. A XUL validator and the Error Console are both available to help debug problems. The help menu provides access to XUL information on MDC. There is even simple “keyword” help lookup for XUL elements.
-
XULRunner
-
XULRunner is a Mozilla runtime package that can be used to bootstrap XUL+XPCOM applications that are as rich as Firefox and Thunderbird. It provides mechanisms for installing, upgrading, and uninstalling these applications.
-
diff --git a/files/nl/archive/mozilla/xul/how_to_quit_a_xul_application/index.html b/files/nl/archive/mozilla/xul/how_to_quit_a_xul_application/index.html deleted file mode 100644 index 1f0852078d..0000000000 --- a/files/nl/archive/mozilla/xul/how_to_quit_a_xul_application/index.html +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: How to Quit a XUL Application -slug: Archive/Mozilla/XUL/How_to_Quit_a_XUL_Application -tags: - - XULRunner -translation_of: Archive/Mozilla/XUL/How_to_quit_a_XUL_application ---- -

Een script kan de applicatie de opdrachtgeven netjes af te sluiten of deze na een fatale fout geforceerd af te sluiten. Dit kan met de nsIAppStartup interface. -

-
<script>
-function quit (aForceQuit)
-{
-  var appStartup = Components.classes['@mozilla.org/toolkit/app-startup;1'].
-    getService(Components.interfaces.nsIAppStartup);
-
-  // eAttemptQuit will try to close each XUL window, but the XUL window can cancel the quit
-  // process if there is unsaved data. eForceQuit will quit no matter what.
-  var quitSeverity = aForceQuit ? Components.interfaces.nsIAppStartup.eForceQuit :
-                                  Components.interfaces.nsIAppStartup.eAttemptQuit;
-  appStartup.quit(quitSeverity);
-}
-</script>
-
-

Als je de functie zo aanroept zal hij geforceerd worden gesloten. Dit gebruik je na bv een fatale fout. -

-
<script>
-try {
-  doSomething();
-}
-catch (e) {
-  quit(true);
-}
-</script>
-
-

Bij het "Quit" menuitem wat de gebruiker gebruikt moet er normaal gesproken gevraagt worden om niet opgeslagen gegevens op te slaan. De gebruiker kan deze afsluiting anuleren. -

-
<menuitem label="Quit" oncommand="quit(false);"/>
-
{{ languages( { "en": "en/How_to_Quit_a_XUL_Application" } ) }} diff --git a/files/nl/archive/mozilla/xul/index.html b/files/nl/archive/mozilla/xul/index.html deleted file mode 100644 index f6d4475a3b..0000000000 --- a/files/nl/archive/mozilla/xul/index.html +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: XUL -slug: Archive/Mozilla/XUL -translation_of: Archive/Mozilla/XUL ---- -
XUL Tutorial
-Een begeleide handleiding die je zal helpen met XUL te beginnen, afkomstig van XULPlanet.
- -
-

XUL (XML User Interface Language) is Mozilla's XML-gebasseerde programmeertaal voor het bouwen van gebruikersinterfaces. Het wordt hoofdzakelijk gebruikt door Firefox. Web ontwikkelaars die al bekend zijn met HTML leren zeer snel XUL en kunnen meteen starten met het bouwen van applicaties. Open XUL Periodic Table in Firefox of een andere Gecko-gebaseerde browser om XUL demos te bekijken.

- -
Opmerking: Deze "XUL Periodic Table" kan niet weergegeven worden in recente versies van Gecko omdat het gebruik maakt van remote XUL, een technologie die niet meer ondersteund wordt wegens mogelijke beveiligingsproblemen. Er is een XULRunner applicatie die de XUL Periodic Table bevat en die het toch mogelijk maakt de demos te openen in Gecko gebaseerde browsers. Je kan het hier downloaden. Bekijk: XULRunner_tips#Using_Firefox_3_to_run_XULRunner_applications voor instructies over hoe de XULRunner apps in Firefox te gebruiken.
-
- - - - - - - - -
-

Documentatie

- -
-
XUL Verwijzingen
-
XUL elementen, attributen, eigenschappen, methodes, and gebeurtenissen.
-
XUL Controls
-
Een beknopte lijst met alle beschikbare XUL controls.
-
XUL School
-
Een begrijpbare handleiding voor het ontwikkelen van Mozilla add-ons.
-
The Joy of XUL
-
Describes the key features and components of XUL.
-
Menus and Popups Guide
-
A guide on using menus and popup panels.
-
Template Guide
-
A detailed guide on XUL templates, which is a means of generating content from a datasource.
-
Drag and Drop
-
How to perform drag and drop operations.
-
Adapting XUL Applications for Firefox 3.0
-
A list of changes in Firefox 3.0, affecting XUL developers.
-
Adapting XUL Applications for Firefox 2.0
-
A list of changes in Firefox 2.0, affecting XUL developers.
-
Adapting XUL Applications for Firefox 1.5
-
A list of changes in Firefox 1.5, affecting XUL developers.
-
- -

View All...

- 		-

Community

- - - -

Tools

- - - -

View All...

- - - - -
- -

 

diff --git a/files/nl/archive/themes/index.html b/files/nl/archive/themes/index.html deleted file mode 100644 index aff151946d..0000000000 --- a/files/nl/archive/themes/index.html +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Themes -slug: Archive/Themes -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/Themes ---- -

Archived theme documentation.

- -

diff --git a/files/nl/archive/web/index.html b/files/nl/archive/web/index.html deleted file mode 100644 index ce3481b9ae..0000000000 --- a/files/nl/archive/web/index.html +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Archived open Web documentation -slug: Archive/Web -tags: - - Archive - - Landing - - NeedsTranslation - - TopicStub - - Web -translation_of: Archive/Web ---- - - -
{{Obsolete_Header}}
- -

The documentation listed below is archived, obsolete material about open Web topics.

- -
-
-
-
Talk:background-size
-
Should not the "Browser compatibility" table also list Google Chrome and Konqueror? Chome is not mentioned at all, but is becoming increasingly popular. Konqueror is listed below the table, which seems inconsistent. Znerd 04 August 2009
-
Browser Detection and Cross Browser Support
-
Improper browser detection can lead to web maintenance nightmares. Rethinking the basics of when and how to detect user agents is crucial to creating maintainable, cross browser web content. This article reviews several approaches to browser detection, their usefulness in specific circumstances to arrive at a common sense approach to browser detection.
-
Browser Feature Detection
-
An experimental approach to discovering degree of support for Standards
-
CSS
-
Obsolete CSS features
-
Displaying notifications (deprecated)
-
Firefox offers support for "desktop notifications"; these are notifications that are displayed to the user outside the context of the web content, using the standard notification system provided by the operating system.
-
E4X
-
ECMAScript for XML (E4X) is a programming language extension that adds native XML support to JavaScript. It does this by providing access to the XML document in a form that feels natural for ECMAScript programmers. The goal is to provide an alternative, simpler syntax for accessing XML documents than via DOM interfaces. A valid alternative to E4X is a non-native JXON algorithm.
-
E4X Tutorial
-
This tutorial walks you through the basic syntax of E4X (ECMAScript for XML). With E4X, programmers can manipulate an XML document with a syntax more familiar to JavaScript programming.
-
Talk:Array.forEach()
-
Ok, in the end I didn't remove the old code as it isn't hosted anywhere (I thought the github reference contained the code) but inserted a faster implementation above while retaining the rest of the document.
-
Iterator
-
The Iterator function returns an object which implements legacy iterator protocol and iterates over enumerable properties of an object.
-
LiveConnect
-
(Please update or remove as needed.)
-
MSX Emulator (jsMSX)
-
 
-
Old Proxy API
-
Proxies are objects for which the programmer has to define the semantics in JavaScript. The default object semantics are implemented in the JavaScript engine, often written in lower-level languages like C++. Proxies let the programmer define most of the behavior of an object in JavaScript. They are said to provide a meta-programming API.
-
ParallelArray
-
The goal of ParallelArray was to enable data-parallelism in web applications. The higher-order functions available on ParallelArray attempted to execute in parallel, though they may fall back to sequential execution if necessary. To ensure that your code executes in parallel, it is suggested that the functions should be limited to the parallelizable subset of JS that Firefox supports.
-
- -
-
-
- -
-
-
Properly Using CSS and JavaScript in XHTML Documents
-
XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition) defines XHTML to be a reformulation of HTML 4 as an XML 1.0 application.
-
Talk:JavaScript Reference
-
The guide section links to an interesting document discussing how to create and use private variables in objects, which is great if you want to protect the various properties within an object from being poked at accidentally. I also just read a document on proper inheritance using apply(). Well if you combine the two, you can have inherited private variables:
-
Scope Cheatsheet
-
JavaScript with Mozilla extensions has both function-scoped vars and block-scoped lets. Along with hoisting and dynamic behavior, scope in JavaScript is sometimes surprising.
-
Server-Side JavaScript
-
Here's a radical idea: Use one language to write entire Web apps -- the same language which billions of web pages already use, every day.
-
Sharp variables in JavaScript
-
A sharp variable is a syntax in object initializers that allows serialization of objects that have cyclic references or multiple references to the same object.
-
Standards-Compliant Authoring Tools
-
Creating cross-browser code upfront will save you lots of time quality testing your web content. The following authoring tools adhere to the W3 standards. If you're using older versions of tools that rely on old browser bugs or generate browser-specific code, it may be time to upgrade:
-
StopIteration
-
The StopIteration object was used to tell the end of the iteration in the legacy iterator protocol. Do not use this ancient feature.
-
Styling the Amazing Netscape Fish Cam Page
-
 
-
Using JavaScript Generators in Firefox
-
Generators can be used to simplify asynchronous code in Firefox by opting in to using JavaScript version 1.7 or later. You can opt in in HTML as follows:
-
Window.importDialog()
-
Because opening windows on mobile isn't necessarily appropriate, the Firefox Mobile team designed the importDialog() method to replace window.openDialog(). Instead of opening a new window, it merges the specified XUL dialog into the main window.
-
Writing JavaScript for XHTML
-
Technical review completed. Editorial review completed.
-
XForms
-
XForms were envisioned as the future of online forms as envisioned by the W3C. Drawing on other W3C standards like XML Schema, XPath, and XML Events, XForms tried to address some of the limitations of the current HTML forms model. However, XForms never gained traction and is now considered obsolete.
-
-
-
diff --git a/files/nl/archive/web/javascript/ecmascript_7_support_in_mozilla/index.html b/files/nl/archive/web/javascript/ecmascript_7_support_in_mozilla/index.html deleted file mode 100644 index d268ed2eff..0000000000 --- a/files/nl/archive/web/javascript/ecmascript_7_support_in_mozilla/index.html +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: ECMAScript 7 support in Mozilla -slug: Archive/Web/JavaScript/ECMAScript_7_support_in_Mozilla -tags: - - ECMAScript 2016 - - Firefox - - JavaScript -translation_of: Archive/Web/JavaScript/ECMAScript_Next_support_in_Mozilla ---- -
{{jsSidebar("New_in_JS")}}
- -

ECMAScript 2016 is de volgende ontwikkelversie van de ECMA-262 standaard, (bekend als JavaScript). Nog voordat ECMAScript 2015 was voltooid op 17 juni 2015 werden er al nieuwe voorstellen tot uitbreiding gedaan. De meest recente voorstellen zijn in te zien in de tc39/ecma262 GitHub repository.

- -

Huidige issues aangaande het specificatieproces zullen worden opgelost door de introductie van stages and champions voor feature sets. Er is tevens voorgesteld een tweejarig release-schema in te voeren. Voor meer informatie over het specificatieproces na ES2015, wordt verwezen naar deze presentatie door Rafael Weinstein.

- -

Een kanaal voor het versturen van reacties met betrekking tot ECMAScript standaarden is es-discuss.

- -

Experimentele features

- -

The volgende features zijn al geïmplementeerd, maar uitsluitend beschikbaar op het Firefox Nightly channel:

- -

Toevoegingen aan het Array object

- - - -

Toevoegingen aan het ArrayBuffer object

- - - -

Nieuwe TypedObject objecten

- - - -

Nieuwe SIMD objecten

- - - -

Uitvoering van stabilisatie van features 

- -

De volgende features worden ondersteund buiten de Nightly channel, maar de verdere specificatie en implementatie is nog in uitvoering. Features die oorspronkelijk in de ontwerpversie van ECMAScript 2015 waren opgenomen en zijn uitgesteld naar ECMAScript 2016 verschijnen waarschijnlijk hier.

- -

Expressies

- - - -

Features die nog niet ondersteund worden

- -

De volgende features zijn nog niet geïmplementeerd, maar worden opgelijnd voor ECMAScript 2016.

- - - -

Meer informatie

- - diff --git a/files/nl/archive/web/javascript/index.html b/files/nl/archive/web/javascript/index.html deleted file mode 100644 index 4687b7bf23..0000000000 --- a/files/nl/archive/web/javascript/index.html +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: JavaScript -slug: Archive/Web/JavaScript -translation_of: Archive/Web/JavaScript ---- - - -

{{Obsolete_Header}}

- -

Obsolete JavaScript features and unmaintained docs

- -

{{SubpagesWithSummaries}}

-- cgit v1.2.3-54-g00ecf