Many Thanks for your great work with this theme
it get's better and better - well done!

When you make a

Taxonomy Exposed Filter Autocomplete

The Autocomplete field
Does not change width to
fit mobile or tablets

I know bug with the bootstrap
theme because I've tested the
same Taxonomy Exposed Filter Autocomplete field
on omega theme and the field changes width
to fit tablets and mobiles

I hope that's helpful feedback

#2 autocomplete.jpg38.05 KBMooff
Members fund testing for the Drupal project. Drupal Association Learn more


markcarver’s picture

Version: 7.x-3.x-dev » 7.x-2.x-dev
Status: Active » Postponed (maintainer needs more info)

Can you upload screenshots of what you are talking about, I'm not quite following. Thanks @charlie charles :)

Mooff’s picture

38.05 KB

Here is a screenshot what i think the problem is (i'm having the same). Autocomplete field causing a scrollbar cause it has a fixed width.

The autocomplete field stays at roughly 400px width. Even forced css rules like width: 100% !important don't help.

But here comes the strange part. I'm not using bootstrap, i'm using omega, the theme where charles said the problem doesn't show up for him (and thus google led me here).

Regardless of the theme, would be great if someone has an idea how to fix it.

markcarver’s picture

@Mooff, would it be possible to provide me (via my contact form) a link to where this is? I would like to inspect this properly because I cannot tell you why otherwise.

Mooff’s picture

Manged to (kinda) fix it for me via those rules (again i'm using omega).
I had to give the wrapper and the form a width.

// global.css for mobile styles
.views-exposed-widget .form-autocomplete  {
// different size for the normal style cci_alpha_defaul_normal.css
.views-exposed-widget.views-widget-filter-field_tags_tid {

link to the autocomplete in question:

440px in the normal style. Switches to 100% in the narrow (ipad etc.) and mobile.

Hope the information is helpful. Cheers.

markcarver’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

This issue has been closed while cleaning up the issue queue. This has likely already been fixed in 7.x-3.x. If it has not, please create a new issue describing the exact issue with that version. The 7.x-2.x branch currently only receives security fixes.