> For the complete documentation index, see [llms.txt](https://doc.qrspace.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.qrspace.dev/he-xin-kong-jian-jia-gou/three-layers.md).

# 三層介面設計

口袋瀏覽器採用三層空間圖層架構，將傳統瀏覽器擁擠的介面元素解構為明確的深度層級。

***

## 空間分層結構

```
[頂層]  置中浮動畫布層 (白板為大 / 全域 Modal / 最高 z-index)
   │
[外圍]  周邊工具層 (左側 8 頁籤 / 頂部動態島 / 底部 Alt+Q 口袋)
   │
[底層]  原生瀏覽層 (標準 Chromium 渲染核心 / 獨立 Process)
```

***

## 1. 原生瀏覽層（底層）

* **架構基礎**：基於最新 Chromium 核心渲染，保有完整 Web 標準相容性。
* **隔離環境**：每個瀏覽分頁運行於獨立沙盒進程中，確保單一分頁崩潰不影響其他分頁與主視窗。
* **無干擾視界**：網頁視野盡可能最大化，除標準導航控制外，無額外的固定工具列占用閱讀高度。

***

## 2. 周邊工具層（外圍）

周邊工具層分佈於視窗外緣，平時縮回邊界，不阻擋網頁主要內容：

* **左側軌道（Side Rail）**：垂直排列 8 個核心工具頁籤（路徑圖、郵件、任務、心智圖、剪貼簿、集合、定時動作、擴充商店等）。點選時以側邊抽屜展開，寬度適中，不打斷主要閱讀流程。
* **頂部動態島（Dynamic Island）**：位於網址列下方中央，僅在特定事件觸發時短暫展開（例如檔案下載進度、定時器提醒、分頁操作反饋），平時完全隱藏。
* **底部口袋（Pocket Dock）**：透過快捷鍵 `Alt + Q` 呼叫。自視窗底部滑出，整合分頁一鍵收合、Bitwarden 密碼金庫、資源嗅探器與多執行緒下載管理器。

***

## 3. 浮動畫布層（頂層）

頂層獨立於網頁 DOM 之外，具備全域最高渲染層級：

* **置中浮動白板**：浮動於視窗中央，底層網頁無論如何滾動或切換分頁，白板均保持顯示，實踐「寫白板為大」的工作模式。
* **非模態交互**：白板開啟時，底層網頁依然可滾動查閱資料，使用者可一邊對照原文、一邊在白板記錄思考架構。
* **即時儲存**：白板畫布狀態與文字即時寫入本地持久化儲存，意外關閉或重啟視窗資料不遺失。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.qrspace.dev/he-xin-kong-jian-jia-gou/three-layers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
