v2.18.0

Minor release from a consumer report: a record of a resource with a detail override (DrawerOverride::detail() or a custom one) now opens over its index without reloading the page, and a resource can name the browser tab of its records with documentTitle(). Read Upgrading to v2.18.0.

Added

• Resource::documentTitle(): ?string: the browser tab title of a record's detail, page or override. null (the default) keeps "{singular label}: {title()}". The detail response carries it as _documentTitle. See Resources → Browser tab title.

Changed

• A detail override opens over the index in place. The row click and the default View action push the record URL and keep the index mounted: the list stays on screen and is not fetched again, the bundled drawer opens at once with its own skeleton, and closing (or the back button) steps back to the index entry with its page, sort and filters. A direct visit to the record URL renders the index with the override on top once the schema has loaded. The top progress bar and the menu badge refresh no longer run for an open or a close. Before, the row click showed a full-page loader until the schema and the record arrived, then mounted the index again, and closing mounted it once more. See Overrides → Detail overrides open over the index.

Fixed

• A drawer swapping in for another one stacked a history entry per swap. Each detail → update → detail swap pushed one more Back sentinel, so after editing, Back (or closing) stayed on the record URL. The drawer that swaps in now takes over the previous one's sentinel, and a pop that leaves the drawer's page is left to the page instead of being taken for a Back press. The Back sentinels of drawers and modals now carry the router's location state, so closing a modal over a drawer no longer makes the router read a location without it.