You may simulate the default case by having a status variable telling whether a match was found in the loop or not.

The advantage of this approach is that the code to execute for each class is arbitrary, like the one in the switch statement in your example all the cases performed a similar operation, but tomorrow you may need to do different things for each.

Having no break after fnsi allows the code to be executed whenever there is a match - so that if the element has, f.i., class1 and class2, both fn1 and fn2 will be executed.

for(var i in fns) iterates through the keys within the fns map.To have different behaviour according to the class, you may use function references, or functions, within a map: function fn1(element) console.log( elm3, ' has class 'a': ', elm3.hasClass('a') ) Ĭonsole.log( elm4, ' has class 'a': ', elm4.hasClass('a') ) This is a test stringįelix's trick of adding spaces to flank the className and the string you're searching for is the right approach to determining whether the elements has the class or not. Var elm4 = document.querySelector('text') // SVG textĬonsole.log( elm1, ' has class 'a': ', elm1.hasClass('a') ) Ĭonsole.log( elm1, ' has class 'b': ', elm1.hasClass('b') ) Ĭonsole.log( elm1, ' has class 'c': ', elm1.hasClass('c') ) Ĭonsole.log( elm1, ' has class 'd': ', elm1.hasClass('d') ) Ĭonsole.log( elm1, ' has class 'a c': ', elm1.hasClass('a c') ) Ĭonsole.log( elm1, ' has class 'a d': ', elm1.hasClass('a d') ) Ĭonsole.log( elm1, ' has class '': ', elm1.hasClass('') ) Ĭonsole.log( elm2, ' has class 'a': ', elm2.hasClass('a') )

TESTS (see browser's console when inspecting the output) If( className.split(classArr).length > 1 )

If( this = null || !classArr || !className ) return false

Js contain