aboutsummaryrefslogtreecommitdiff
path: root/files/ko/web/api
diff options
context:
space:
mode:
Diffstat (limited to 'files/ko/web/api')
-rw-r--r--files/ko/web/api/audio_channels_api/using_the_audiochannels_api/index.html248
-rw-r--r--files/ko/web/api/audiochannelmanager/index.html74
-rw-r--r--files/ko/web/api/audiochannels_api/index.html121
-rw-r--r--files/ko/web/api/mozmmsevent/index.html82
-rw-r--r--files/ko/web/api/mozmmsmessage/index.html83
-rw-r--r--files/ko/web/api/mozmobilemessagemanager/index.html101
-rw-r--r--files/ko/web/api/mozmobilemessagethread/index.html40
-rw-r--r--files/ko/web/api/mozsmsevent/index.html109
-rw-r--r--files/ko/web/api/mozsmsfilter/index.html108
-rw-r--r--files/ko/web/api/mozsmsmanager/index.html95
-rw-r--r--files/ko/web/api/mozsmsmessage/index.html56
-rw-r--r--files/ko/web/api/mozsmssegmentinfo/index.html36
-rw-r--r--files/ko/web/api/navigator/mozmobilemessage/index.html58
-rw-r--r--files/ko/web/api/navigator/moznotification/index.html63
-rw-r--r--files/ko/web/api/navigator/mozsms/index.html67
15 files changed, 0 insertions, 1341 deletions
diff --git a/files/ko/web/api/audio_channels_api/using_the_audiochannels_api/index.html b/files/ko/web/api/audio_channels_api/using_the_audiochannels_api/index.html
deleted file mode 100644
index 1e07e262c6..0000000000
--- a/files/ko/web/api/audio_channels_api/using_the_audiochannels_api/index.html
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: Using the AudioChannels API
-slug: Web/API/Audio_Channels_API/Using_the_AudioChannels_API
-tags:
- - Firefox OS
- - Guide
- - Non-standard
-translation_of: Archive/B2G_OS/API/Audio_Channels_API/Using_the_AudioChannels_API
----
-<p>{{DefaultAPISidebar("Audio Channels API")}}{{ non-standard_header() }}</p>
-
-<div class="summary">
-<p>오디오 채널 API(<a href="/en-US/docs/Web/API/Audio_Channels_API">Audio Channels API</a>)는 현재 Firefox OS 전용 기능으로, 응용프로그램의 오디오 컨텐트를 중요성에 따른 계층구조로 배치하도록 한다. 이는 다른 오디오의 재생과 액션 발생에 반응하여 오디오가 일시정지되고 다시재생될 때를 지시하고 다른 종류의 볼륨을 제어할 수 있도록 한다. 이 가이드는 오디오 채널에 대한 기본적인 사용방법을 보여줄 것이다.</p>
-</div>
-
-<p>오디오 채널의 종류는 다음과 같다.</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">채널 이름</th>
- <th scope="col">중요도</th>
- <th scope="col">용도</th>
- <th scope="col">앱 권한 수준</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>normal</td>
- <td>1</td>
- <td>UI 효과음, 앱과 웹 컨텐트</td>
- <td>Normal</td>
- </tr>
- <tr>
- <td>content</td>
- <td>2</td>
- <td>음악, 라디오, 비디오</td>
- <td>Normal</td>
- </tr>
- <tr>
- <td>notification</td>
- <td>3</td>
- <td>새 이메일, SMS 수신음</td>
- <td>Privileged</td>
- </tr>
- <tr>
- <td>alarm</td>
- <td>4</td>
- <td>알람 시계, 캘린더 알람</td>
- <td>Privileged</td>
- </tr>
- <tr>
- <td>ringer</td>
- <td>5</td>
- <td>전화 수신 벨소리</td>
- <td>Internal</td>
- </tr>
- <tr>
- <td>telephony</td>
- <td>6</td>
- <td>진행중인 통화, VOIP 통화</td>
- <td>Internal</td>
- </tr>
- <tr>
- <td>publicnotification</td>
- <td>7</td>
- <td>강제된 카메라 셔터음</td>
- <td>Internal</td>
- </tr>
- </tbody>
-</table>
-
-<p>하나의 오디오 채널이 사용되면, 언제든지 낮은 우선순위의 채널들은 자동으로 일시정디 된다. 단, 한가지 예외가 있는데, "normal"과 "content"채널은 동일한 우선순위를 가진다. 이는 "content"채널이 사용된다면 "normal"채널과 믹싱된다는 것을 의미한다. 만약 두 앱이 동시에 "content" 채널을 사용하려 한다면, 포어그라운드 앱이 우선권을 가진다. 만약 두 앱 모두 백그라운드 앱이라면, 마지막에 채널을 사용시도한 앱이 우선권을 가진다.</p>
-
-<div class="note">
-<p><strong>Note</strong>: 각 채널은 음소거와 볼륨 설정을 따로 가지고 있다.</p>
-</div>
-
-<div class="note">
-<p><strong>Note</strong>: "telephony" 채널은 통화용 내장 스피커를 사용한다. 다른 모든 채널은 스피커 또는 헤드폰/헤드셋 등을 사용한다.</p>
-</div>
-
-<h2 id="유즈_케이스">유즈 케이스</h2>
-
-<p>As obvious user-centric uses cases, audio channels allow users to play music from audio player apps even when they are running in the background, so they can do other things as it plays. However, they probably want the music to pause when someone rings the phone. As another example, when users mute their phone, they probably don't want to also mute their wake up alarm for the next morning.</p>
-
-<p>Other use cases:</p>
-
-<ul>
- <li>When the user leaves an app, under normal circumstances the app should be muted.</li>
- <li>When the volume keys are used it should change the volume for different audio types depending on context. For example while in the alarm app, the volume keys should adjust the alarm volume and not the "normal" volume.</li>
- <li>When a video app starts playing audio, background music should be muted while the video is playing.</li>
- <li>Turn down the volume of background audio rather than completely silence it when the "notification" channel is used.</li>
- <li>Show which applications/tabs are currently playing audio.</li>
- <li>Show UI to mute a specific app/tag.</li>
- <li>Enable a spotify-app/tab to be treated as a music app. I.e. it should be able to get the same benefits as if it had mozaudiochannel=content. Including both the automatic muting of other content audio, and the ability to play in the background.</li>
- <li>Control which application/tab gets to play audio if there are several background applications that all are attempting to use the "content" channel, but no visible apps using the "content" channel.</li>
-</ul>
-
-<h2 id="예제_앱">예제 앱</h2>
-
-<p>To explain audio channel functionality, we have built a sample app, imaginitively called <a href="https://github.com/mdn/audio-channels-demo">audio-channels-demo</a> (you can <a href="http://mdn.github.io/audio-channels-demo/">see it running live here</a>.) The following shows what it looks like on Firefox OS.</p>
-
-<p><img alt="A demo showing a title of AudioChannels demo, with an audio player and a select box to choose an audio channel to play the audio in." src="https://mdn.mozillademos.org/files/8801/demo-screen.png" style="display: block; height: 356px; margin: 0px auto; width: 200px;"></p>
-
-<p>The demo provides an audio player, and a {{htmlelement("select")}} box for choosing what audio channel to play the audio in (only "Normal" and "Content" are provided.) When the content audio channel is selected, you will be able to go to the homescreen and put the app in the background but still have the music keep playing. This is not the case with the normal channel — "normal" audio content is stopped when an app goes into the background.</p>
-
-<p>To interrupt the playing of "content" audio content, you could try phoning the phone that the app is running on, or setting off an alarm. As you can see from the table above, these are both in higher priority audio channels.</p>
-
-<p>The app also fires notifications when audio is interrupted or play resumes, and when the headphones are unplugged or plugged in again. Let's explore how this functionality is implemented.</p>
-
-<h2 id="매니페스트_권한이_요구된다">매니페스트 권한이 요구된다</h2>
-
-<p>As explained in the table near the top, the different audio channels require a range of <a href="/en-US/Apps/Build/App_permissions">different permission levels</a> for their use in apps, ranging from normal (hosted apps) to internal (also known as certified.) In any case, you do need to declare the <code>permissions</code> field in your <code>manifest.webapp</code> file to use AudioChannels, once per channel (note that we also declared permission to use system notifications, as they are used in our demo app also.)</p>
-
-<pre class="brush: json">"permissions": {
- "audio-channel-normal" : {
- "description" : "Needed to play this app's audio content on the normal channel"
- },
- "audio-channel-content" : {
- "description" : "Needed to play this app's audio content on the content channel"
- },
- "desktop-notification" : {
- "description" : "Needed to fire system notifications"
- }
-}</pre>
-
-<h2 id="Selecting_the_audio_channel">Selecting the audio channel</h2>
-
-<p>Changing the audio channel to play the audio through in the app is a slightly more complex matter than you might think. Declaring the channel type statically in your HTML might look like this:</p>
-
-<pre class="brush: html">&lt;audio mozaudiochannel="content" autoplay src="myAudio.ogg"&gt;&lt;/audio&gt;</pre>
-
-<p>Declaring it dynamically in your JavaScript might look like this:</p>
-
-<pre class="brush: js">var player = new Video();
-player.mozAudioChannelType = 'content';
-player.src = '../video-clips/myVideo.ogv';</pre>
-
-<p>However you do it, you need to declare the channel before you declare the <code>src</code> of the media you want to play, so it can be loaded and placed into the right channel. For this reason, our demo app does it in a slightly convoluted way, deleting and then recreating the audio player each time the audio channel is changed:</p>
-
-<pre class="brush: js">function createAudio(channelValue) {
-
- ...
-
- audioContainer.innerHTML = '';
- var player = document.createElement('audio');
- var source1 = document.createElement('source');
- var source2 = document.createElement('source');
-
- player.controls = true;
- player.mozAudioChannelType = channelValue;
- source1.src = 'audio/dragon.ogg';
- source1.type = 'audio/ogg';
- source2.src = 'audio/dragon.mp3';
- source2.type = 'audio/mpeg';
-
- player.appendChild(source1);
- player.appendChild(source2);
- audioContainer.appendChild(player);
-
- ...
-
-}
-
-channelSelect.addEventListener('change', function() {
- createAudio(channelSelect.value);
-});</pre>
-
-<p>So the <code>createAudio()</code> function is run when the {{htmlelement("select")}} box (referenced in the JS as <code>channelSelect</code>) has its value changed, with the <code>channelSelect</code> value as a parameter. In this function, the <code>audioContainer</code> (a simple {{htmlelement("div")}} that wraps the audio player) has its contents deleted. Next, a new audio player and {{htmlelement("source")}} elements are created, have their necessary attributes filled in, and are added back into the <code>audioContainer</code>. Note that <code>player.mozAudioChannelType = channelValue;</code> is included before the audio source is set.</p>
-
-<p>So with the audio channel set to "content", you can now keep the audio playing even when the app is in the background.</p>
-
-<h2 id="Setting_which_channel's_volume_to_control">Setting which channel's volume to control</h2>
-
-<p>As well as setting what audio channel your audio is going to play in, you can also separately set what channel will have its volume adjusted when the user presses the device's volume keys. This for example allows us to adjust our standard content's volume without affect ringer or alarm volume. It is controlled using the {{domxref("AudioChannelManager.volumeControlChannel")}} property. So at the top of the <code>createAudio()</code> function, we include this block:</p>
-
-<pre class="brush: js">function createAudio(channelValue) {
- if (navigator.mozAudioChannelManager) {
- if(channelValue == 'normal') {
- navigator.mozAudioChannelManager.volumeControlChannel = 'normal';
- } else if(channelValue == 'content') {
- navigator.mozAudioChannelManager.volumeControlChannel = 'content';
- }
- console.log(navigator.mozAudioChannelManager.volumeControlChannel);
- }
-
- ...
-
-}
-</pre>
-
-<p>The {{domxref("AudioChannelManager")}} object is accessed by a call to the {{domxref("Navigator.mozAudioChannelManager","navigator.mozAudioChannelManager")}} property — note the <code>moz</code> prefix. This is first done to provide some rudimentary feature detection, so trying to access this feature won't break the app on platforms that don't support it. Next, we include an <code>if ... else if</code> block to check what channel value was passed into the function from the {{htmlelement("select")}} element, and then set the <code>volumeControlChannel</code> value accordingly.</p>
-
-<h2 id="Firing_notifications_when_the_audio_is_interrupted">Firing notifications when the audio is interrupted</h2>
-
-<p>Now we have audio playing in an audio channel, it will be interrupted either when a more important audio channel starts being played (for example when a telephone call is received), or when the app is moved into the background in the case of the lowest priority "normal" channel. When this condition ends, our channel will resume playing. We can respond to these events using the <code>mozinterruptbegin</code> and <code>mozinterruptend</code> event handlers, which can be attached to the video or audio player playing the audio. You can see these handlers being used at the bottom of the <code>createAudio()</code> function:</p>
-
-<pre class="brush: js">function createAudio(channelValue) {
-
- ...
-
- player.addEventListener('mozinterruptbegin', function() {
- var notification = new Notification('Metal interrupted!', { body: "Something more important?" });
- });
-
- player.addEventListener('mozinterruptend', function() {
- var notification = new Notification('Metal resumed!', { body: "Important thing finished." });
- });
-}</pre>
-
-<p>Here we attach both relevant event listeners to the audio <code>player</code>; when the events occur, we run simple functions that fire system notifications to tell the user what has happened. See the following screenshots for what it will look like:</p>
-
-<div style="width: 410px; margin: 0 auto;"><img alt="A notification at the top of the Firefox OS interface saying Metal interrupted: something more important?" src="https://mdn.mozillademos.org/files/8803/interrupt-notification.png" style="height: 356px; margin: 0; padding: 0; width: 200px;"> <img alt="A notification at the top of the Firefox OS interface saying Metal resumed: important thing finished?" src="https://mdn.mozillademos.org/files/8805/resume-notification.png" style="height: 356px; margin: 0; padding: 0; width: 200px;"></div>
-
-<h2 id="Firing_notifications_when_the_headphones_are_(un)plugged">Firing notifications when the headphones are (un)plugged</h2>
-
-<p>The {{domxref("AudioChannelManager")}} object includes a {{domxref("AudioChannelManager.headphones","headphones")}} property that returns <code>true</code> if headphones are plugged into the device and false if not, and an event handler — {{domxref("AudioChannelManager.onheadphoneschange","onheadphoneschange")}} — which fires whenever headphones are plugged in to or unplugged from the device. We decided to use these together to create a headphone status notification system:</p>
-
-<pre class="brush: js">if (navigator.mozAudioChannelManager) {
- navigator.mozAudioChannelManager.onheadphoneschange = function() {
- if(navigator.mozAudioChannelManager.headphones == true) {
- var notification = new Notification('Headphones plugged in!');
- } else {
- var notification = new Notification('Headphones unplugged!');
- }
- }
-}</pre>
-
-<p>Let's go through this and explain what's happening. Again, multiple calls are made to {{domxref("Navigator.mozAudioChannelManager","navigator.mozAudioChannelManager")}}, first for feature detection, then to set up a function that runs when the onheadphoneschange handler fires. Inside this function, we check whether the headphones property returns true — if so, the headphones are plugged in, so we tell the user that with a notification. If not, they must be unplugged, so we return a suitable notification for that case too. The notifications will look something like this:</p>
-
-<p><img alt="A notification at the top of the Firefox OS interface saying Headphones plugged in!" src="https://mdn.mozillademos.org/files/8807/headphones-notification.png" style="display: block; height: 356px; margin: 0px auto; width: 200px;"></p>
-
-<h2 id="Specifications">Specifications</h2>
-
-<p>The AudioChannels API has no official spec at the moment; see <a href="https://wiki.mozilla.org/WebAPI/AudioChannels">https://wiki.mozilla.org/WebAPI/AudioChannels</a> for implementation details, WebIDL, etc.</p>
-
-<h2 id="See_also">See also</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li><a href="/en-US/Apps/Build/App_permissions">App permissions for Firefox OS</a></li>
- <li><a href="/en-US/docs/Web/API/AudioChannels_API/Using_the_AudioChannels_API">Using the AudioChannels API</a></li>
- <li>{{domxref("Navigator.mozAudioChannelManager","navigator.mozAudioChannelManager")}}</li>
- <li>{{domxref("HTMLMediaElement")}}</li>
- <li><a href="/en-US/Apps/Build/User_notifications">Notifications</a></li>
-</ul>
diff --git a/files/ko/web/api/audiochannelmanager/index.html b/files/ko/web/api/audiochannelmanager/index.html
deleted file mode 100644
index 6bee14adb8..0000000000
--- a/files/ko/web/api/audiochannelmanager/index.html
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: AudioChannelManager
-slug: Web/API/AudioChannelManager
-tags:
- - API
- - Audio
- - Non-standard
-translation_of: Archive/B2G_OS/API/AudioChannelManager
----
-<p>{{APIRef("Web Audio API")}} {{Non-standard_header}}</p>
-
-<p>AudioChannelManager는 디바이스의 오디오 채널을 관리하는 기능을 포함하는 오디오 채널 API(<a href="/en-US/docs/Web/API/AudioChannels_API">AudioChannels API</a>)의 인터페이스이다. 특정한 앱 내에서 볼륨 버튼이 눌렸을 때 어떤 채널의 볼륨이 적용될지를 설정하는 기능을 포함하고 있다.</p>
-
-<h2 id="메소드">메소드</h2>
-
-<div class="note">
-<p><strong>Note</strong>: 부모클래스인 {{domxref("EventTarget")}}의 메소드를 상속받는다.</p>
-</div>
-
-<h2 id="속성">속성</h2>
-
-<div class="note">
-<p><strong>Note</strong>: 부모클래스인 {{domxref("EventTarget")}}의 속성을 상속받는다.</p>
-</div>
-
-<dl>
- <dt>{{domxref("AudioChannelManager.headphones")}} {{readonlyinline}}</dt>
- <dd>헤드폰이 디바이스에 장착되었는지 여부를 나타내는 불리언 값.</dd>
- <dt>{{domxref("AudioChannelManager.telephonySpeaker")}}</dt>
- <dd><span class="short_text" id="result_box" lang="ko"><span class="atn">"</span><span class="atn">telephony</span><span class="atn">" </span><span>오디오</span> <span class="hps">채널이</span> <span class="hps">장치의</span> <span class="hps">스피커</span> <span class="hps">밖으로</span> <span class="atn hps">재생</span><span>할지 여부를</span> <span class="hps">설정할</span> <span class="hps">수 있도록하는</span> <span class="atn hps">불리언 값</span><span>.</span></span></dd>
- <dt>{{domxref("AudioChannelManager.volumeControlChannel")}}</dt>
- <dd>하드웨어 볼륨 버튼을 눌렀을 때 변경해야 할 오디오 채널에 대한 {{domxref("DOMString")}} 값.</dd>
-</dl>
-
-<h3 id="이벤트_핸들러">이벤트 핸들러</h3>
-
-<dl>
- <dt>{{domxref("AudioChannelManager.onheadphoneschange")}}</dt>
- <dd>헤드폰이 장착되었는지 혹은 해제되었는지 알려주는 트리거.</dd>
-</dl>
-
-<h2 id="예제">예제</h2>
-
-<p>아래 간단한 예제를 보면, 앱의 <code>AudioChannelManager 객체에 접근하기 위해 </code>{{domxref("Navigator.mozAudioChannelManager","navigator.mozAudioChannelManager")}} 속성을 사용한다.  먼저 첫번째로 수신된 변수에 따라 {{domxref("AudioChannelManager.volumeControlChannel")}} 속성을 설정한 후, 몇 가지 기본적인 특징을 검출한다.</p>
-
-<pre class="brush: js">var channelValue = 'content';
-
-if (navigator.mozAudioChannelManager) {
- if(channelValue == 'normal') {
- navigator.mozAudioChannelManager.volumeControlChannel = 'normal';
- } else if(channelValue == 'content') {
- navigator.mozAudioChannelManager.volumeControlChannel = 'content';
- }
- console.log(navigator.mozAudioChannelManager.volumeControlChannel);
-}</pre>
-
-<div class="note">
-<p><strong>Note</strong>: 완전히 동작하는 예제를 보기 위해서는 <a href="https://github.com/mdn/audio-channels-demo">audio-channels-demo</a>를 확인하기 바란다. Firefox OS 디바이스에 앱을 설치하고 음악을 재생한 뒤, 채널을 normal 그리고 content로 지정하여 앱을 백그라운드로 전환 후 어떤 일이 발생하는지 확인하도록 한다.</p>
-</div>
-
-<h2 id="명세">명세</h2>
-
-<p>현재 오디오 채널 API는 공식적인 명세(스펙)가 정의되어있지 않다. <a href="https://wiki.mozilla.org/WebAPI/AudioChannels">https://wiki.mozilla.org/WebAPI/AudioChannels</a>를 참고하면 WebIDL에 대한 자세한 구현사항에 대해 확인할 수 있다.</p>
-
-<h2 id="함께_보기">함께 보기</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li><a href="/en-US/Apps/Build/App_permissions">App permissions for Firefox OS</a></li>
- <li><a href="/en-US/docs/Web/API/AudioChannels_API/Using_the_AudioChannels_API">Using the AudioChannels API</a></li>
- <li>{{domxref("Navigator.mozAudioChannelManager","navigator.mozAudioChannelManager")}}</li>
- <li>{{domxref("HTMLMediaElement")}}</li>
-</ul>
diff --git a/files/ko/web/api/audiochannels_api/index.html b/files/ko/web/api/audiochannels_api/index.html
deleted file mode 100644
index de4d98de42..0000000000
--- a/files/ko/web/api/audiochannels_api/index.html
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: Audio Channels API
-slug: Web/API/AudioChannels_API
-tags:
- - API
- - Audio
- - AudioChannels
- - Firefox OS
- - Non-standard
- - Obsolete
- - Reference
-translation_of: Archive/B2G_OS/API/Audio_Channels_API
----
-<p>{{DefaultAPISidebar("Audio Channels API")}}</p>
-
-<div class="blockIndicator nonStandard">
-<p><strong>Non-standard</strong><br>
- This feature is not on a current W3C standards track, but it is supported on the Firefox OS platform. Although implementations may change in the future and it is not supported widely across browsers, it is suitable for use in code dedicated to Firefox OS apps.</p>
-</div>
-
-<p class="summary">The <strong>Audio Channels API</strong> is a Firefox OS-only feature allowing you to place your app audio content into a hierarchy of importance, which dictates when the audio will be paused and resumed in response to other audio playing and actions occurring and allows you to control the volume of different types of audio independently from one another.</p>
-
-<p>Use case examples:</p>
-
-<ul>
- <li>You want your audio player app to continue playing audio even when it is running in the background so you can do other things as it plays, but you want it to pause when someone rings your phone.</li>
- <li>When you mute your phone you don't want to also mute your wake up alarm for the next morning.</li>
-</ul>
-
-<div class="note">
-<p><strong>Note</strong>: Since the AudioChannels API is non-standard and requires permissions, for many simple use cases such as pausing game music when the app/web page goes into the background you would be better off using the standard <a href="/en-US/docs/Web/Guide/User_experience/Using_the_Page_Visibility_API">Page Visibility API</a>, or perhaps <a href="/en-US/docs/Web/API/Window/onfocus" title="The onfocus property returns the onFocus event handler code on the current element."><code>window.onfocus</code></a>/<a href="/en-US/docs/Web/API/Window/onblur" title="The onblur property returns the onBlur event handler code, if any, that exists on the current element."><code>window.onblur</code></a>. AudioChannels are mainly useful for more complex phone uses cases involving telephony, etc.</p>
-</div>
-
-<h2 id="Concepts_and_usage">Concepts and usage</h2>
-
-<p>The AudioChannels API extends the <a href="/en-US/docs/Web/API/HTMLMediaElement" title="The HTMLMediaElement interface adds to HTMLElement the properties and methods needed to support basic media-related capabilities that are common to audio and video."><code>HTMLMediaElement</code></a> and <a href="/en-US/docs/Web/API/AudioContext" title="The AudioContext interface represents an audio-processing graph built from audio modules linked together, each represented by an AudioNode. An audio context controls both the creation of the nodes it contains and the execution of the audio processing, or decoding. You need to create an AudioContext before you do anything else, as everything happens inside a context."><code>AudioContext</code></a> interfaces with (among other things) a <code>mozAudioChannelType</code> property that can be set to the channel you want your audio to be played in. The  <a href="/en-US/docs/Web/HTML/Element/audio" title="The HTML &lt;audio> element is used to embed sound content in documents. It may contain one or more audio sources, represented using the src attribute or the &lt;source> element: the browser will choose the most suitable one. It can also be the destination for streamed media, using a MediaStream."><code>&lt;audio&gt;</code></a> and <a href="/en-US/docs/Web/HTML/Element/video" title="Use the HTML &lt;video> element to embed video content in a document."><code>&lt;video&gt;</code></a> elements can also be used to set this value via the <code>mozaudiochannel</code> attribute. When your audio is placed into a channel, it is generally paused (or interrupted) by audio in a higher priority channel being played. Audio in the least important channel — <code>normal</code> — is also paused by its app being put into the background (this is not the case with the other channels). The audio channels are as follows:</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Channel name</th>
- <th scope="col">importance</th>
- <th scope="col">Used for</th>
- <th scope="col">App permission level</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>normal</td>
- <td>1</td>
- <td>UI sounds, app and web content</td>
- <td>Normal</td>
- </tr>
- <tr>
- <td>content</td>
- <td>2</td>
- <td>Music, radio, video</td>
- <td>Normal</td>
- </tr>
- <tr>
- <td>notification</td>
- <td>3</td>
- <td>New email, incoming SMS</td>
- <td>Privileged</td>
- </tr>
- <tr>
- <td>alarm</td>
- <td>4</td>
- <td>Alarm clock, calendar alarms</td>
- <td>Privileged</td>
- </tr>
- <tr>
- <td>ringer</td>
- <td>5</td>
- <td>Incoming phone calls</td>
- <td>Certified</td>
- </tr>
- <tr>
- <td>telephony</td>
- <td>6</td>
- <td>Ongoing phone calls, VOIP calls</td>
- <td>Certified</td>
- </tr>
- <tr>
- <td>publicnotification</td>
- <td>7</td>
- <td>Forced camera shutter sounds</td>
- <td>Certified</td>
- </tr>
- </tbody>
-</table>
-
-<p>Each channel has a separate mute and volume setting, to provide more granular control over the different parts of audio on your device. These are accessed using the <a href="/en-US/docs/Web/API/MozAudioChannelManager" title="The documentation about this has not yet been written; please consider contributing!"><code>mozAudioChannelManager</code></a> object via the <a href="/en-US/docs/Web/API/Navigator/mozAudioChannelManager" title="The documentation about this has not yet been written; please consider contributing!"><code>navigator.mozAudioChannelManager</code></a> property.</p>
-
-<div class="note">
-<p><strong>Note</strong>: If you have two apps playing audio in the content channel, only the one in the foreground can play audio, while the other is interrupted. When the foreground app is put into the background with audio playing, it will not be muted, as per normal "content" behaviour.</p>
-</div>
-
-<div class="note">
-<p><strong>Note</strong>: Find more out about how to use the AudioChannels API in our <a href="/en-US/docs/Web/API/AudioChannels_API/Using_the_AudioChannels_API">Using the AudioChannels API</a> guide.</p>
-</div>
-
-<h2 id="AudioChannels_interfaces">AudioChannels interfaces</h2>
-
-<dl>
- <dt><a href="/en-US/docs/Web/API/AudioChannelManager" title="The documentation about this has not yet been written; please consider contributing!"><code>AudioChannelManager</code></a></dt>
- <dd>Includes some features for managing your device's audio channels, including setting what channel's volume to affect when the volume buttons are pressed inside a particular app.</dd>
- <dt><a href="/en-US/docs/Web/API/HTMLMediaElement" title="The HTMLMediaElement interface adds to HTMLElement the properties and methods needed to support basic media-related capabilities that are common to audio and video."><code>HTMLMediaElement</code></a> and <a href="/en-US/docs/Web/API/AudioContext" title="The AudioContext interface represents an audio-processing graph built from audio modules linked together, each represented by an AudioNode. An audio context controls both the creation of the nodes it contains and the execution of the audio processing, or decoding. You need to create an AudioContext before you do anything else, as everything happens inside a context."><code>AudioContext</code></a> extensions</dt>
- <dd><code>HTMLMediaElement</code> and <code>AudioContext</code> are extended with some proprietary features for controlling audio channels, including setting what audio channel the media is in, and events that fire when the audio is interrupted, and resumes playing.</dd>
- <dt><a href="/en-US/docs/Web/API/Using_the_Browser_API">Browser API</a> extensions</dt>
- <dd>The Browser API will also be including some audio channels features, for putting audio content inside a browser instance into audio channels, controlling its volume, etc., but it doesn't look like these have yet been implemented. This should occur soon.</dd>
-</dl>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/Apps/Build/App_permissions">App permissions for Firefox OS</a></li>
- <li><a href="/en-US/docs/Web/API/AudioChannels_API/Using_the_AudioChannels_API">Using the Audio Channels API</a></li>
- <li><a href="/en-US/docs/Web/API/Navigator/mozAudioChannelManager" title="The documentation about this has not yet been written; please consider contributing!"><code>navigator.mozAudioChannelManager</code></a></li>
- <li><a href="/en-US/docs/Web/API/HTMLMediaElement" title="The HTMLMediaElement interface adds to HTMLElement the properties and methods needed to support basic media-related capabilities that are common to audio and video."><code>HTMLMediaElement</code></a></li>
-</ul>
diff --git a/files/ko/web/api/mozmmsevent/index.html b/files/ko/web/api/mozmmsevent/index.html
deleted file mode 100644
index 6a3975d40b..0000000000
--- a/files/ko/web/api/mozmmsevent/index.html
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: MozMmsEvent
-slug: Web/API/MozMmsEvent
-tags:
- - Firefox OS
- - Mobile
- - Non-standard
- - Obsolete
- - Reference
- - WebSMS
-translation_of: Archive/B2G_OS/API/MozMmsEvent
----
-<p>{{ Apiref() }}</p>
-
-<div class="warning">
-<p style="text-align: center;">This API is available on <a href="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> for <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security#App_Types">internal applications</a> only.</p>
-</div>
-
-<h2 id="요약">요약</h2>
-
-<p>DOM <code>MozMmsEvent</code> 는 WebSMS MMS 메시지와 관련된 이벤트 객체이다.</p>
-
-<h2 id="속성">속성</h2>
-
-<dl>
- <dt>{{domxref("MozMmsEvent.message")}} {{readonlyinline}}</dt>
- <dd>해당 이벤트에 의해 발생된 {{ domxref("MozMmsMessage") }} 이다.</dd>
-</dl>
-
-<p><code>MozM</code><code>msEvent</code> 는 또한 {{domxref("Event")}} 의 속성을 상속받는다.</p>
-
-<p>{{page("/en-US/docs/Web/API/Event","Properties")}}</p>
-
-<h2 id="메소드">메소드</h2>
-
-<p><code>MozMmsEvent</code> 는 {{domxref("Event")}} 의 메소드를 상속받는다.</p>
-
-<p>{{page("/en-US/docs/Web/API/Event","Methods")}}</p>
-
-<h2 id="이벤트">이벤트</h2>
-
-<p><code>MozMmsEvent</code> 는 다음과 같은 이벤트들에 사용된다:</p>
-
-<dl>
- <dt>{{event("deliverysuccess")}}</dt>
- <dd>MMS가 수신자에게 전달되었을 때 발생한다.</dd>
- <dt>{{event("received")}}</dt>
- <dd>MMS를 받았을 때 발생한다.</dd>
- <dt>{{event("sent")}}</dt>
- <dd>MMS를 보냈을 때 발생한다.</dd>
-</dl>
-
-<h2 id="명세">명세</h2>
-
-<p>이 API는 비 표준 스펙의 구현체이다. 그러나 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있다.</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="같이_보기">같이 보기</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozSms") }}</li>
- <li>{{ domxref("MozMobileMessageManager") }}</li>
- <li>{{ domxref("MozMmsMessage") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozmmsmessage/index.html b/files/ko/web/api/mozmmsmessage/index.html
deleted file mode 100644
index 1d00b8050d..0000000000
--- a/files/ko/web/api/mozmmsmessage/index.html
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: MozMmsMessage
-slug: Web/API/MozMmsMessage
-tags:
- - Firefox OS
- - Mobile
- - Non-standard
- - Obsolete
- - Reference
- - WebSMS
-translation_of: Archive/B2G_OS/API/MozMmsMessage
----
-<div>{{APIRef("Mobile Messaging API")}}</div>
-
-<div class="warning">
-<p style="text-align: center;">This API is available on <a href="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> for <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security#App_Types">internal applications</a> only.</p>
-</div>
-
-<h2 id="요약">요약</h2>
-
-<p>DOM <code>MozMmsMessage</code> 객체는 MMS 메시지를 나타내며 발신자, 수신자, 본문, 첨부 파일, 날짜와 같은 모든 정보를 가지고 있다.</p>
-
-<h2 id="속성">속성</h2>
-
-<dl>
- <dt> </dt>
- <dt>{{domxref("MozMmsMessage.type")}} {{readonlyinline}}</dt>
- <dd><code>mms라는 값을 가지는 문자열이다.</code></dd>
- <dt>{{domxref("MozMmsMessage.id")}} {{readonlyinline}}</dt>
- <dd>메시지의 id를 나타내는 숫자를 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.threadId")}} {{readonlyinline}}</dt>
- <dd>메시지 일부의 스레드의 id를 나타내는 숫자를 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.subject")}} {{readonlyinline}}</dt>
- <dd>메시지의 제목을 나타내는 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.smil")}} {{readonlyinline}}</dt>
- <dd>메시지의 SMIL 콘텐츠를 나타내는 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.attachments")}} {{readonlyinline}}</dt>
- <dd>SMIL 콘텐츠에 필요한 첨부 파일을 나타내는 객체의 배열을 반환한다. 이 객체들은 <code>id</code>, <code>location,</code> <code>content</code>(<a href="https://developer.mozilla.org/en-US/docs/Web/API/Blob" title="/en-US/docs/Web/API/Blob"><code>Blob</code></a>)를 포함하고 있다.</dd>
- <dt>{{domxref("MozMmsMessage.expiryDate")}} {{readonlyinline}}</dt>
- <dd>MMS를 수동으로 다운로드 받게 되는 만기일을 나타내는 <code><a href="/en/JavaScript/Reference/Global_Objects/Date" title="Date">Date</a></code> 객체를 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.delivery")}} {{readonlyinline}}</dt>
- <dd><code>not-download</code>, <code>received</code>, <code>sending</code>, <code>sent</code>, <code>error</code> 중 하나의 값을 가지게 되는 {{ domxref("DOMString") }} 의 배열을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.deliveryStatus")}} {{readonlyinline}}</dt>
- <dd><code>delivery</code> 속성 값에 따른 상태를 나타내는 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.read")}} {{readonlyinline}}</dt>
- <dd>메시지를 읽었는지 읽지 않았는지를 가리키는 Boolean을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.receivers")}} {{readonlyinline}}</dt>
- <dd>각 수신자의 이름을 가진 {{ domxref("DOMString") }} 의 배열을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.sender")}} {{readonlyinline}}</dt>
- <dd>발신자의 이름을 가진 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozMmsMessage.timestamp")}} {{readonlyinline}}</dt>
- <dd>메시지의 타임스탬프인 <code><a href="/en/JavaScript/Reference/Global_Objects/Date" title="Date">Date</a></code> 객체를 반환한다.</dd>
-</dl>
-
-<h2 id="명세">명세</h2>
-
-<p>이 API는 비 표준 스펙의 구현체이다. 그러나 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있다.</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="같이_보기">같이 보기</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozMobileMessage") }}</li>
- <li>{{ domxref("MozMobileMessageManager") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozmobilemessagemanager/index.html b/files/ko/web/api/mozmobilemessagemanager/index.html
deleted file mode 100644
index 6b301fe71b..0000000000
--- a/files/ko/web/api/mozmobilemessagemanager/index.html
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: MozMobileMessageManager
-slug: Web/API/MozMobileMessageManager
-tags:
- - Firefox OS
- - Mobile
- - Obsolete
- - Reference
- - WebSMS
-translation_of: Archive/B2G_OS/API/MozMobileMessageManager
----
-<div>{{APIRef("Mobile Messaging API")}}</div>
-
-<div class="warning">
-<p style="text-align: center;">This API is available on <a href="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> for <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security#App_Types">internal applications</a> only.</p>
-</div>
-
-<h2 id="요약">요약</h2>
-
-<p>기기에서 WebSMS를 사용하여 MMS와 SMS 메시지 전송과 관리를 할 수 있는 기능을 제공한다.</p>
-
-<h2 id="이벤트_핸들러">이벤트 핸들러</h2>
-
-<dl>
- <dt>{{domxref("MozMobileMessageManager.ondeliveryerror")}}</dt>
- <dd>{{event("deliveryerror")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 MMS 또는 SMS가 수취인에게 전달되지 않았을 때 발생한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.ondeliverysuccess")}}</dt>
- <dd>{{event("deliverysuccess")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 MMS 또는 SMS가 수취인에게 전달되었을 때 발생한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.onreceived")}}</dt>
- <dd>{{event("received")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 MMS 또는 SMS를 받았을 때 발생한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.onretrieving")}}</dt>
- <dd>{{event("retrieving")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 검색 단계의 시작에 MMS 또는 SMS가 진입했을 때 발생한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.onsent")}}</dt>
- <dd>{{event("sent")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 MMS 또는 SMS가 보내졌을 때 발생한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.onsending")}}</dt>
- <dd>{{event("sending")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 전송 단계의 시작에 MMS 또는 SMS가 진입했을 때 발생한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.onfailed")}}</dt>
- <dd>{{event("failed")}} 이벤트에 대한 핸들러; {{ domxref("MozMmsEvent") }} 는 SMS 전송이 실패했을 때 발생한다.</dd>
-</dl>
-
-<h2 id="메소드">메소드</h2>
-
-<dl>
- <dt>{{domxref("MozMobileMessageManager.delete","MozMobileMessageManager.delete(param)")}}</dt>
- <dd>메시지를 삭제하고 {{ domxref("DOMRequest") }} 객체를 반환한다<code> (DOMRequest.result</code>는 메시지가 삭제되었는지 아닌지를 반영하는 Boolean 값이다). 메시지 <code>id</code>, {{ domxref("MozSmsMessage") }} 객체 또는 {{ domxref("MozMmsMessage") }} 객체가 파라미터로 사용된다.</dd>
- <dt>{{domxref("MozMobileMessageManager.getMessage()","MozSmsManager.getMessage(id)")}}</dt>
- <dd>해당 <code>id에 대한 메시지를 받아서 </code>{{ domxref("DOMRequest") }} 객체를 반환한다. 이 객체의 <code>DOMRequest.result</code>는 {{ domxref("MozSmsMessage") }} 이다.</dd>
- <dt>{{domxref("MozMobileMessageManager.getMessages()","MozSmsManager.getMessages(filter, reverseOrder)")}}</dt>
- <dd>여러 개의 메시지를 받는다. {{ domxref("MozSmsFilter") }} 객체를 사용하여 필터링이 가능하고 두번째 파라미터 Boolean 값에 따라 메시지의 순서를 거꾸로 바꿀 수도 있다. {{ domxref("DOMCursor") }} 를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.getSegmentInfoForText()","MozMobileMessageManager.getSegmentInfoForText(text)")}}</dt>
- <dd>주어진 문자(보통 SMS당 160 글자)에 대한 멀티 파트 SMS를 만들기 위해 필요한 정보를 가진 {{domxref("MozSmsSegmentInfo")}} 객체를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.markMessageRead()","MozMobileMessageManager.markMessageRead(id, isRead)")}}</dt>
- <dd>해당 <code>id</code> 의 메시지를 Boolean <code>isRead</code> 값에 따라 읽음 또는 읽지 않음으로 표시한다. {{ domxref("DOMRequest") }} 객체를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.send()","MozMobileMessageManager.send(number, message)")}}</dt>
- <dd>해당 전화번호에 메시지를 전송한다. 만약 <code>number</code>가 {{ domxref("DOMString") }} (한 개의 전화번호) 라면 {{ domxref("DOMRequest") }} 객체를 반환한다. 만약 <code>number</code>가 {{ domxref("DOMString") }} 객체의 배열(여러 개의 전화번호)이라면 {{ domxref("DOMRequest") }} 객체의 배열을 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.sendMMS()","MozMobileMessageManager.sendMMS(param)")}}</dt>
- <dd>수신자 목록에 MMS를 전송한다. {{ domxref("DOMRequest") }} 객체를 반환한다.<br>
- param 객체는 다음과 같은 4개의 속성을 가지고 있는 일반 JavaScript 객체이다:<br>
- <code>receivers</code>: 문자열 배열, 각 문자열은 수신자의 전화번호를 나타낸다.<br>
- <code>subject</code>: MMS의 제목을 나타내는 문자열이다.<br>
- <code>smil</code>: MMS를 정의하는 SMIL 문서의 문자열 버전이다.<br>
- <code>attachments</code>: SMIL에 의해 사용되는 첨부 파일 객체의 배열이다. 이 객체는 <code>id</code>, <code>location</code>, <code>content</code> ({{domxref("Blob")}})를 포함하고 있다.</dd>
- <dt>{{domxref("MozMobileMessageManager.getThreads()")}}</dt>
- <dd>{{domxref("MozMobileMessageThread")}} 의 목록을 받는다. {{ domxref("DOMCursor") }} 를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageManager.retrieveMMS()","MozMobileMessageManager.retrieveMMS(id)")}}</dt>
- <dd>해당 <code>id의 메시지를 받아 </code>{{ domxref("DOMRequest") }} 를 반환한다. 이 객체의 <code>DOMRequest.result</code> 는 {{ domxref("MozMmsMessage") }} 이다.</dd>
-</dl>
-
-<p><code>MozMobileMessageManager</code> 또한 {{domxref("EventTarget")}} 의 메소드를 상속받는다.</p>
-
-<p>{{Page("/en-US/docs/Web/API/EventTarget","Methods")}}</p>
-
-<h2 id="명세">명세</h2>
-
-<p>이 API는 비 표준 스펙의 구현체이다. 하지만 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있다.</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="같이_보기">같이 보기</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozMobileMessage") }}</li>
- <li>{{ domxref("MozMmsEvent") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozmobilemessagethread/index.html b/files/ko/web/api/mozmobilemessagethread/index.html
deleted file mode 100644
index 4e8e8048a5..0000000000
--- a/files/ko/web/api/mozmobilemessagethread/index.html
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: MozMobileMessageThread
-slug: Web/API/MozMobileMessageThread
-tags:
- - Non-standard
-translation_of: Archive/B2G_OS/API/MozMobileMessageThread
----
-<p>{{ ApiRef() }}</p>
-
-<p>{{ non-standard_header() }}</p>
-
-<h2 id="요약">요약</h2>
-
-<p>DOM <code>MozMobileMessageThread</code> 객체는 메시지의 스레드를 나타낸다.</p>
-
-<h2 id="속성">속성</h2>
-
-<dl>
- <dt>{{domxref("MozMobileMessageThread.id")}} {{readonlyinline}}</dt>
- <dd>스레드의 id를 나타내는 숫자를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageThread.body")}} {{readonlyinline}}</dt>
- <dd>스레드의 마지막 메시지의 본문을 나타내는 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageThread.unreadCount")}} {{readonlyinline}}</dt>
- <dd>스레드에 있는 총 읽지 않은 메시지의 개수를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageThread.participants")}} {{readonlyinline}}</dt>
- <dd>스레드에 각 참가자의 주소를 나타내는 {{ domxref("DOMString") }} 의 배열을 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageThread.timestamp")}} {{readonlyinline}}</dt>
- <dd>스레드의 마지막 메시지의 타임스탬프를 나타내는 <code><a href="/en/JavaScript/Reference/Global_Objects/Date" title="Date">Date</a></code> 객체를 반환한다.</dd>
- <dt>{{domxref("MozMobileMessageThread.lastMessageType")}} {{readonlyinline}}</dt>
- <dd><code>sms</code> 또는 <code>mms 값을 가지는 </code>{{ domxref("DOMString") }} 을 반환한다.</dd>
-</dl>
-
-<h2 id="참고_자료">참고 자료</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozMobileMessage") }}</li>
- <li>{{ domxref("MozMobileMessageManager") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozsmsevent/index.html b/files/ko/web/api/mozsmsevent/index.html
deleted file mode 100644
index 14a7f48d51..0000000000
--- a/files/ko/web/api/mozsmsevent/index.html
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: MozSmsEvent
-slug: Web/API/MozSmsEvent
-translation_of: Archive/B2G_OS/API/MozSmsEvent
----
-<p>{{ Apiref() }}</p>
-<p>{{ non-standard_header() }}</p>
-<p>{{ B2GOnlyHeader2('certified') }}</p>
-<h2 id="요약">요약</h2>
-<p>DOM <code>MozSmsEvent</code> 는 WebSMS 문자 메시지와 관련된 이벤트 객체이다.</p>
-<h2 id="속성">속성</h2>
-<dl>
- <dt>
- {{domxref("MozSmsEvent.message")}} {{readonlyinline}}</dt>
- <dd>
- 해당 이벤트에 의해 발생된 {{ domxref("MozSmsMessage") }} 이다.</dd>
-</dl>
-<p><code>MozSmsEvent</code> 는 또한 {{domxref("Event")}} 의 속성들을 상속받는다.</p>
-<p>{{page("/en-US/docs/Web/API/Event","Properties")}}</p>
-<h2 id="메소드">메소드</h2>
-<p><code>MozSmsEvent</code> 는 {{domxref("Event")}} 의 메소드들을 상속받는다.</p>
-<p>{{page("/en-US/docs/Web/API/Event","Methods")}}</p>
-<h2 id="이벤트">이벤트</h2>
-<p><code>MozSmsEvent</code> 는 다음과 같은 이벤트들에 사용된다:</p>
-<dl>
- <dt>
- {{event("deliverysuccess")}}</dt>
- <dd>
- SMS가 수신자에게 전달되었을 때 발생한다.</dd>
- <dt>
- {{event("received")}}</dt>
- <dd>
- SMS를 받았을 때 발생한다.</dd>
- <dt>
- {{event("sent")}}</dt>
- <dd>
- SMS를 보냈을 때 발생한다.</dd>
-</dl>
-<h2 id="스펙">스펙</h2>
-<p>이 API는 비 표준 스펙의 구현체입니다. 하지만 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있습니다.</p>
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-<h2 id="브라우저_호환성">브라우저 호환성</h2>
-<p>당연하게도, 모바일 브라우저를 주로 지원할 것으로 예상됩니다.</p>
-<p>{{ CompatibilityTable() }}</p>
-<div id="compat-desktop">
- <table class="compat-table">
- <tbody>
- <tr>
- <th>Feature</th>
- <th>Chrome</th>
- <th>Firefox (Gecko)</th>
- <th>Internet Explorer</th>
- <th>Opera</th>
- <th>Safari</th>
- </tr>
- <tr>
- <td>Basic support</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- </tr>
- </tbody>
- </table>
-</div>
-<div id="compat-mobile">
- <table class="compat-table">
- <tbody>
- <tr>
- <th>Feature</th>
- <th>Android</th>
- <th>Firefox Mobile (Gecko)</th>
- <th>IE Mobile</th>
- <th>Opera Mobile</th>
- <th>Safari Mobile</th>
- </tr>
- <tr>
- <td>Basic support</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatGeckoMobile("12.0") }} {{property_prefix("Moz")}}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- </tr>
- </tbody>
- </table>
-</div>
-<h2 id="참고_자료">참고 자료</h2>
-<ul>
- <li>{{ domxref("window.navigator.mozSms") }}</li>
- <li>{{ domxref("MozSmsManager") }}</li>
- <li>{{ domxref("MozSmsMessage") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozsmsfilter/index.html b/files/ko/web/api/mozsmsfilter/index.html
deleted file mode 100644
index 001d55e2a8..0000000000
--- a/files/ko/web/api/mozsmsfilter/index.html
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: MozSmsFilter
-slug: Web/API/MozSmsFilter
-translation_of: Archive/B2G_OS/API/MozSmsFilter
----
-<p>{{ Apiref() }}</p>
-<p>{{ non-standard_header() }}</p>
-<p>{{ B2GOnlyHeader2('certified') }}</p>
-<h2 id="요약">요약</h2>
-<p>DOM <code>MozSmsFilter</code> 인터페이스는 {{ domxref("SmsMessage") }} 객체들을 필터링하기 위한 방법을 제공합니다.</p>
-<h2 id="속성">속성</h2>
-<dl>
- <dt>
- {{domxref("MozSmsFilter.startDate")}}</dt>
- <dd>
- 메시지를 필터링하기 위한 시작일을 나타내는 <a href="/en/JavaScript/Reference/Global_Objects/Date" title="Date"><code>Date</code></a> 이다.</dd>
- <dt>
- {{domxref("MozSmsFilter.endDate")}}</dt>
- <dd>
- 메시지를 필터링하기 위한 종료일을 나타내는 <a href="/en/JavaScript/Reference/Global_Objects/Date" title="Date"><code>Date</code></a> 이다.</dd>
- <dt>
- {{domxref("MozSmsFilter.numbers")}}</dt>
- <dd>
- 전화번호로 필터링하기 위한 {{ domxref("DOMString") }} 의 배열이다.</dd>
- <dt>
- {{domxref("MozSmsFilter.delivery")}}</dt>
- <dd>
- 메시지를 전달 상태에 따라 필터링하기 위해 "sent"와 "received" 값을 가지게 되는 {{ domxref("DOMString") }} 이다.</dd>
- <dt>
- {{domxref("MozSmsFilter.read")}}</dt>
- <dd>
- 메시지를 읽었는지 읽지 않았는지를 필터링하는 Boolean 이다.</dd>
- <dt>
- {{domxref("MozSmsFilter.threadid")}}</dt>
- <dd>
- 스레드 id를 나타내는 숫자이다.</dd>
-</dl>
-<h2 id="스펙">스펙</h2>
-<p>이 API는 비 표준 스펙의 구현체입니다. 하지만 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있습니다.</p>
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-<h2 id="브라우저_호환성">브라우저 호환성</h2>
-<p>당연하게도, 모바일 브라우저를 주로 지원할 것으로 예상됩니다.</p>
-<p>{{ CompatibilityTable() }}</p>
-<div id="compat-desktop">
- <table class="compat-table">
- <tbody>
- <tr>
- <th>Feature</th>
- <th>Chrome</th>
- <th>Firefox (Gecko)</th>
- <th>Internet Explorer</th>
- <th>Opera</th>
- <th>Safari</th>
- </tr>
- <tr>
- <td>Basic support</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- </tr>
- </tbody>
- </table>
-</div>
-<div id="compat-mobile">
- <table class="compat-table">
- <tbody>
- <tr>
- <th>Feature</th>
- <th>Android</th>
- <th>Firefox Mobile (Gecko)</th>
- <th>IE Mobile</th>
- <th>Opera Mobile</th>
- <th>Safari Mobile</th>
- </tr>
- <tr>
- <td>Basic support</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatGeckoMobile("12.0") }} {{property_prefix("Moz")}}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- <td>{{ CompatNo() }}</td>
- </tr>
- </tbody>
- </table>
-</div>
-<h2 id="참고_자료">참고 자료</h2>
-<ul>
- <li>{{ domxref("window.navigator.mozSms") }}</li>
- <li>{{ domxref("MozSmsManager") }}</li>
- <li>{{ domxref("MozSmsMessage") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozsmsmanager/index.html b/files/ko/web/api/mozsmsmanager/index.html
deleted file mode 100644
index bfea424be7..0000000000
--- a/files/ko/web/api/mozsmsmanager/index.html
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: MozSmsManager
-slug: Web/API/MozSmsManager
-tags:
- - Firefox OS
- - Mobile
- - Non-standard
- - Obsolete
- - Reference
- - WebSMS
-translation_of: Archive/B2G_OS/API/MozSmsManager
----
-<div>{{APIRef("Mobile Messaging API")}}</div>
-
-<div class="warning">
-<p style="text-align: center;">This API is available on <a href="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> for <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security#App_Types">internal applications</a> only.</p>
-</div>
-
-<div class="note">
-<p><strong>Note:</strong> As of <span title="(Firefox 25.0 / Thunderbird 25.0 / SeaMonkey 2.22)">Gecko 25.0</span>, this interface has been removed in favor of <a href="/en-US/docs/Web/API/MozMobileMessageManager" title="The documentation about this has not yet been written; please consider contributing!"><code>MozMobileMessageManager</code></a>.</p>
-</div>
-
-<h2 id="요약">요약</h2>
-
-<p>기기에서 WebSMS를 사용하여 SMS 메시지 전송과 관리를 할 수 있는 기능을 제공한다.</p>
-
-<h2 id="이벤트_핸들러">이벤트 핸들러</h2>
-
-<dl>
- <dt>{{domxref("MozSmsManager.ondeliveryerror")}}</dt>
- <dd>{{event("deliveryerror")}} 이벤트에 대한 핸들러; 이 {{ domxref("MozSmsEvent") }} 는 SMS가 수취인에게 전달되지 않았을 때 발생한다.</dd>
- <dt>{{domxref("MozSmsManager.ondeliverysuccess")}}</dt>
- <dd>{{event("deliverysuccess")}} 이벤트에 대한 핸들러; 이 {{ domxref("MozSmsEvent") }} 는 SMS가 수취인에게 전달되었을 때 발생한다.</dd>
- <dt>{{domxref("MozSmsManager.onreceived")}}</dt>
- <dd>{{event("received")}} 이벤트에 대한 핸들러; 이 {{ domxref("MozSmsEvent") }} 는 SMS를 받았을 때 발생한다..</dd>
- <dt>{{domxref("MozSmsManager.onsent")}}</dt>
- <dd>{{event("sent")}} 이벤트에 대한 핸들러; 이 {{ domxref("MozSmsEvent") }} 는 SMS가 보내졌을 때 발생한다.</dd>
- <dt>{{domxref("MozSmsManager.onsending")}}</dt>
- <dd>{{event("sending")}} 이벤트에 대한 핸들러; 이 {{ domxref("MozSmsEvent") }} 는 전송 단계의 시작에 SMS가 진입했을 때 발생한다.</dd>
- <dt>{{domxref("MozSmsManager.onfailed")}}</dt>
- <dd>{{event("failed")}} 이벤트에 대한 핸들러; 이 {{ domxref("MozSmsEvent") }} 는 SMS 전송이 실패했을 때 발생한다.</dd>
-</dl>
-
-<h2 id="메소드">메소드</h2>
-
-<dl>
- <dt>{{domxref("MozSmsManager.delete","MozSmsManager.delete(param)")}}</dt>
- <dd>메시지를 삭제하고 {{ domxref("DOMRequest") }} 객체를 반환한다 (<code>DOMRequest.result는 메시지가 삭제되었는지 아닌지를 반영하는 Boolean 값이다).</code> 메시지 <code>id</code> 또는 {{ domxref("MozSmsMessage") }} 객체가 파라미터로 사용된다.</dd>
- <dt>{{domxref("MozSmsManager.getMessage()","MozSmsManager.getMessage(id)")}}</dt>
- <dd>해당<code> id에 대한 메시지를 받아서 </code>{{ domxref("DOMRequest") }} 객체를 반환한다.  <code>이 객체의 DOMRequest.result는</code> {{ domxref("MozSmsMessage") }} 이다.</dd>
- <dt>{{domxref("MozSmsManager.getMessages()","MozSmsManager.getMessages(filter, reverseOrder)")}}</dt>
- <dd>여러 개의 메시지를 받는다. {{ domxref("MozSmsFilter") }} 객체를 사용하여 필터링이 가능하고 두번째 파라미터 boolean 값에 따라 순서를 거꾸로 바꿀 수도 있다. {{ domxref("DOMCursor") }} 를 반환한다.</dd>
- <dt>{{domxref("MozSmsManager.getSegmentInfoForText()","MozSmsManager.getSegmentInfoForText(text)")}}</dt>
- <dd>주어진 문자(보통 SMS 당 160 글자)에 대한 멀티 파트 SMS를 만들기 위해 필요한 정보를 가진 {{domxref("MozSmsSegmentInfo")}} 객체를 반환한다.</dd>
- <dt>{{domxref("MozSmsManager.markMessageRead()","MozSmsManager.markMessageRead(id, isRead)")}}</dt>
- <dd>해당 <code>id의 메시지를 </code>Boolean <code>isRead 값에 따라 읽음 또는 읽지 않음으로 표시한다. </code>{{ domxref("DOMRequest") }}<code> 객체를 반환한다.</code></dd>
- <dt>{{domxref("MozSmsManager.send()","MozSmsManager.send(number, message)")}}</dt>
- <dd>해당 <code>전화번호</code>에 메시지를 전송한다. 만약 <code>number가 </code>{{ domxref("DOMString") }} (한 개의 전화번호)라면 {{ domxref("DOMRequest") }} 객체를 반환한다. 만약 <code>number</code>가 {{ domxref("DOMString") }} 객체의 배열(여러 개의 전화번호)라면 {{ domxref("DOMRequest") }} 객체의 배열을 반환한다.</dd>
- <dt>{{domxref("MozSmsManager.getThreads()")}}</dt>
- <dd>{{domxref("MozMobileMessageThread")}}의 목록을 받는다. {{ domxref("DOMCursor") }} 를 반환된다.</dd>
-</dl>
-
-<p><code>MozSmsManager</code> 는 또한 {{domxref("EventTarget")}} 의 메소드를 상속받는다.</p>
-
-<p>{{Page("/en-US/docs/Web/API/EventTarget","Methods")}}</p>
-
-<h2 id="명세">명세</h2>
-
-<p>이 API는 비 표준 스펙의 구현체입니다. 하지만 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있습니다.</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="참고_자료">참고 자료</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozSms") }}</li>
- <li>{{ domxref("MozSmsEvent") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozsmsmessage/index.html b/files/ko/web/api/mozsmsmessage/index.html
deleted file mode 100644
index 7918a44209..0000000000
--- a/files/ko/web/api/mozsmsmessage/index.html
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: MozSmsMessage
-slug: Web/API/MozSmsMessage
-tags:
- - Non-standard
-translation_of: Archive/B2G_OS/API/MozSmsMessage
----
-<p>{{ ApiRef() }}</p>
-
-<p>{{ non-standard_header() }}</p>
-
-<p>{{ B2GOnlyHeader2('certified') }}</p>
-
-<h2 id="요약">요약</h2>
-
-<p>DOM <code>MozSmsMessage</code> 객체는 SMS 문자 메시지를 나타내며 발신자, 수신자, 본문, 날짜와 같은 모든 정보를 가지고 있다.</p>
-
-<h2 id="속성">속성</h2>
-
-<dl>
- <dt>{{domxref("MozSmsMessage.type")}} {{readonlyinline}}</dt>
- <dd><code>sms라는 값을 가지는 문자열이다</code>.</dd>
- <dt>{{domxref("MozSmsMessage.id")}} {{readonlyinline}}</dt>
- <dd>메시지의 id를 나타내는 숫자를 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.threadId")}} {{readonlyinline}}</dt>
- <dd>메시지 일부의 스레드의 id를 나타내는 숫자를 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.body")}} {{readonlyinline}}</dt>
- <dd>메시지의 본문을 나타내는 {{ domxref("DOMString") }} 를 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.delivery")}} {{readonlyinline}}</dt>
- <dd><code>received</code>, <code>sending</code>, <code>sent</code>, <code>error</code> 중 하나의 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.deliveryStatus")}} {{readonlyinline}}</dt>
- <dd><code>delivery 속성 값에 따라 다음과 같은 </code>{{ domxref("DOMString") }} 을 반환한다:<br>
- * <code>received</code> : <code>success</code><br>
- * <code>sending </code> : <code>pending</code> 또는 <code>not-applicable</code> (만약 메시지가 상태 보고 요청없이 전송되었다면)<br>
- * <code>sent    </code> : <code>pending</code>, <code>success</code>, <code>error</code> 또는 <code>not-applicable</code> (만약 메시지가 상태 보고 요청없이 전송되었다면)<br>
- * <code>error   </code> : <code>error</code></dd>
- <dt>{{domxref("MozSmsMessage.read")}} {{readonlyinline}}</dt>
- <dd>메시지를 읽었는지 읽지 않았는지를 가리키는 Boolean을 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.receiver")}} {{readonlyinline}}</dt>
- <dd>수신자 이름을 나타내는 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.sender")}} {{readonlyinline}}</dt>
- <dd>발신자 이름을 나타내는 {{ domxref("DOMString") }} 을 반환한다.</dd>
- <dt>{{domxref("MozSmsMessage.timestamp")}} {{readonlyinline}}</dt>
- <dd>메시지의 타임스탬프인 <code><a href="/en/JavaScript/Reference/Global_Objects/Date" title="Date">Date</a> 객체를 반환한다.</code></dd>
- <dt>{{domxref("MozSmsMessage.messageClass")}} {{readonlyinline}}</dt>
- <dd><code>normal</code>, <code>class-0</code>, <code>class-1</code>, <code>class-2</code>, <code>class-3</code> 중 하나의 {{ domxref("DOMString") }} 을 반환한다.</dd>
-</dl>
-
-<h2 id="참고_자료">참고 자료</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozSms") }}</li>
- <li>{{ domxref("MozSmsManager") }}</li>
-</ul>
diff --git a/files/ko/web/api/mozsmssegmentinfo/index.html b/files/ko/web/api/mozsmssegmentinfo/index.html
deleted file mode 100644
index 02f324b453..0000000000
--- a/files/ko/web/api/mozsmssegmentinfo/index.html
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: MozSmsSegmentInfo
-slug: Web/API/MozSmsSegmentInfo
-tags:
- - Non-standard
-translation_of: Archive/B2G_OS/API/MozSmsSegmentInfo
----
-<p>{{ ApiRef() }}</p>
-
-<p>{{ non-standard_header() }}</p>
-
-<h2 id="요약">요약</h2>
-
-<p>DOM <code>MozSmsSegmentInfo</code> 인터페이스는 문자가 자동으로 어떻게 세그멘트로 나누어지는에 관한 정보를 제공합니다. 각 세그먼트는 멀티 파트 SMS 메시지의 단일 SMS를 나타냅니다.</p>
-
-<p><code>MozSmsSegmentInfo</code> 인터페이스는 직접적으로 인스턴스화 될 수 없습니다; 각 객체를 얻기 위해서는 {{domxref("MozSmsManager.getSegmentInfoForText()")}} 메소드를 사용하십시오.</p>
-
-<h2 id="속성">속성</h2>
-
-<dl>
- <dt>{{domxref("MozSmsSegmentInfo.segments")}} {{readonlyinline}}</dt>
- <dd>입력 문자열에 대한 총 세그먼트의 개수이다.</dd>
- <dt>{{domxref("MozSmsSegmentInfo.charsPerSegment")}} {{readonlyinline}}</dt>
- <dd>각 세그먼트당 사용 가능한 문자의 개수이다.</dd>
- <dt>{{domxref("MozSmsSegmentInfo.charsAvailableInLastSegment")}} {{readonlyinline}}</dt>
- <dd>마지막 세그먼트에서 사용 가능한 문자의 최대 개수이다.</dd>
-</dl>
-
-<h2 id="참고_자료">참고 자료</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>{{ domxref("window.navigator.mozSms") }}</li>
- <li>{{ domxref("MozSmsManager") }}</li>
-</ul>
diff --git a/files/ko/web/api/navigator/mozmobilemessage/index.html b/files/ko/web/api/navigator/mozmobilemessage/index.html
deleted file mode 100644
index 7645d8d833..0000000000
--- a/files/ko/web/api/navigator/mozmobilemessage/index.html
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: window.navigator.mozMobileMessage
-slug: Web/API/Navigator/mozMobileMessage
-tags:
- - Non-standard
- - Obsolete
-translation_of: Archive/B2G_OS/API/Navigator/mozMobileMessage
----
-<p>{{ ApiRef() }}</p>
-
-<p>{{ non-standard_header() }}</p>
-
-<p>{{ B2GOnlyHeader2('certified') }}</p>
-
-<h2 id="Summary" name="Summary">요약</h2>
-
-<p>{{ domxref("MozMobileMessageManager") }} 객체를 반환한다. 이 객체는 MMS와 SMS 메시지를 보내거나 받는데 사용된다.</p>
-
-<h2 id="명세">명세</h2>
-
-<p> </p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="설정_이용_가능한_환경">설정 &amp; 이용 가능한 환경</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>WebSMS는 기본적으로 비활성화 되어있습니다. <code>dom.sms.enabled 설정을 true로 지정하여야 활성화됩니다.</code></li>
- <li>WebSMS API를 사용하도록 허가된 호스트명들의 화이트 리스트(콤마로 구분)는 반드시 <code>dom.sms.whitelist 설정에 명시되어야 합니다. 이 문자열은 기본적으로 빈 문자열입니다.</code></li>
- <li>WebSMS는 오직 Firefox OS (B2G) 에 인증된 앱에서만 이용 가능합니다.</li>
- <li>MMS는 Firefox OS 1.1 부터 이용 가능합니다.</li>
-</ul>
-
-<h2 id="참고_자료">참고 자료</h2>
-
-<ul>
- <li><a href="/en-US/docs/API/WebSMS" title="/en-US/docs/API/WebSMS">WebSMS API</a></li>
- <li>{{ domxref("MozMobileMessageManager") }}</li>
- <li>{{ domxref("window.navigator.mozTelephony") }} for controlling telephone calls.</li>
- <li>{{ domxref("window.navigator.mozSms") }} for handling SMS only.</li>
-</ul>
diff --git a/files/ko/web/api/navigator/moznotification/index.html b/files/ko/web/api/navigator/moznotification/index.html
deleted file mode 100644
index 9c593ec4a1..0000000000
--- a/files/ko/web/api/navigator/moznotification/index.html
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: navigator.mozNotification
-slug: Web/API/Navigator/mozNotification
-translation_of: Archive/API/Navigator/mozNotification
----
-<div class="warning">
-<p style="text-align: center;">The support for this property as been dropped in favor of the standard {{domxref("Notification")}} constructor.</p>
-</div>
-
-<p>Provides support for creating {{ domxref("notification") }} objects, which are used to display desktop notification alerts to the user. Currently, these are only supported on Firefox Mobile and Firefox OS. See <a href="/en/DOM/Displaying_notifications" title="en/DOM/Displaying notifications">Displaying notifications</a> for an example.</p>
-
-<h2 id="Method_overview" name="Method_overview">Method overview</h2>
-
-<table class="standard-table">
- <tbody>
- <tr>
- <td><code>notification <a href="#createNotification()">createNotification</a>(in DOMString title, in DOMString description, in DOMString iconURL {{ optional_inline() }});</code></td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="Methods" name="Methods">Methods</h2>
-
-<h3 id="createNotification()" name="createNotification()">createNotification()</h3>
-
-<p>Creates and returns a notification object that can be used to display the specified message with an optional URL.</p>
-
-<pre class="eval">notification createNotification(
- in DOMString title,
- in DOMString description,
- in DOMString iconURL {{ optional_inline() }}
-);
-</pre>
-
-<h6 id="Parameters" name="Parameters">Parameters</h6>
-
-<dl>
- <dt><code>title</code></dt>
- <dd>알림 타이틀.</dd>
- <dt><code>description</code></dt>
- <dd>알림에 표시할 텍스트.</dd>
- <dt><code>iconURL</code> {{ optional_inline() }}</dt>
- <dd>A URL identifying the image to display in the notification.</dd>
-</dl>
-
-<h6 id="Return_value" name="Return_value">Return value</h6>
-
-<p>A new {{ domxref("notification") }} object.</p>
-
-<h2 id="Methods" name="Methods">Permissions</h2>
-
-<p>manifest 파일에 "desktop-notification" permission 을 추가 해야 한다.</p>
-
-<pre class="default prettyprint prettyprinted"><code><span class="str">"permissions"</span><span class="pun">:</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
- </span><span class="str">"desktop-notification"</span><span class="pun">:{}</span><span class="pln">
-</span><span class="pun">}</span></code></pre>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{ domxref("notification") }}</li>
- <li><a href="/en/DOM/Displaying_notifications" title="en/DOM/Displaying notifications">Displaying notifications</a></li>
-</ul>
diff --git a/files/ko/web/api/navigator/mozsms/index.html b/files/ko/web/api/navigator/mozsms/index.html
deleted file mode 100644
index d6c9c16983..0000000000
--- a/files/ko/web/api/navigator/mozsms/index.html
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: window.navigator.mozSms
-slug: Web/API/Navigator/mozSms
-tags:
- - API
- - Firefox OS
- - Mobile
- - Obsolete
- - Property
- - WebSMS
-translation_of: Archive/B2G_OS/API/Navigator/mozSms
----
-<p>{{APIRef("Mobile Messaging API")}}</p>
-
-<div class="blockIndicator obsolete">
-<p><strong>Obsolete since Gecko 25 (Firefox 25 / Thunderbird 25 / SeaMonkey 2.22)</strong><br>
- This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.</p>
-</div>
-
-<div class="blockIndicator warning">
-<p style="text-align: center;">This API is available on <a href="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> for <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security#App_Types">internal applications</a> only.</p>
-</div>
-
-<p><code><a href="/ko/docs/Archive/B2G_OS/API/MozSmsManager">MozSmsManager</a></code> 객체를 반환한다. 이 객체는 SMS 메시지를 보내거나 받는데 사용된다.</p>
-
-<div class="blockIndicator note">
-<p>Note: <strong>Do not use anymore! </strong>This object has been removed in favor of <a href="/en-US/docs/Archive/B2G_OS/API/Navigator/mozMobileMessage" title="Returns a MozMobileMessageManager object you can use to receive and send MMS and SMS messages."><code>Navigator.mozMobileMessage</code></a>.</p>
-</div>
-
-<h2 id="명세">명세</h2>
-
-<p>이 API는 비 표준 스펙의 구현체입니다. 하지만 W3C의 <a href="http://www.w3.org/2012/sysapps/" title="http://www.w3.org/2012/sysapps/">System Application Working Group</a>에서 논의되고 있습니다.</p>
-
-<table class="standard-table">
- <thead>
- <tr>
- <th scope="col">Specification</th>
- <th scope="col">Status</th>
- <th scope="col">Comment</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>{{SpecName('Messaging')}}</td>
- <td>{{Spec2('Messaging')}}</td>
- <td>Editor Draft (WIP).</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="설정_이용_가능한_환경">설정 &amp; 이용 가능한 환경</h2>
-
-<div id="compat-mobile"> </div>
-
-<ul>
- <li>WebSMS는 기본적으로 비활성화 되어있습니다. <code>dom.sms.enabled</code> 설정을 true로 지정하여야 활성화됩니다.</li>
- <li>WebSMS API를 사용하도록 허가된 호스트명들의 화이트 리스트(콤마로 구분)는 반드시 <code>dom.sms.whitelist 설정에 명시되어야 합니다. 이 문자열은 기본적으로 빈 문자열입니다.</code></li>
- <li>WebSMS는 오직 Firefox OS (B2G) 에 인증된 앱에서만 이용 가능합니다.</li>
-</ul>
-
-<h2 id="참고_자료">참고 자료</h2>
-
-<ul>
- <li><a href="/en-US/docs/API/WebSMS" title="/en/docs/API/WebSMS">WebSMS API</a></li>
- <li>{{ domxref("SmsManager") }}</li>
- <li>{{ domxref("window.navigator.mozTelephony") }} for controlling telephone calls.</li>
-</ul>