Custom dropdown selector
Public versus private fields
In Java, it is a custom to make all your fields private, unless they must be explicitly accessed by other sources. I believe this custom also applies to JavaScript.
Instead of having the element be a public (this) field, why don't you make it a private (var) field? There doesn't really seem to be another place you use it.
And, if there is another place that on using it in, why don't you create a getter? This would be a function that returns the field, and it might be named something like getElement.
This is up to you.
Defining the functions with Filter.prototype
You did exactly this, and that is perfect. Keep that up, it is a great practice.
querySelector versus getElementsByClassName
This is a matter of efficiency versus readability - whatever you chose to have.
It would be more efficient to use getElementsByClassName in place of querySelector in the link field, as the getElementsByClassName function doesn't have to do checks on the argument provided(whether or not the argument is a class, an id, a tag name, or a mixture); it knows it's looking for a one class and one class only.
It is slightly more readable having querySelector, as the syntax for it's arguments is the same syntax for CSS; it's a &quot;universal&quot; syntax.
Indentation
With only 2 spaces for an indent, your code looks fairly cramped. I recommend using tabs or 4 spaces as an indent.