Describe the bug
The Copy record URL button in the expanded record header copies window.location.href. In the kanban and gallery views, clicking a card expands the record through local component state only, without putting recordId in the URL, so the copied link points at the view instead of the record. The same record opened from a grid view produces a correct deep link.
To Reproduce
- Open a table with a kanban view (a gallery view behaves the same).
- Click a card to expand the record.
- Click the link icon in the expanded record header (Copy record URL).
- Paste the clipboard content.
Expected behavior
A deep link to the record, as the grid view already produces:
https://host/base/bseXXX/table/tblXXX/viwXXX?recordId=recXXX
Actual behavior
The bare view URL, with no recordId:
https://host/base/bseXXX/table/tblXXX/viwXXX
Reopening that link shows the view with no record expanded, which makes the button useless for sharing a record with a teammate.
Side effects of the same cause: expanding a card from kanban or gallery does not create a history entry, and a browser refresh loses the expanded record.
Environment
- Self-hosted, teable 1.10.0
- Reproduced on
develop with the local dev stack (postgres + redis, pnpm dev)
- Chrome 149, Linux
Notes
The calendar view expands records the same way and has no recordId synchronization at all in its provider, so it is affected too.
Describe the bug
The Copy record URL button in the expanded record header copies
window.location.href. In the kanban and gallery views, clicking a card expands the record through local component state only, without puttingrecordIdin the URL, so the copied link points at the view instead of the record. The same record opened from a grid view produces a correct deep link.To Reproduce
Expected behavior
A deep link to the record, as the grid view already produces:
https://host/base/bseXXX/table/tblXXX/viwXXX?recordId=recXXXActual behavior
The bare view URL, with no
recordId:https://host/base/bseXXX/table/tblXXX/viwXXXReopening that link shows the view with no record expanded, which makes the button useless for sharing a record with a teammate.
Side effects of the same cause: expanding a card from kanban or gallery does not create a history entry, and a browser refresh loses the expanded record.
Environment
developwith the local dev stack (postgres + redis,pnpm dev)Notes
The calendar view expands records the same way and has no
recordIdsynchronization at all in its provider, so it is affected too.