From 966130123e140c8be2ff0f703a5d7e346c7a1b45 Mon Sep 17 00:00:00 2001 From: Dikran Samarjian Date: Wed, 3 Jun 2026 11:46:19 -0700 Subject: [PATCH] remove redundant paragraph --- docs/guides/faq.mdx | 2 -- versioned_docs/version-0.12/guides/faq.mdx | 2 -- versioned_docs/version-0.13/guides/faq.mdx | 2 -- 3 files changed, 6 deletions(-) diff --git a/docs/guides/faq.mdx b/docs/guides/faq.mdx index 9b4d5746..43ec3b06 100644 --- a/docs/guides/faq.mdx +++ b/docs/guides/faq.mdx @@ -246,8 +246,6 @@ Use HTML launch entry points for all new and existing work. The older `splash` p Treat inline and expanded mode differently. Inline should avoid scroll traps and heavy gesture hijacking so users can still scroll past the post, while expanded is the right place for richer touch interaction and more space. -There's no single canonical viewport size for all devices. Design responsively, test in [UI Simulator](./tools/ui_simulator.mdx), and use the current launch-mode docs for inline vs expanded behavior in [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md) and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md). - diff --git a/versioned_docs/version-0.12/guides/faq.mdx b/versioned_docs/version-0.12/guides/faq.mdx index 9b4d5746..43ec3b06 100644 --- a/versioned_docs/version-0.12/guides/faq.mdx +++ b/versioned_docs/version-0.12/guides/faq.mdx @@ -246,8 +246,6 @@ Use HTML launch entry points for all new and existing work. The older `splash` p Treat inline and expanded mode differently. Inline should avoid scroll traps and heavy gesture hijacking so users can still scroll past the post, while expanded is the right place for richer touch interaction and more space. -There's no single canonical viewport size for all devices. Design responsively, test in [UI Simulator](./tools/ui_simulator.mdx), and use the current launch-mode docs for inline vs expanded behavior in [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md) and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md). - diff --git a/versioned_docs/version-0.13/guides/faq.mdx b/versioned_docs/version-0.13/guides/faq.mdx index 9b4d5746..43ec3b06 100644 --- a/versioned_docs/version-0.13/guides/faq.mdx +++ b/versioned_docs/version-0.13/guides/faq.mdx @@ -246,8 +246,6 @@ Use HTML launch entry points for all new and existing work. The older `splash` p Treat inline and expanded mode differently. Inline should avoid scroll traps and heavy gesture hijacking so users can still scroll past the post, while expanded is the right place for richer touch interaction and more space. -There's no single canonical viewport size for all devices. Design responsively, test in [UI Simulator](./tools/ui_simulator.mdx), and use the current launch-mode docs for inline vs expanded behavior in [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md) and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md). -