# Conflicts: # aio/content/cli/index.md # aio/content/guide/accessibility.md # aio/content/guide/ajs-quick-reference.md # aio/content/guide/angular-compiler-options.md # aio/content/guide/animations.md # aio/content/guide/aot-compiler.md # aio/content/guide/architecture-components.md # aio/content/guide/architecture-modules.md # aio/content/guide/architecture-next-steps.md # aio/content/guide/architecture-services.md # aio/content/guide/attribute-directives.md # aio/content/guide/bootstrapping.md # aio/content/guide/browser-support.md # aio/content/guide/cli-builder.md # aio/content/guide/comparing-observables.md # aio/content/guide/component-styles.md # aio/content/guide/creating-libraries.md # aio/content/guide/dependency-injection-in-action.md # aio/content/guide/dependency-injection-navtree.md # aio/content/guide/dependency-injection-providers.md # aio/content/guide/dependency-injection.md # aio/content/guide/deployment.md # aio/content/guide/deprecations.md # aio/content/guide/displaying-data.md # aio/content/guide/dynamic-component-loader.md # aio/content/guide/elements.md # aio/content/guide/file-structure.md # aio/content/guide/glossary.md # aio/content/guide/http.md # aio/content/guide/i18n.md # aio/content/guide/ivy-compatibility.md # aio/content/guide/language-service.md # aio/content/guide/lifecycle-hooks.md # aio/content/guide/module-types.md # aio/content/guide/ngmodule-faq.md # aio/content/guide/ngmodule-vs-jsmodule.md # aio/content/guide/ngmodules.md # aio/content/guide/observables-in-angular.md # aio/content/guide/pipes.md # aio/content/guide/providers.md # aio/content/guide/releases.md # aio/content/guide/route-animations.md # aio/content/guide/router-tutorial.md # aio/content/guide/router.md # aio/content/guide/rx-library.md # aio/content/guide/schematics-authoring.md # aio/content/guide/schematics-for-libraries.md # aio/content/guide/service-worker-config.md # aio/content/guide/service-worker-getting-started.md # aio/content/guide/structural-directives.md # aio/content/guide/styleguide.md # aio/content/guide/template-syntax.md # aio/content/guide/template-typecheck.md # aio/content/guide/testing.md # aio/content/guide/typescript-configuration.md # aio/content/guide/upgrade-setup.md # aio/content/guide/user-input.md # aio/content/guide/using-libraries.md # aio/content/guide/web-worker.md # aio/content/guide/workspace-config.md # aio/content/marketing/docs.md # aio/content/marketing/events.html # aio/content/navigation.json # aio/content/start/index.md # aio/content/start/start-data.md # aio/content/start/start-deployment.md # aio/content/tutorial/toh-pt2.md # aio/content/tutorial/toh-pt4.md # aio/package.json # aio/src/app/app.component.ts # aio/src/app/layout/footer/footer.component.html # aio/src/app/shared/custom-icon-registry.ts # aio/src/environments/environment.stable.ts # aio/tools/stackblitz-builder/builder.js # aio/tools/transforms/angular-content-package/index.js # aio/tools/transforms/templates/api/lib/memberHelpers.html # aio/yarn.lock # integration/ng_elements/e2e/app.e2e-spec.ts # integration/ng_elements/src/app.ts # packages/common/src/pipes/date_pipe.ts # packages/core/src/metadata/directives.ts # packages/core/src/metadata/ng_module.ts # packages/core/src/render/api.ts # packages/forms/src/directives/ng_model.ts # packages/forms/src/form_builder.ts # packages/forms/src/model.ts # packages/platform-browser/src/browser.ts # packages/router/src/config.ts # packages/router/src/directives/router_link.ts # packages/router/src/directives/router_link_active.ts # packages/router/src/events.ts # packages/router/src/router.ts # packages/router/src/router_module.ts # packages/router/src/router_state.ts
		
			
				
	
	
		
			116 lines
		
	
	
		
			5.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			116 lines
		
	
	
		
			5.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| {@a top}
 | ||
| 
 | ||
| # Set the document title
 | ||
| 
 | ||
| # 设置文档标题
 | ||
| 
 | ||
| Your app should be able to make the browser title bar say whatever you want it to say.
 | ||
| This cookbook explains how to do it.
 | ||
| 
 | ||
| 你的应用应该能让浏览器标题栏显示你想让它显示的内容。本文会解释怎么做。
 | ||
| 
 | ||
| See the <live-example name="set-document-title"></live-example>.
 | ||
| 
 | ||
| 参阅<live-example name="set-document-title"></live-example>
 | ||
| 
 | ||
| ## The problem with *<title>*
 | ||
| 
 | ||
| ## *<title>*的问题
 | ||
| 
 | ||
| The obvious approach is to bind a property of the component to the HTML `<title>` like this:
 | ||
| 
 | ||
| 显而易见的方法是把组件的属性绑定到 HTML 的 `<title>` 标签上,像这样:
 | ||
| 
 | ||
| <code-example format=''>
 | ||
|   <title>{{This_Does_Not_Work}}</title>
 | ||
| </code-example>
 | ||
| 
 | ||
| Sorry but that won't work.
 | ||
| The root component of the application is an element contained within the `<body>` tag.
 | ||
| The HTML `<title>` is in the document `<head>`, outside the body, making it inaccessible to Angular data binding.
 | ||
| 
 | ||
| 抱歉,这样不行。应用程序的根组件是一个包含在 `<body>` 标签里的元素。该 HTML 的 `<title>` 在文档的 `<head>` 元素里,在 `<body>` 之外,Angular 的数据绑定无法访问到它。
 | ||
| 
 | ||
| You could grab the browser `document` object and set the title manually.
 | ||
| That's dirty and undermines your chances of running the app outside of a browser someday.
 | ||
| 
 | ||
| 可以从浏览器获得 `document` 对象,并且手动设置标题。但是这样看起来很脏,而且将无法在浏览器之外运行应用程序。
 | ||
| 
 | ||
| <div class="alert is-helpful">
 | ||
| 
 | ||
|   Running your app outside a browser means that you can take advantage of server-side
 | ||
|   pre-rendering for near-instant first app render times and for SEO. It means you could run from
 | ||
|   inside a Web Worker to improve your app's responsiveness by using multiple threads. And it
 | ||
|   means that you could run your app inside Electron.js or Windows Universal to deliver it to the desktop.
 | ||
| 
 | ||
|   在浏览器外运行应用程序意味着:利用服务器端预先渲染,为应用程序实现几乎实时的首次渲染,同时还能支持 SEO(搜索引擎优化)。
 | ||
| 意味着你可以在一个 Web Worker 中运行你的应用程序,通过多线程技术增强应用程序的响应性。
 | ||
| 还意味着你可以在 Electron.js 或者 Windows Universal 里面运行,发布到桌面环境。
 | ||
| 
 | ||
| </div>
 | ||
| 
 | ||
| ## Use the `Title` service
 | ||
| 
 | ||
| ## 使用 `Title` 服务
 | ||
| 
 | ||
| Fortunately, Angular bridges the gap by providing a `Title` service as part of the *Browser platform*.
 | ||
| The [Title](api/platform-browser/Title) service is a simple class that provides an API
 | ||
| for getting and setting the current HTML document title:
 | ||
| 
 | ||
| 幸运的是,Angular 在*浏览器平台*的包中,提供了一个 `Title` 服务,弥补了这种差异。
 | ||
| [Title](api/platform-browser/Title)服务是一个简单的类,提供了一个 API,用来获取和设置当前 HTML 文档的标题。
 | ||
| 
 | ||
| * `getTitle() : string`—Gets the title of the current HTML document.
 | ||
| 
 | ||
|    `getTitle(): string` —— 获取当前 HTML 文档的标题。
 | ||
| 
 | ||
| * `setTitle( newTitle : string )`—Sets the title of the current HTML document.
 | ||
| 
 | ||
|    `setTitle( newTitle: string)` —— 设置当前 HTML 文档的标题。
 | ||
| 
 | ||
| You can inject the `Title` service into the root `AppComponent` and expose a bindable `setTitle` method that calls it:
 | ||
| 
 | ||
| 你可以把 `Title` 服务注入到根组件 `AppComponent`,并暴露出可供绑定的 `setTitle` 方法让别人来调用该服务:
 | ||
| 
 | ||
| <code-example path="set-document-title/src/app/app.component.ts" region="class" header="src/app/app.component.ts (class)"></code-example>
 | ||
| 
 | ||
| Bind that method to three anchor tags and voilà!
 | ||
| 
 | ||
| 把这个方法绑定到三个 A 标签,瞧瞧!
 | ||
| 
 | ||
| <div class="lightbox">
 | ||
|   <img src="generated/images/guide/set-document-title/set-title-anim.gif" alt="Set title">
 | ||
| </div>
 | ||
| 
 | ||
| Here's the complete solution:
 | ||
| 
 | ||
| 这里是完整的方案(代码)。
 | ||
| 
 | ||
| <code-tabs>
 | ||
|   <code-pane header="src/main.ts" path="set-document-title/src/main.ts"></code-pane>
 | ||
|   <code-pane header="src/app/app.module.ts" path="set-document-title/src/app/app.module.ts"></code-pane>
 | ||
|   <code-pane header="src/app/app.component.ts" path="set-document-title/src/app/app.component.ts"></code-pane>
 | ||
| </code-tabs>
 | ||
| 
 | ||
| ## Why provide the `Title` service in `bootstrap`
 | ||
| 
 | ||
| ## 为什么要在 *bootstrap* 里面提供这个 *Title* 服务
 | ||
| 
 | ||
| Generally you want to provide application-wide services in the root application component, `AppComponent`.
 | ||
| 
 | ||
| 你通常会在应用程序的根组件 `AppComponent` 中提供应用程序级的服务。
 | ||
| 
 | ||
| This cookbook recommends registering the title service during bootstrapping,
 | ||
| a location you reserve for configuring the runtime Angular environment.
 | ||
| 
 | ||
| 但这里,要在引导过程中注册这个 Title 服务,这个位置是为你设置 Angular 运行环境而保留的。
 | ||
| 
 | ||
| That's exactly what you're doing.
 | ||
| The `Title` service is part of the Angular *browser platform*.
 | ||
| If you bootstrap your application into a different platform,
 | ||
| you'll have to provide a different `Title` service that understands
 | ||
| the concept of a "document title" for that specific platform.
 | ||
| Ideally, the application itself neither knows nor cares about the runtime environment.
 | ||
| 
 | ||
| 你的做法正是如此。这里的 `Title` 服务是 Angular*浏览器平台*的一部分。如果在其它平台上引导应用程序,就得提供另一个专为那个平台准备的 `Title` 服务。
 |