-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The page with form submissions is ugly on screens with >=1280px #3759
Comments
Proposed solution - we pull out the date search parts from the header completely.
All the search content would go under the <div class="nice-padding">
<form action="" method="get" novalidate>
<div class="col search-bar">
<ul class="fields row rowflush">
{% for field in select_date_form %}
{% include "wagtailadmin/shared/field_as_li.html" with field=field field_classes="field-small" li_classes="col4" %}
{% endfor %}
<li class="submit col2">
<button type="submit" name="action" value="filter" class="button button-filter">{% trans 'Filter' %}</button>
</li>
</ul>
</div>
</form> Note: we would need to ensure the form row is not centre aligned but other than that - it looks much better I think. |
We will aim to get this resolved as part of the UX unification work in the header - #8539 But in the mean time - marking as a good first issue for anyone to pick up. Actions required
|
- relates to wagtail#8539 - fixes wagtail#3759 - rename index_submissions to submissions_index (aligns with naming of all other index views)
Will be fixed by #8862 - new layout that streamlines the way the filtering shows. |
- relates to wagtail#8539 - fixes wagtail#3759 - fixes wagtail#3236 - rename index_submissions to submissions_index (aligns with naming of all other index views)
Issue Summary
The page with form submissions looks ugly on screens with >=1280px.
Steps to Reproduce
Result
Expected result
Screenshots
Viewport width 1280px-1215px (desktops):
Viewport width ~768px (iPad and other tablets):
Technical details
master
branch, commit e2b5dc3).The text was updated successfully, but these errors were encountered: