AtomUI/docs/releases/6.2.1-api-changes.md

AtomUI 6.2.1 API Change Examples

AtomUI 6.2.1 intentionally changes Pagination's default navigation window and Semantic Part marker count while aligning jump navigation with Ant Design. Applications that snapshot, automate or style the realized navigation container pool must update as described below.

Chinese version: AtomUI 6.2.1 API 变更示例.

Quick reference

Area	6.2.0 behavior	6.2.1 migration
Pagination navigation pool	11 fixed PaginationNavItem containers, with non-interactive ellipsis cells	9 fixed containers: previous + 7 intermediate slots + next; update snapshots or automation that assert the old count
Pagination jump behavior	Ellipsis cells do not navigate	JumpPrevious / JumpNext move five pages by default and three pages with IsShowLessItems=true; set IsShowPrevNextJumpers=false to hide jump actions
Pagination Semantic Parts	The runtime item marker pool follows 11 containers	The runtime pool follows 9 containers; jump items remain excluded from PaginationItemStyle matching

Pagination: update navigation-window expectations

Pagination now uses a fixed nine-container navigation pool. The first and last containers remain previous and next actions; the seven intermediate slots are reused for page indicators and JumpPrevious / JumpNext actions. The jump actions support pointer activation and the Enter key.

The navigation model uses these defaults:

• IsShowLessItems=false: up to seven intermediate slots and five-page jump actions.
• IsShowLessItems=true: up to five intermediate slots and three-page jump actions.
• IsShowPrevNextJumpers=true: jump actions are shown when the page window requires them.
• IsShowPrevNextJumpers=false: the window omits the jump actions.

6.2.0 assumptions that need updating

Tests or automation that inspect realized containers may currently expect 11 PaginationNavItem instances or the corresponding Semantic Part marker pool. Update those expectations to 9. Applications should continue to style page, previous and next items through the generated PaginationItemStyle; JumpPrevious and JumpNext intentionally do not carry the semantic-item marker.

<Style Selector="atom|Pagination">
    <atom:PaginationItemStyle x:SetterTargetType="ContentControl">
        <Setter Property="CornerRadius" Value="999" />
    </atom:PaginationItemStyle>
</Style>

Do not depend on the internal PaginationNavItem type, container indexes or hidden-container count. Use CurrentPage, PageSize, IsShowLessItems, IsShowPrevNextJumpers and the generated Semantic Part style entry point instead.

Choosing the 6.2.1 navigation modes

<!-- Ant Design-aligned default window and five-page jumps. -->
<atom:Pagination Total="500"
                 CurrentPage="20"
                 IsShowPrevNextJumpers="True" />

<!-- Denser window and three-page jumps. -->
<atom:Pagination Total="500"
                 CurrentPage="20"
                 IsShowLessItems="True"
                 IsShowPrevNextJumpers="True" />

<!-- Page indicators only; no jump actions. -->
<atom:Pagination Total="500"
                 CurrentPage="20"
                 IsShowPrevNextJumpers="False" />

There is no compatibility switch that restores the exact 11-container pool. Applications whose UI contract requires that internal realization shape must remain on 6.2.0 or replace that dependency with public Pagination state and Semantic Part styling before upgrading.