Changes between Initial Version and Version 1 of Ticket #13629


Ignore:
Timestamp:
06/18/10 10:41:49 (5 years ago)
Author:
russellm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13629

    • Property Patch needs improvement unset
    • Property Triage Stage changed from Unreviewed to Accepted
    • Property Needs tests unset
    • Property Needs documentation unset
  • Ticket #13629 – Description

    initial v1  
    1 Change form pages have "app-model_name" classes in body tag, for eg:[[BR]]
    2 <body class="main-client change-form">. Change list pages don't, which[[BR]]
     1Change form pages have "app-model_name" classes in body tag, for eg:
     2<body class="main-client change-form">. Change list pages don't, which
    33makes them unrecognizable in JavaScript code.
    44
    55Example use case:
    6 I'm currently implementing jQuery tooltips for searchbars to give user[[BR]]
     6I'm currently implementing jQuery tooltips for searchbars to give user
    77information about which model's fields are searchable in each change list.
    88
    9 Currently to achieve this I had to override ModelAdmin.changelist_view (to[[BR]]
    10 add model._meta to context) and change_list.html template. This is ok but I[[BR]]
     9Currently to achieve this I had to override ModelAdmin.changelist_view (to
     10add model._meta to context) and change_list.html template. This is ok but I
    1111think it would be nice to have it already done in django?
Back to Top