-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update: Rephrase "Force page reload" and move to Advanced #65081
Changes from 3 commits
d0270d6
660cd82
d0e453c
966ef85
ba35aa5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,19 +25,19 @@ export default function EnhancedPaginationControl( { | |
); | ||
} else if ( enhancedPagination ) { | ||
help = __( | ||
"Browsing between pages won't require a full page reload, unless non-compatible blocks are detected." | ||
'Reload the full page—instead of just the posts list—when visitors navigate between pages.' | ||
); | ||
} else if ( hasUnsupportedBlocks ) { | ||
help = __( | ||
"Force page reload can't be disabled because there are non-compatible blocks inside the Query block." | ||
"Reload full page can't be disabled because there are non-compatible blocks inside the Query block." | ||
jasmussen marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One important note. When there are non-compatible blocks, then the full page navigation, as in older WordPress versions, needs to happen. I think it's what it says but it's still confusing for me. Eventually, we should aim to remove this compatibility check and instead handle everything on the front end using a progressive enhancement approach. For example, when the partial page change withouth full reload is enabled, we try to go to the next page and if Interactivity API detects something went wrong, it should fall back to the usual behavior when someone click a link. |
||
); | ||
} | ||
|
||
return ( | ||
<> | ||
<ToggleControl | ||
__nextHasNoMarginBottom | ||
label={ __( 'Force page reload' ) } | ||
label={ __( 'Reload full page' ) } | ||
help={ help } | ||
checked={ | ||
! enhancedPagination && ! fullPageClientSideNavigation | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this is correct.