You need to check the selenium tests but I found that with this change, I can no longer create new items in the tabular inline (I can't update the fields or delete the row entries)

Thank you Sarah, Looks like the absolute positioned element is covering the interactive buttons. 🥲

@Antoliny0919 can you take a look at the "View on Site" button for a stackedinline on mobile/tablet views:

I think it would be better if either both the change link and view on site button is on a new line or they are together

@Antoliny0919 can you take a look at the "View on Site" button for a stackedinline on mobile/tablet views:
I think it would be better if either both the change link and view on site button is on a new line or they are together

Thank you Sarah :) I agree. It would be better to separate the links and the object string into different lines.
By the way, the image above wasn’t generated through screenshot tests, right?
I didn’t see it when I was testing.
How about adding a screenshot test for StackedInline when an object exist? (+ links)
It seems like we don’t have one yet.

By the way, the image above wasn’t generated through screenshot tests, right?

Correct, I found this through manual testing. Having a screenshot with the StackedInline is also a good idea.
I would have the changes around this link becoming a button, including the additional test, be in a separate commit if possible

So now the buttons are always on a new line in the staked case, which I'm not sure this is what's wanted

In the ticket (and I know it's discussed in the forum: https://forum.djangoproject.com/t/improving-consistency-and-accessibility-between-tabularinline-and-stackedinline/37951/2), I was hoping we'd land on having the stackedinline and taburlarinline having the same design approach. Currently, this PR makes the two designs diverge further
Perhaps we should remove the model name prefix from the stacked inlines but otherwise use the stacked inline design for the titles? So then we don't truncate the name of the tabular inlines?

So now the buttons are always on a new line in the staked case, which I'm not sure this is what's wanted

In the ticket (and I know it's discussed in the forum: https://forum.djangoproject.com/t/improving-consistency-and-accessibility-between-tabularinline-and-stackedinline/37951/2), I was hoping we'd land on having the stackedinline and taburlarinline having the same design approach. Currently, this PR makes the two designs diverge further Perhaps we should remove the model name prefix from the stacked inlines but otherwise use the stacked inline design for the titles? So then we don't truncate the name of the tabular inlines?

I think that would probably be the most ideal.
But since TabularInline is in a table format and the object __str__ is displayed in a single column.
hmm… I guess I’ll have to give it a try.
Thanks for the great suggestion Sarah!

In the Tabular layout, a single object can be represented using up to three rows.
Do you think it would be better to unify the background color of these three rows(row group)?

Previously, a single object could take up to two rows (error, data), and in that case, the background colors were not unified.