From 310fd066e91f454b990372ffa30e803cc8120975 Mon Sep 17 00:00:00 2001
From: Florian Merz <me@fiji-flo.de>
Date: Thu, 11 Feb 2021 12:56:40 +0100
Subject: unslug zh-cn: move

---
 files/zh-cn/chrome/index.html | 70 -------------------------------------------
 1 file changed, 70 deletions(-)
 delete mode 100644 files/zh-cn/chrome/index.html

(limited to 'files/zh-cn/chrome/index.html')

diff --git a/files/zh-cn/chrome/index.html b/files/zh-cn/chrome/index.html
deleted file mode 100644
index a40b228f6b..0000000000
--- a/files/zh-cn/chrome/index.html
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Chrome
-slug: Chrome
-tags:
-  - Toolkit API
-translation_of: Glossary/Chrome
-translation_of_original: Chrome
----
-<p><b>Chrome</b> 这个单词在 Mozilla 的技术中有着多重含义。</p>
-<dl>
-  <dt>
-    Browser chrome / Chrome</dt>
-  <dd>
-    "browser chrome" 或者直接 Chrome 可以用来指代围绕着普通网页区域的浏览器界面，它对应的词是 content ，表示网页区域.</dd>
-  <dd>
-    更通用点讲, chrome is the entirety of entities making up the user interface of a specific application or <a href="en/Extension">extension</a>.</dd>
-  <dt>
-     <code><a class="external" rel="freelink">chrome://</a></code> URL</dt>
-  <dd>
-    An URL using the <code><a class="external" rel="freelink">chrome://</a></code> protocol. Code loaded from a chrome URL has extended, or
-    <i>
-      chrome</i>
-    , privileges.</dd>
-  <dd>
-    XUL-based applications load the code for their interface from <code><a class="external" rel="freelink">chrome://</a></code> URLs.</dd>
-  <dt>
-    Chrome 特权</dt>
-  <dd>
-    拥有 chrome 特权的代码可以实现各种事情, 而普通网页中的 JS 代码则不是。</dd>
-  <dt>
-    <code>window.open</code> 方法的<code> chrome</code> 参数</dt>
-  <dd>
-    将 <a href="en/DOM/window.open#Features_requiring_privileges"><code>chrome</code> 参数传给 <code>window.open</code></a> 能够打开一个没有多余浏览器界面元素（工具栏、地址栏等）的新窗口.</dd>
-  <dt>
-    <code>chrome</code> 文件夹</dt>
-  <dd>
-    profile 根目录中的 chrome 文件夹通常是用来存放 userChrome.js 扩展需要加载的 js 脚本</dd>
-  <dt>
-    <code>-chrome</code> 命令行参数</dt>
-  <dd>
-    Starts the application and opens the specified XUL file in a top level window. E.g. <code>mozilla -chrome <a class="external" rel="freelink">chrome://inspector/content</a></code> starts the DOM Inspector.</dd>
-  <dt>
-    Chrome 包</dt>
-  <dd>
-    A
-    <i>
-      chrome package</i>
-    consists of a set of
-    <i>
-      <a href="en/Chrome_Registration">chrome providers</a></i>
-    . There are three basic types of chrome providers:
-    <ul>
-      <li><b>Content</b>. Content can consist of any file type viewable from within Mozilla. In particular, the content provider most often consists of a set of <a href="en/XUL">XUL</a>, <a href="en/JavaScript">JavaScript</a> and <a href="en/XBL">XBL</a> binding files.</li>
-      <li><b>Locale</b>. Translations for multi-language support. The two main types of files are <a href="en/XUL_Tutorial/Localization">DTD</a> files and java-style <a href="en/XUL_Tutorial/Property_Files">properties files</a>.</li>
-      <li><b>Skin</b>. The skin provider provides complete appearance data for the user interface. Consisting of <a href="en/CSS">CSS</a> files and images.</li>
-    </ul>
-  </dd>
-</dl>
-<dl>
-  <dt>
-    <code>chrome.rdf</code></dt>
-  <dd>
-    The chrome registry, stores the list of registered chrome packages and other information. It was located in the install directory and in the profile. It is no longer used since Gecko 1.8 (Firefox 1.5).</dd>
-</dl>
-<h2 id="See_also" name="See_also">相关链接</h2>
-<p>(Note that while both of the documents below mention <code>contents.rdf</code> files, an easier way of registering your chrome providers - using <a href="en/Chrome_Registration">Chrome Manifests</a> - is supported since <a href="en/Firefox_1.5">Firefox 1.5</a> / Toolkit 1.8)</p>
-<ul>
-  <li><a href="en/XUL_Tutorial/XUL_Structure">XUL Tutorial:XUL Structure</a></li>
-  <li><a href="en/XUL_Tutorial/The_Chrome_URL">XUL_Tutorial:The Chrome URL</a></li>
-</ul>
-- 
cgit v1.2.3-54-g00ecf