Code

Opened 4 years ago

Closed 13 months ago

#12680 closed New feature (wontfix)

Floating submitbuttons

Reported by: shoyer Owned by: nobody
Component: contrib.admin Version: master
Severity: Normal Keywords: submitbotton design_ux
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: yes
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: yes

Description

If one have quite large forms in the admin you have to scroll a lot, even if you changed only one field in the upper section.
So i build a floating submitbutton bar. See screenshot

It currently dosn't work with IE6.

Attachments (2)

overlay.png (180.2 KB) - added by shoyer 4 years ago.
Screenshot
overlay.diff (1.8 KB) - added by shoyer 4 years ago.
Patch

Download all attachments as: .zip

Change History (9)

Changed 4 years ago by shoyer

Screenshot

Changed 4 years ago by shoyer

Patch

comment:1 Changed 4 years ago by shoyer

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Version changed from 1.1 to SVN

comment:2 Changed 4 years ago by russellm

  • Keywords design_ux added
  • Triage Stage changed from Unreviewed to Design decision needed

comment:3 Changed 3 years ago by mattmcc

  • Severity set to Normal
  • Type set to New feature

comment:4 Changed 3 years ago by julien

  • UI/UX set

comment:5 follow-up: Changed 3 years ago by ramiro

  • Easy pickings unset
  • Needs documentation set

Isn't this what ModelAdmin.save_on_top is for?

comment:6 in reply to: ↑ 5 Changed 3 years ago by anonymous

Replying to ramiro:

Isn't this what ModelAdmin.save_on_top is for?

I would say ModelAdmin.save_on_top solves the issue when the edit/change page fits in two screen of height. However, IMHO, it's quite common to have the edit/change pages spans over that when you have 2 or more inline formset for example.

I think this ticket would be a good candidate for django-ux.

comment:7 Changed 13 months ago by aaugustin

  • Resolution set to wontfix
  • Status changed from new to closed

Floating things aren't good for accessibility, especially on mobile devices.

Even if save_on_top doesn't suffice, this can be implemented with custom js/css, the admin provides hooks for this purpose.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.