You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.
The position of the searchbox for filter on listview has some position issues, it has whitespace around it (not sure whether this is intended) but the bottom of the input field disappears behind the listview
I noticed this issue after 1.4 alpha, but didn't fix it yet because I want to make some changes. We added option inset for textinputs to adjust styling but I want to remove that option and do this a bit differently.
@frequent - Thanks, but no need to do a PR for this.
You can now use class ui-filterable on the input or its form wrapper to have the framework adjust the margin between the input and the listview.
Edit: I made some changes in the CSS. Class ui-filterable should be added to the form in which the search input is wrapped or the listview itself, not to the input element or its div wrapper.
@uGoMobi When I try 1.4.0a2 I am still seeing the same issue as presented in the example, my page only contains input and listview (they are separate as I read that would be the preferred method). If I put the input inside the ul it looks better but has other issues
See my previous comment. You have add the ui-filterable class to the listview or to the form element in which you wrap the input. http://jsbin.com/ofuhaw/214/edit
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The position of the searchbox for filter on listview has some position issues, it has whitespace around it (not sure whether this is intended) but the bottom of the input field disappears behind the listview
http://jsbin.com/ofuhaw/163/edit
I did manage to somewhat correct this with the following CSS change (update to margin)
.ui-input-inset, textarea.ui-input-text { margin: -1em -1em 1em -1em;}
The text was updated successfully, but these errors were encountered: