Voting starts in March for the Drupal Association Board election.
Currently, Flexslider allows the user to substitute a CSS tag "namespace" in the advanced section of the Flexslider optionset. This namespace currently replaces the "flex-" namespace tag used in the flexslider styling. This does allow the user to override CSS styling on the flexsliders for each namespace, but requires creating all new styling for each optionset. This can create a ton of extra CSS if one uses several flexslider styles on a website.
Feature: the flexslider module should retain and apply the "flex-" tag on all elements and optionsets, and make the namespace option a second tag IN ADDITION TO the "flex-" tag. Why? Consider the following scenario:
I have two flexslider optionsets. The styling is similar for both but the paging buttons differ in style. If I want to use the custom namespace, I have to create all new styling for each element of the slider in CSS, even though I only need to change the styling of the paging buttons. If I have a lot of optionsets, (which I do) then I have completely new styling for all flexslider elements, because currently, there is only one unique tag (the value in the namespace field) attached to each element. The stylesheet for my flexsliders is well over 1000 lines because of this.
If there were TWO classes, (for instance class="flex-flexslider custom-flexslider") then I would only have to apply styling to the "custom-flexslider" class when that element differs from the default provided by "flex-". This would GREATLY reduce the amount of CSS necessary to style multiple flexsliders. In addition, since you already provide styling in the module for "flex-" new users will only need to use the custom namespace class to make changes to the default style.
(I hope this makes sense)