Skip to content

Allow referencing and history of tab navigation on detail pages#7191

Open
beknownst wants to merge 4 commits intoEasyCorp:4.xfrom
beknownst:refactor/extract-tab-control
Open

Allow referencing and history of tab navigation on detail pages#7191
beknownst wants to merge 4 commits intoEasyCorp:4.xfrom
beknownst:refactor/extract-tab-control

Conversation

@beknownst
Copy link

@beknownst beknownst commented Oct 29, 2025

As described in #6442, linking to tabs or storing tab navigation in history only works for form pages (new/edit).

I also have some use cases where Action::DETAIL is added to actions of CrudControllers and where I want to redirect a user to a specific tab in the detail view. This currently does not work as the logic for activating the tab is present only in form.js.

This PR simply moves the logic from form.js to app.js to make it present on both form and detail pages.
Furthermore it uses a slightly simplified approach to display the first tab with errors and I adjusted some commentary to make it less about forms and more about tabs.

Since I did not find any guidelines regarding PR-creation on the subject of altered frontend assets, I only commited the changes made to the JavaScript files and not those to entrypoints.json, manifest.json and other build files in /public. If this is required, please do let me know.

Fixes: #6442

@beknownst beknownst changed the title Allow referencing and history of tab navigation on both detail and form pages Allow referencing and history of tab navigation on detail pages Feb 16, 2026
@beknownst
Copy link
Author

@javiereguiluz Is there anything I can do or improve? I have a fairly large amount of projects with customers that want to link to tabs in the detail view.

Regards, with full understanding that you most presumably are quite busy and have limited time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow direct linking to FormField::Tab content on DETAIL page

1 participant

Comments