Tags: lozturner/mark.js
Tags
Implemented accuracy limiters option
Beside of a string value it is now possible to pass an object to "accuracy". This object must contain two properties, "value" and "limiters". "value" must contain one of the three possible values ("partially", "exactly", "complementary"), "limiters" must contain a custom array of string limiters for accuracy "exactly" and "complementary". Read more about this in the documenation.
Implemented 'noMatch' callback When called from within "mark()", this callback function receives the not found term. When called from within "markRegExp()", this callback function receives the not found regular expression. Also the callback function "complete" is now deprecated. Use "done" instead.
Fixed accuracy "exactly" with diacritics When searching for "ipsu" with "exactly" accuracy, you would expect only this exact standalone word to be marked. However, when searching with diacritics also "ipsü" inside "ipsüm" will be marked. This happens due to the fact that the word boundary will only match ASCII characters (and ü is a unicode character). This is now solved.
jquery.mark is now mark.js and waived now on any dependencies. That s…
…aid, jQuery is not necessary anymore. Neverthless mark.js still provides a jQuery API.
Other changes:
- The jQuery method "removeMark()" was renamed to "unmark()"
- The new option "accuracy" has been implemented (closes #25)
- The option "className" is now optional
- The default value of the option "element" is now "mark" and not "span"
- The option "separateWordSearch" is now enabled by default
- Unit tests are now splitted into separate files
- There are now two build templates, one for jQuery and one for pure JS.
Therefore the Grunt tasks have been changed
- The documentation is now available on the website
Detect empty iframe contents as inaccessible iframe When trying to access an inaccessible iframe an empty jQuery object will be returned in some browsers instead of throwing an exception. Therefore the 'complete' callback was not called. This will be fixed in this release.
PreviousNext