#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 <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019458744265-c195fbb0-5868-4295-b1fa-09fb2afdbce7-000000%40eu-central-1.amazonses.com.

Reply via email to