Re: [Django] #36079: Size of the object's str in TabularInline is too small

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: Inline, Font, | Triage Stage: Accepted
accessibility |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Antoliny):

* Attachment "inline_fields_layout.png" added.

--
Ticket URL: <https://code.djangoproject.com/ticket/36079>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: Inline, Font, | Triage Stage: Accepted
accessibility |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------

Comment (by Antoliny):

The main difference between `TabularInline` and `StackedInline` is the
row/column arrangement of the fields.
[[Image(inline_fields_layout.png)]]
Therefore, I don't think the headers of the forms inside `TabularInline`
and `StackedInline` need to be in different formats. How about making the
form headers inside both `TabularInline` and `StackedInline` the same
style?
Even if they are the same, I believe the differences in their layouts
(row/column) are enough to distinguish them. If they are the same, I
personally prefer the header style of `StackedInline`😃(especially
considering situations with many forms)
--
Ticket URL: <https://code.djangoproject.com/ticket/36079#comment:6>

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: Inline, Font, | Triage Stage: Accepted
accessibility |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Antoliny):

[https://forum.djangoproject.com/t/improving-consistency-and-
accessibility-between-tabularinline-and-stackedinline/37951 discussion]
--
Ticket URL: <https://code.djangoproject.com/ticket/36079#comment:7>

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: Inline, Font, | Triage Stage: Accepted
accessibility |

Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------

Changes (by Antoliny):

* has_patch: 0 => 1

Comment:

[https://github.com/django/django/pull/19698 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/36079#comment:8>

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:

Keywords: inline, | Triage Stage: Accepted

accessibility |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Antoliny):

* keywords: Inline, Font, accessibility => inline, accessibility

--
Ticket URL: <https://code.djangoproject.com/ticket/36079#comment:9>

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:

Keywords: inline, | Triage Stage: Ready for
accessibility | checkin

Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------

Changes (by Sarah Boyce):

* stage: Accepted => Ready for checkin

--
Ticket URL: <https://code.djangoproject.com/ticket/36079#comment:10>

[Django]

#36079: Size of the object's str in TabularInline is too small
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny

Type: | Status: closed

Cleanup/optimization |
Component: contrib.admin | Version: dev

Severity: Normal | Resolution: fixed

Keywords: inline, | Triage Stage: Ready for
accessibility | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------

Changes (by Sarah Boyce <42296566+sarahboyce@…>):

* resolution: => fixed
* status: assigned => closed

Comment:

In [changeset:"65377325855ab6faa7ac487e336e9902c6268c96" 65377325]:
{{{#!CommitTicketReference repository=""
revision="65377325855ab6faa7ac487e336e9902c6268c96"
Fixed #36079 -- Fixed text size of TabularInline object titles.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36079#comment:11>