预期行为：对分页表的列进行排序
当用户查看分页表并请求按特定列排序时，会显示哪个页面？
这种情况是否有标准的预期行为？我可以想象几种可能的结果，但想知道是否有一个标准。
When a user is viewing a paged table and requests it to sorted by a particular column, what page is shown?
Is there a standard expected behavior for this scenario? I can imagine several possible outcomes, but want to know if there is a standard.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您的意思是在表中的 n 页中显示哪一页？没有好的选择——任何可能性都可能让用户迷失方向和沮丧，因为没有标准，也没有特别好的理由来选择一个选项而不是另一个选项。如果你要测试用户，我怀疑他们会有一致的期望。即使同一用户在不同时间也可能期望不同的事情。分页表还提供有关表中当前位置的相对较弱的反馈，因此用户很难在对您使用的任何选项进行排序后了解他们所在的位置。可用排序是分页表不如滚动表的原因之一。
可能性：
如果您有办法在表中显示当前选定或聚焦的项目（行），那么您可以转到该项目所在的任何页面，假设用户选择在该页面进行排序以便看到与他们正在查看的项目类似的其他项目。这与滚动表的一些实现是一致的。但是，大多数网络应用程序分页表格不支持选择项目。
您可以显示用户排序时所在的第i页（例如，如果他们排序时位于第三页，则显示新排序顺序下的第三页） 。这与滚动表的一些其他实现是一致的。它还支持表格几乎正确排序的情况（例如，在发送日期，当需要接收日期时）。显示第i页面会让用户进入与之前“相同的页面”。然而，这并不是最常见的用例，由于位置反馈较弱，用户可能会觉得自己被扔到了任意页面。此选项可能会产生最大的迷失方向。
您可以在新的排序顺序下显示第一页。根据您的任务，也许大多数时候，当用户对表进行排序时，用户会对排序所依据的属性值最高或最低的项目感兴趣。通过显示第一页，你正确的概率可以接近 50%。这是最不会让人迷失方向的，因为用户感觉他们回到了精神锚点——开始。另一方面，如果用户觉得自己“重新开始”，他们可能会感到沮丧。总的来说，这可能是您的最佳选择。
通常，在排序后，用户希望跳转到其排序属性上具有特定值的项目。这对于分页表来说很困难，因为分页速度很慢并且用户不知道哪个页码对应于哪个值。您可以使用在页面上找到的值范围来标记页面的链接，但这可能会消耗大量空间。至少，无论页面有多少，您都应该始终提供指向表格第一页和最后一页的链接，以便用户只需单击一下即可找到具有最高和最低值的项目。
或者，考虑支持过滤而不是排序来实现相同的目的。根据用户的任务，这可能会工作得更好，并且不会那么混乱和费力。
You mean which page to show among the n pages in the table? There are no good options –any possibility is likely to be disorienting and frustrating for the user precisely because there is no standard and no particularly good reason to chose one option over the other. If you were to test users, I doubt they’d have consistent expectations. Even the same user may expect different things at different times. Paged tables also provide relatively weak feedback on the current location in the table so it’s hard for users to understand where they are after sorting whatever option you use. Usable sorting is one reason paged tables are inferior to scrolling tables.
Of the possibilities:
If you have a way of showing a currently selected or focused item (row) in the table, then you can go to whatever page that item is on, under the assumption that the users chose to sort at that moment in order to see other items like the item they’re looking at. This is consistent with some implementations of scrolling tables. However, most web-app paged tables don’t support the selection of an item.
You can show the ith page that the users are on when they sorted (e.g., if they’re on the third page when they sorted, show the third page under the new sort order). This is consistent with some other implementations of scrolling tables. It also supports the case where the table is almost sorted correctly (e.g., on Send Date, when Received Date is need). Showing the ith page puts the users on about the “same page” they were before. This is however not the most common use case and users are likely to feel they’ve been thrown to an arbitrary page given the weak location feedback. This option will probably produce the greatest disorientation.
You can show the 1st page under the new sort order. Depending on your tasks, perhaps most of the time when a user sorts a table, the users are interested in the items with the highest or lowest value of the attribute they sorted on. By showing the first page, the probability of you being right can approach 50%. It’s the least disorienting because the user feels they’re back at a mental anchor point –the beginning. On the other hand, users may be frustrated if they feel they’re “starting over.” Overall, this is probably your best option.
Generally following a sort, users want to jump to items with a certain value on the attribute they sorted on. This is difficult with a paged table because paging is slow and the users don’t know what page number corresponds to what value. You could label the links for the pages with the range of values found on them, but that can consume a lot of real estate. At the very least, you should always provide a link to the first and last page of the table however many pages there are so users can get to the items with highest and lowest values in one click.
Alternatively, consider supporting filtering rather than sorting to accomplish the same purpose. Depending on your users’ task, that may work much better and be less confusing and effortful.
Michael Zuschlag 的回答非常好，但我认为他提出的案例#1 和案例#2 确实不常见，这样做可能会让人困惑而不是有用。
在我看来，您应该始终在新的排序顺序下显示第一页。如果用户选择了一个项目，通常他不想对任何内容进行排序，因为他已经找到了他要查找的内容。
如果您想对列表进行排序，通常您希望看到真实的、完整的顺序。
一个典型的场景可以是一个 torrent 站点：
我搜索一个 torrent，输入一些内容
关键词。
搜索后我有
无序列表，每个列表 50 个项目
页面。
我转到第二页。
现在，我认为最好从种子数量最多的项目开始对结果进行排序，然后单击种子列的标题。
我希望在操作 4 之后看到播种者数量最多的项目，因此排序后您必须向我显示第一页。我认为对于任何排序情况都是如此。
The answer of Michael Zuschlag is very good, but I think that the case #1 and #2 that he presents are really uncommon, and doing so can be more confusing than useful.
In my opinion, you should always show the 1st page under the new sort order. If the user has selected an item, usually he don't want to sort anything, because he already found what he was looking for.
If you want to give a sort order to a list, usually you want to see the real, complete order.
A classic scenario can be a torrent site:
I search for a torrent typing some
keywords.
After the search I a have
an unordered list, 50 items per
page.
I go to second page.
Now, I think that is better sort the results starting from the item that has the highest number of seeders, and click to the header of the seeds column.
I expect to see the item with the the highest number of seeders after action 4, so after sorting you have to show me the first page. And I think this is true for about any sorting situation.
首先，对之前的答案表示感谢（和+1）
其次，仅针对用户熟悉和可能期望的现实生活示例，雅虎邮件执行#3（排序后跳转到第1页）。许多其他网站也是如此。
我个人的建议 - 如果可行的话 - 将是上面的#1（允许跳转到包含当前所选元素的页面）。确保该元素仍处于选中状态。
这既有点直观，又不是非常出乎意料，并且在用户关心发生的情况时最有用。另外，假设您的分页控件包括“转到第 1 页”，则选项#3（跳转到第一页）对于用户来说只需点击 1 次即可，而正如前面的答案中所述，执行第一页会让用户感到困难和漫长谁确实想保留当前项目。
如果可行的话，我绝对支持“添加过滤”的想法 - 我发现自己使用 Excel 处理来自任何应用程序/网站的表格/列表的工作超过 50%，因为它出色地结合了过滤和排序。假设您的 UI 是 HTML，也许 YUI 有一个不错的可过滤表格元素？
First of all, AMEN to the previous answer (and +1)
Second, just for real life examples of what users are familiar with and may expect, Yahoo Mail does #3 (jump to page 1 after sort). So do many other web sites.
My personal recommendation - if feasible to implement - would be #1 above (allow jumping to the page containing the currently selected element). Make sure that element is STILL selected.
That is both somewhat intuitive, not very un-expected, and most useful in cases where the user cares what happens. Plus, the option #3 (jumping to first page) is only 1 click away for the user assuming your paging controls include "Go to page 1", whereas, as noted in previous answer, doing first page makes it hard and long for user who did want to stay with the current item.
I definitely support the "add filtering" idea as well if feasible - I find myself using Excel for >50% of the work with tables/lists originated from any app/website, due to its exceptional combination of filtering and sorting. Perhaps YUI has a decent filterable table element assuming your UI is HTML?