Closed (fixed)
Project:
Module Filter
Version:
7.x-1.0
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jan 2011 at 21:37 UTC
Updated:
21 Mar 2011 at 19:21 UTC
At page admin/config/user-interface/modulefilter the following text can be seen:
[x] Tabs
Themes module list into tabs.
[] Autocomplete
Enable this to provide autocomplete suggestions of existing module names in the module filter textfield. Currently only works if tabs are disabled below.
1. in the autocomplete explanation is written " if tabs are disabled below"
That should be " if tabs are disabled above"
2. Perhaps the first setting text can be changed into:
Divides module list into tabs
I read Themes as the plural of Theme and not as a verb. Which results in a weird line.
Comments
Comment #1
greenskin commentedSounds like good changes to me, especially the 'above' instead of 'below'. :D
Comment #2
henrijs.seso commentedThis above and below is irrelevant. New Form API allows easelly add items dynamically via AHAH so just add that checkbox if first one is off.
Comment #3
greenskin commented@LavaMeTender What happens if a user has JavaScript disabled? I have no problem hiding/showing the additional field but I don't think AHAH is applicable in a settings situation. The user, with JavaScript disabled, would have to save the form twice. Once to enable the visibility of the additional field and again to save it.
Comment #4
henrijs.seso commented@greenSkin Im still exploring and learning D7 but I bet they have solid system in place for no-js cases. I dont even remember how that feature was called, but there is an option to add something to form array that will load element if other element is checked.
Comment #5
realityloop commentedFixed in 7.x-1.4