澄清滚动内容限制 [英] Clarify scrolling content constraints
问题描述
在Windows AER App Guidance Doc：3.1 UX Bar测试用例中，有一个测试用例，讨论限制内容，使其只向一个方向滚动。 您能否澄清以下内容？
In the Windows AER App Guidance Doc: 3.1 UX Bar Test cases there is a test case that talks about constraining content so it only scrolls in one direction. Can you clarify the following?
案例：
我们的应用程序的主要方向是横向。
Our app's primary orientation is landscape.
在Hub中，我们有三个不同的部分，用户可以通过水平平移来浏览它们。
In the Hub, we have three distinct sections that the user can navigate between by panning horizontally.
三个部分中的一个部分有一个可以延伸到屏幕初始垂直高度以下的项目列表，即用户必须在该部分内垂直向下滚动到查看所有项目。
One of the three sections has a list of items that could extend below the initial vertical height of the screen, ie, users would have to vertically scroll down within that section to see all of the items.
我在线搜索了所有文档，除了这个测试用例之外，我没有看到任何内容，它解决了垂直和水平滚动的组合。 ;我确实看到内容区域没有设置底部边距。
I've searched through all the documentation online and I don't see anything, besides this test case, that addresses a combination of vertical and horizontal scrolling. I do see that there is no set bottom margin for the content area.
我的问题是：
- 在集线器中，必须是所有部分内容在同一个底点结束，或者一个部分的内容可以垂直滚动到初始水平屏幕高度以下？
-in the hub, must all section content end at the same bottom point or can content in one section scroll vertically below the initial horizontal screen height?
- 如果是，这是否适用于层次结构的其他级别，即部分页面？用户是否可以平移部分页面中的离散内容块以及垂直滚动特定的内容块？
-If yes, does this apply to other levels of the hierarchy, ie, section pages? Can the user both pan across discrete content blocks within a section page as well as vertically scroll a particular block of content?
感谢您的帮助和/或对特定文档的指导我应该看一下。
Thanks for your help and/or direction to specific documentation I should look at.
推荐答案
我无法说出微软正在使用的确切规则。 ;但是从我所看到的情况来看，通常在这种情况下，较大的部分会占用多个"窗格"。或显示数据视图并继续创建窗格，直到您显示所有数据。 我们
在我们正在构建的应用程序中使用此范例，它运行正常。 您可能需要设置自己的捕捉点，以便用户可以在一个部分内正确滑动，当需要多个屏幕才能显示所有内容时。
I can't speak to the exact rules Microsoft is using. But from what I've seen, typically in this case your larger section would take up more than one "pane" or viewport of data and continue to create panes until you've shown all the data. We use this paradigm all over the app we are building and it works fine. You probably will want to set up your own snap points so that users can correctly swipe within a section when it takes more than one screen to show it all.
这篇关于澄清滚动内容限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
