Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove references to IE #32868

Merged
merged 2 commits into from
Mar 28, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions files/en-us/web/api/document/plugins/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,3 @@ An {{domxref("HTMLCollection")}}.
## Browser compatibility

{{Compat}}

## See also

- [MSDN documentation](<https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms537477(v=vs.85)>)
55 changes: 0 additions & 55 deletions files/en-us/web/api/fullscreen_api/guide/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,61 +108,6 @@ This starts by looking at the value of the `fullscreenElement` attribute on the

If fullscreen mode is already active (`fullscreenElement` is non-`null`), we call {{DOMxRef("document.exitFullscreen()")}}.

## Prefixing

For the moment not all browsers are implementing the unprefixed version of the API (for vendor agnostic access to the Fullscreen API you can use [Fscreen](https://github.com/rafgraph/fscreen)). Here is the table summarizing the prefixes and name differences between them:

<table class="standard-table">
<thead>
<tr>
<th scope="row">Standard</th>
<th scope="col">WebKit (Safari) / Blink (Chrome &#x26; Opera) / Edge</th>
<th scope="col">Gecko (Firefox)</th>
<th scope="col">Internet Explorer</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">
{{DOMxRef("Document.fullscreen")}} {{Deprecated_Inline}}
</th>
<td><code>webkitIsFullScreen</code></td>
<td><code>mozFullScreen</code></td>
<td>-</td>
</tr>
<tr>
<th scope="row">
{{DOMxRef("Document.fullscreenEnabled")}}
</th>
<td><code>webkitFullscreenEnabled</code></td>
<td><code>mozFullScreenEnabled</code></td>
<td><code>msFullscreenEnabled</code></td>
</tr>
<tr>
<th scope="row">
{{DOMxRef("Document.fullscreenElement")}}
</th>
<td><code>webkitFullscreenElement</code></td>
<td><code>mozFullScreenElement</code></td>
<td><code>msFullscreenElement</code></td>
</tr>
<tr>
<th scope="row">{{DOMxRef("Document.exitFullscreen()")}}</th>
<td><code>webkitExitFullscreen()</code></td>
<td><code>mozCancelFullScreen()</code></td>
<td><code>msExitFullscreen()</code></td>
</tr>
<tr>
<th scope="row">
{{DOMxRef("Element.requestFullscreen()")}}
</th>
<td><code>webkitRequestFullscreen()</code></td>
<td><code>mozRequestFullScreen()</code></td>
<td><code>msRequestFullscreen()</code></td>
</tr>
</tbody>
</table>

## Specifications

{{Specifications}}
Expand Down
1 change: 0 additions & 1 deletion files/en-us/web/css/zoom/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,4 +149,3 @@ Not part of any standard. Apple has [a description in the Safari CSS Reference](
## See also

- [`zoom` entry in CSS-Tricks' CSS Almanac](https://css-tricks.com/almanac/properties/z/zoom/)
- [Bug 390936: Implement Internet Explorer `zoom` property for CSS](https://bugzil.la/390936) on the Firefox issue tracker Bugzilla
Original file line number Diff line number Diff line change
Expand Up @@ -27,17 +27,17 @@ For [HTML](/en-US/docs/Web/HTML) documents, browsers use a DOCTYPE in the beginn
</html>
```

The DOCTYPE shown in the example, `<!DOCTYPE html>`, is the simplest possible, and the one recommended by current HTML standards. Earlier versions of the HTML standard recommended other variants, but all existing browsers today will use full standards mode for this DOCTYPE, even the dated Internet Explorer 6. There are no valid reasons to use a more complicated DOCTYPE. If you do use another DOCTYPE, you may risk choosing one which triggers almost standards mode or quirks mode.
The DOCTYPE shown in the example, `<!DOCTYPE html>`, is the simplest possible, and the one recommended by current HTML standards. Earlier versions of the HTML standard recommended other variants, but all existing browsers today will use full standards mode for this DOCTYPE. There are no valid reasons to use a more complicated DOCTYPE. If you do use another DOCTYPE, you may risk choosing one which triggers almost standards mode or quirks mode.

Make sure you put the DOCTYPE right at the beginning of your HTML document. Anything before the DOCTYPE, like a comment or an XML declaration will trigger quirks mode in Internet Explorer 9 and older.
Put the DOCTYPE right at the beginning of your HTML document, before any other content.

The only purpose of `<!DOCTYPE html>` is to activate no-quirks mode. Older versions of HTML standard DOCTYPEs provided additional meaning, but no browser ever used the DOCTYPE for anything other than switching between render modes.

See also a detailed description of [when different browsers choose various modes](https://hsivonen.fi/doctype/).

### XHTML

If you serve your page as [XHTML](/en-US/docs/Glossary/XHTML) using the `application/xhtml+xml` MIME type in the `Content-Type` HTTP header, you do not need a DOCTYPE to enable standards mode, as such documents always use 'full standards mode'. Note however that serving your pages as `application/xhtml+xml` will cause Internet Explorer 8 to show a download dialog box for an unknown format instead of displaying your page, as the first version of Internet Explorer with support for XHTML is Internet Explorer 9.
If you serve your page as [XHTML](/en-US/docs/Glossary/XHTML) using the `application/xhtml+xml` MIME type in the `Content-Type` HTTP header, you do not need a DOCTYPE to enable standards mode, as such documents always use 'full standards mode'.

If you serve XHTML-like content using the `text/html` MIME type, browsers will read it as HTML, and you will need the DOCTYPE to use standards mode.

Expand Down
2 changes: 1 addition & 1 deletion files/en-us/web/http/headers/x-xss-protection/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ browser-compat: http.headers.X-XSS-Protection

{{HTTPSidebar}}{{Non-standard_header}}

The HTTP **`X-XSS-Protection`** response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting ({{Glossary("Cross-site_scripting", "XSS")}}) attacks. These protections are largely unnecessary in modern browsers when sites implement a strong {{HTTPHeader("Content-Security-Policy")}} that disables the use of inline JavaScript (`'unsafe-inline'`).
The HTTP **`X-XSS-Protection`** response header was a feature of Internet Explorer, Chrome and Safari that stopped pages from loading when they detected reflected cross-site scripting ({{Glossary("Cross-site_scripting", "XSS")}}) attacks. These protections are largely unnecessary in modern browsers when sites implement a strong {{HTTPHeader("Content-Security-Policy")}} that disables the use of inline JavaScript (`'unsafe-inline'`).

> **Warning:** Even though this feature can protect users of older web browsers that don't yet support {{Glossary("CSP")}}, in some cases, **XSS protection can create XSS vulnerabilities** in otherwise safe websites. See the section below for more information.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -558,50 +558,6 @@ There are also a couple of events related to buffering:

> **Note:** You can read more on [Buffering, Seeking and Time Ranges](/en-US/docs/Web/Media/Audio_and_video_delivery/buffering_seeking_time_ranges) elsewhere.

## Browser support

The following tables list basic audio support across desktop and mobile browsers, and what audio codecs are supported.

### Desktop

| Desktop Browser | Version |
| ----------------- | ------- |
| Chrome | 4+ |
| Firefox | 3.5+ |
| Internet Explorer | 9+ |
| Opera | 10.5+ |
| Safari | 4+ |

### Mobile

| Mobile Browser | Version |
| ----------------- | ------- |
| Chrome (Android) | 32+ |
| Firefox (Android) | 26+ |
| IE Mobile | 10+ |
| Opera Mobile | 11+ |
| Safari (iOS) | 4+ |
| Android Browser | 2.3+ |
| Blackberry | 7+ |

## Audio Codec Support

| Browser | Ogg | MP3 | AAC | PCM | Opus |
| ------------------------ | --- | ------- | --- | -------- | ------- |
| Firefox 3.5+ | ✓ | ✓ \*26+ | | ✓ | ✓ \*14+ |
| Safari 5+ | | ✓ | ✓ | | |
| Chrome 6+ | ✓ | ✓ | ✓ | ✓ \*9+ | |
| Opera 10.5+ | ✓ | | | | |
| Internet Explorer 9+ | | ✓ | ✓ | | |
| Firefox Mobile | ✓ | ✓ | ✓ | ✓ | ✓ |
| Safari iOS3+ | | ✓ | ✓ | ✓ \*4.2+ | |
| Chrome Mobile | ✓ | ✓ | ✓ | ✓ | |
| Opera Mobile | ✓ | ✓ | ✓ | ✓ | |
| Internet Explorer Mobile | ✓ | ✓ | ✓ | ✓ | |
| Android 2.3+ | ✓ | ✓ | ✓ | ✓ | |

> **Note:** Nearly all browsers support MP3 — for more details see this page on [media format browser compatibility](/en-US/docs/Web/Media/Formats#browser_compatibility).

## See also

- [Buffering, Seeking and Time Ranges](/en-US/docs/Web/Media/Audio_and_video_delivery/buffering_seeking_time_ranges)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -94,28 +94,9 @@ HLS can also be decoded using JavaScript, which means we can support the latest

At the start of the streaming session, an [extended M3U (m3u8) playlist](https://en.wikipedia.org/wiki/M3U8#Extended_M3U_directives) is downloaded. This contains the metadata for the various sub-streams that are provided.

### Streaming File Format Support

| Browser | DASH | HLS | Opus (Audio) |
| --------------------- | ----- | ----- | ------------ |
| Firefox 32 | ✓ [1] | ✓ [2] | ✓ 14+ |
| Safari 6+ | | ✓ | |
| Chrome 24+ | ✓ [1] | ✓ | |
| Opera 20+ | ✓ [1] | | |
| Internet Explorer 10+ | ✓ 11 | ✓ [2] | |
| Firefox Mobile | ✓ | ✓ | ✓ |
| Safari iOS6+ | | ✓ | |
| Chrome Mobile | ✓ | ✓ [2] | |
| Opera Mobile | ✓ [1] | ✓ | |
| Android | ✓ | | |

\[1] Via JavaScript and MSE

\[2] Via JavaScript and a CORS Proxy

## Audio Streaming File Formats

There are also some audio formats beginning to see support across browsers.
There are also several audio formats:

### Opus

Expand Down
73 changes: 1 addition & 72 deletions files/en-us/web/media/formats/audio_codecs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -401,28 +401,6 @@ As a patent-encumbered format, AAC support is somewhat less predictable. For exa
<tr>
<th scope="row">Browser compatibility</th>
<td>
<table class="standard-table">
<tbody>
<tr>
<th scope="row">Feature</th>
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
<tr>
<th scope="row">AAC support</th>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>9</td>
<td>Yes</td>
<td>3.1</td>
</tr>
</tbody>
</table>
<p>
Due to patent issues, Firefox does not directly support AAC. Instead,
Firefox relies upon a platform's native support for AAC. This
Expand Down Expand Up @@ -457,39 +435,6 @@ As a patent-encumbered format, AAC support is somewhat less predictable. For exa
</tbody>
</table>

<table class="standard-table" style="margin-left: 4em; max-width: 30em">
<caption>
AAC support in Firefox using external library, by platform
</caption>
<thead>
<tr>
<th scope="row">Platform</th>
<th scope="col">First Firefox version<br />with AAC support</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">Windows (Vista and later)</th>
<td>22</td>
</tr>
<tr>
<th scope="row">Android</th>
<td>20</td>
</tr>
<tr>
<th scope="row">
Linux (depends on
<a href="https://gstreamer.freedesktop.org/">GStreamer</a>)
</th>
<td>26</td>
</tr>
<tr>
<th scope="row">macOS</th>
<td>35</td>
</tr>
</tbody>
</table>

### ALAC (Apple Lossless Audio Codec)

The **Apple Lossless Audio Codec** (**ALAC** or **Apple Lossless**) is a lossless codec developed by Apple. After initially being a closed format, Apple opened it up under an Apache license.
Expand Down Expand Up @@ -549,7 +494,6 @@ Keep in mind, however, that lossless codecs require substantially more bandwidth
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -559,7 +503,6 @@ Keep in mind, however, that lossless codecs require substantially more bandwidth
<td>No</td>
<td>No</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
</tr>
</tbody>
Expand Down Expand Up @@ -651,7 +594,6 @@ As a speech-specific codec, AMR is essentially useless for any other content, in
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -660,7 +602,6 @@ As a speech-specific codec, AMR is essentially useless for any other content, in
<td>No</td>
<td>?</td>
<td>No</td>
<td>?</td>
<td>No</td>
<td>?</td>
</tr>
Expand Down Expand Up @@ -753,7 +694,6 @@ FLAC is a great choice for smaller audio effects files where pristine quality an
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -762,8 +702,7 @@ FLAC is a great choice for smaller audio effects files where pristine quality an
<td>Yes</td>
<td>Yes</td>
<td>51 (desktop)<br />58 (mobile)</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
<td>11</td>
</tr>
</tbody>
Expand Down Expand Up @@ -846,7 +785,6 @@ This codec is required to be supported by all [WebRTC](/en-US/docs/Web/API/WebRT
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -855,7 +793,6 @@ This codec is required to be supported by all [WebRTC](/en-US/docs/Web/API/WebRT
<td>23</td>
<td>15</td>
<td>22</td>
<td>No</td>
<td>43</td>
<td>11</td>
</tr>
Expand Down Expand Up @@ -949,7 +886,6 @@ G.722 is primarily used with WebRTC connections, as it's one of the audio codecs
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -958,7 +894,6 @@ G.722 is primarily used with WebRTC connections, as it's one of the audio codecs
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
</tr>
Expand Down Expand Up @@ -1069,7 +1004,6 @@ The patents behind MP3 have expired, removing many or most licensing concerns ar
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -1078,7 +1012,6 @@ The patents behind MP3 have expired, removing many or most licensing concerns ar
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>9</td>
<td>Yes</td>
<td>3.1</td>
</tr>
Expand Down Expand Up @@ -1274,7 +1207,6 @@ Opus is a good all-around audio codec for use in your web applications, and can
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -1283,7 +1215,6 @@ Opus is a good all-around audio codec for use in your web applications, and can
<td>33</td>
<td>14</td>
<td>15</td>
<td>No</td>
<td>20</td>
<td>11</td>
</tr>
Expand Down Expand Up @@ -1376,7 +1307,6 @@ Generally, Vorbis is more efficient in terms of size and bit rate than MP3 at si
<th scope="col">Chrome</th>
<th scope="col">Edge</th>
<th scope="col">Firefox</th>
<th scope="col">Internet Explorer</th>
<th scope="col">Opera</th>
<th scope="col">Safari</th>
</tr>
Expand All @@ -1385,7 +1315,6 @@ Generally, Vorbis is more efficient in terms of size and bit rate than MP3 at si
<td>4</td>
<td>17</td>
<td>3.5</td>
<td>No</td>
<td>11.5</td>
<td>No</td>
</tr>
Expand Down
Loading
Loading