Found 31 pages:
|#||Page||Tags and summary|
|1||Developer guides||API, Guide, Landing, Web|
|There are a number of guides within MDN docs. These articles aim to add additional usage examples, or teach you how to use an API or feature. This page links to some of the most popular material.|
When these technologies are combined in the Ajax model, web applications are able to make quick, incremental updates to the user interface without reloading the entire browser page. This makes the application faster and more responsive to user actions.
|If you know of useful mailing lists, newsgroups, forums, or other communities related to AJAX, please link to them here.|
|This article guides you through the AJAX basics and gives you some simple hands-on examples to get you started.|
|5||WAI ARIA Live Regions/API Support||AJAX, Accessibility|
|Firefox 3 contains important improvements to the way the Mozilla engine exposes live changes in a document.|
|6||Guide to Web APIs||API, Guide, Landing, Web|
|7||Audio and Video Delivery||Audio, Guide, HTML, HTML5, Media, Video|
We can deliver audio and video on the web in a number of ways, ranging from 'static' media files to adaptive live streams. This article is intended as a starting point for exploring the various delivery mechanisms of web based media and compatibility with popular browsers.
|8||Adding captions and subtitles to HTML5 video||HTML5, Media, WebVTT, captions, subtitles, track|
In other articles we looked at how to build a cross browser video player using the
|9||Media buffering, seeking, and time ranges||Apps, Buffer, HTML5, TimeRanges, Video, buffering, seeking|
Sometimes it's useful to know how much
|10||Creating a cross-browser video player||Apps, HTML5, Video, full screen|
This article describes a simple HTML5 video player that uses the Media and Fullscreen APIs and works across most major desktop and mobile browsers. As well as working fullscreen, the player features custom controls rather than just using the browser defaults. The player controls themselves won't be styled beyond the basics required to get them working; full styling of the player will be taken care of in a future article.
|11||Cross-browser audio basics||Apps, Audio, Guide, HTML5, Media, events|
|This article provides:|
|12||Live streaming web audio and video||Guide, adaptive streaming|
Live streaming technology is often employed to relay live events such as sports, concerts and more generally TV and Radio programmes that are output live. Often shortened to just streaming, live streaming is the process of transmitting media 'live' to computers and devices. This is a fairly complex and nascent subject with a lot of variables, so in this article, we'll introduce you to the subject and let you know how you can get started.
|13||Setting up adaptive streaming media sources||Audio, HLS, HTML5, HTTP Live Streaming, MPEG-DASH, Video, adaptive streaming|
Let's say you want to set up an adaptive streaming media source on a server, to be consumed inside an HTML5 media element. How would you do that? This article explains how, looking at two of the most common formats: MPEG-DASH and HLS (HTTP Live Streaming.)
|14||Video player styling basics||Apps, Guide, Media, Styling, Video|
In the previous Cross browser video player article we described how to build a cross-browser HTML5 video player using the Media and Fullscreen APIs. This follow-up article looks at how to style this custom player, including making it responsive.
|15||Writing Web Audio API code that works in every browser||API|
|You probably have already read the announcement on the Web Audio API coming to Firefox, and are totally excited and ready to make your until-now-WebKit-only sites work with Firefox, which uses the unprefixed version of the spec.|
|16||Web Audio playbackRate explained||Apps, Audio, Media, Video, playbackRate|
|17||Audio and video manipulation||Audio, Canvas, Examples, Guide, HTML5, Media, Video, Web Audio API, WebGL, developer recommendation|
The beauty of the web is that you can combine technologies to create new forms. Having native audio and video in the browser means we can use these data streams with technologies such as
|18||Graphics on the Web||2D, 3D, Canvas, Graphics, HTML5, SVG, Web, WebGL, WebRTC|
|Websites and applications often need to present graphics, such as images.|
|Whether you're just getting started with Web development, or are just expanding your horizons into new realms of Web awesomeness, the links here should help you get started.|
|20||Mobile Web Development||Intermediate, NeedsExample|
|This page provides an overview of some of the main techniques needed to design web sites that work well on mobile devices. If you're looking for information on Mozilla's Firefox OS project, see the Firefox OS page. Or you might be interested in details about Firefox for Android.|
|21||A hybrid approach||Mobile, Responsive Design, Web Development|
|Silver bullets are hard to find in web development — you’re more likely to come across strategies that make the best use of a variety of techniques given the circumstances. This brings us to our third approach, which aims to avoid some of the shortcomings the separate sites and responsive design approaches by combining them.|
|22||Mobile-friendliness||Mobile, Web Development|
|Mobile friendliness can mean a multitude of things, depending on who you’re talking to. It can be helpful to think of it in terms of three goals for improving your site’s user experience: Presentation, Content, and Performance.|
|23||Separate sites for mobile and desktop||Mobile, Web Development|
|The "separate sites" approach to mobile Web development involves creating different sites for mobile and desktop Web users. This approach has positive and negative aspects.|
|24||Parsing and serializing XML||AJAX, Add-ons, DOM, DOM Parsing, Document, Extensions, Guide, HTMLDocument, JSON, Parsing, Parsing XML, Serializing, Serializing XML, XML, XMLDocument, XMLHttpRequest|
|In this article, we'll look at the objects provided by the web platform to make the common tasks of serializing and parsing XML easy.|
|25||Optimization and performance||Landing, Optimization, Performance, Web|
|When building modern Web apps and sites, it's important to make your content perform well. That is, to make it work quickly and efficiently. This lets it work effectively both for users of powerful desktop systems as well as for handheld devices with less power. There are several tools available to check the performance of a website or blog. The most notable tools are listed below.|
|26||Printing||DOM, Guide, NeedsContent, NeedsRelocation, printing|
|There may be times in which your web site or application would like to improve the user's experience when printing content. There are a number of possible scenarios:|
|27||SVG-in-OpenType||Draft, Fonts, Guide, NeedsContent|
|The SVG-in-OpenType work is currently in the hands of the MPEG group. Once we're ready for wider adoption the information from wiki.mozilla.org will be moved here, updated and expanded.|
|28||The Unicode Bidirectional Text Algorithm||Algorithm, BiDi, Guide, Internationalization, Introduction, Localization, Text, Unicode, direction, i18n, l10n, ltr, rtl|
|The Unicode® Bidirectional Algorithm (also known as the BiDi Algorithm) is part of the Unicode text standard that describes how the user agent should order characters while rendering Unicode text.|
|29||User input and controls||Screen Orientation, contenteditable, drag and drop, fullscreen, keyboard, mouse, pointer lock, touch, user input|
Modern web user input goes beyond simple mouse and keyboard: think of touchscreens for example. This article provides recommendations for managing user input and implementing controls in open web apps, along with FAQs, real-world examples, and links to further information for anyone needing more detailed information on the underlying technologies. Relevant APIs and events include touch events, Pointer Lock API, Screen Orientation API, Fullscreen API, Drag & Drop and more.
|30||The Web Open Font Format (WOFF)||Fonts, NeedsMobileBrowserCompatibility, WOFF, WOFF2|
|WOFF (the Web Open Font Format) is a web font format developed by Mozilla in concert with Type Supply, LettError, and other organizations. It|
|This page explains how to write websites that do not break when new browser versions are released.
This is especially important for intranets and other non-public websites; if we can't see your code, we can't see that it broke. It's not always possible to follow all of these, but following as many of them as possible will help future-proof your website.