> 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/ce-bian-gong-ju-lie-yu-kuo-chong/mobile-view.md).

# Mobile View 行動視角

口袋瀏覽器提供獨立的 Mobile View 工具頁籤，可在桌面端快速模擬真實智慧型手機的瀏覽視界。

***

## 為什麼需要 Mobile View

在桌面環境開發網頁、檢查排版或查閱僅為行動裝置最佳化的網站時，傳統方式往往需要手動打開 Chrome DevTools、切換裝置工具列，再手動縮放視窗尺寸。

口袋瀏覽器將行動視口封裝為側邊獨立頁籤，隨時一鍵呼叫。

***

## 介面與控制規格

可在擴充商店中將 Mobile View 新增至左側工具列。打開該頁籤時，介面維持極簡導航：

* **頂部工具列**：
  * 上一頁 / 下一頁按鈕
  * 重新整理按鈕
  * 獨立網址輸入列
* **視口區域**：
  * 預設鎖定為標準智慧型手機縱向比例（Viewport Width 375px \~ 412px）。
  * 自動發送真實行動裝置的 User-Agent 與觸控模擬事件。
  * 任何輸入的網址均直接以手機版介面載入。

***

## 適用情境

* **前端開發與 QA 測試**：無需開啟肥大的開發者工具，即時比對桌面版與行動版排版差異。
* **行動限定服務存取**：查閱部分僅在手機端提供完整功能或版面的社群網站與行動服務。
* **對照閱讀**：右側瀏覽桌面版詳細文檔，左側抽屜對照行動版快速摘要。


---

# 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/ce-bian-gong-ju-lie-yu-kuo-chong/mobile-view.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.
