-
Notifications
You must be signed in to change notification settings - Fork 34
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
Resource Table Click Action not working for Computed Fields with asHtml() #6001
Comments
Please provide full reproducing repository based on fresh installation as suggested in the bug report template (or you can refer to https://github.com/nova-issues for example) |
Hi @crynobone Please see https://github.com/goldmerc/nova-clickable-row-computed-field-test You'll need to set up a database, migrate + create a nova user. Then just view the index page of the user resource. You'll see "clickable" and "not clickable". Fairly self explanatory! Thanks for your help. |
This behavior is expected to allow adding custom link to field with |
Thanks for the explanation. With Nova 3, I used to use a package to implement clickable table rows. I'm not sure how the functionality is implemented in Nova 4 but the old package had no trouble with links in asHtml fields as well as buttons and text selection. It simply ignored certain HTML elements. It's a short bit of code... https://github.com/dcasia/clickable-table-row/blob/development/resources/js/tool.js I think this functionality would be the behaviour expected by most users but that's just my view. |
This! In my case I'm just formatting a column bold using a span and 'font-bold' class. But since this is not clickable now, it's confusing users... |
Still relevant. Instead of just Vue click.stop it would be helpful if it was filtered, ie similar to what @goldmerc linked. |
Computed Fields with asHtml() are not clickable in resource table rows. Without asHtml() they work as expected.
Text::make('foo', fn() => 'clickable'),
Text::make('bar', fn() => 'not clickable')->asHtml(),
The text was updated successfully, but these errors were encountered: