After testing this story, I can confirm that this issue is functioning as expected. Decimals places are now allowed when using the Filter By feature and the feature seems to be functioning properly. Since this story is resolved and there seem to be no side effects related to this change, it will now be closed.

Make corrections to git history (remove commits for "merged lorainelab/master" ) then make the pull request.

Reviewing the issue...

The changes to the code are appropriate and sufficiently limited in scope.
The code base builds. And the feature now functions as expected. I tested it with the test case (which has decimal scores) and with another file generated by tophat and one by LL junctions. All looks good.

The commit history includes a merge from main master, we'll remove that commit and then I think this branch will be ready for a pull request into main master.

Fixed the bug.
Now the input box of score takes decimal values and filtering works correctly during the time of dev testing.
Also verified by applying different filters.
Moving to "Needs 1st Level Review" phase.

Branch: https://bitbucket.org/swathark/integrated-genome-browser/branch/IGBF-1204-DecimalScore

Test case file:
IGB Quickload > ChIP-Seq > ARR10 PRJNA263839 > peaks > line a1 BA-treated

Load a region of the file.
With the track selected, go to the annotations tab, select Label Field: score.
Zoom to in enough to see the score above the annotated regions.
See that these scores have decimal values.
In this region [ Chr1:9,329,031-9,329,932 ] notice that there are two annotations with scores between 1 and 2.

Right click the track name > Filter... > Add > select Score > enter a value of 1.8.

Currently it is not possible to enter 1.8 as a value here.
Change the input to allow decimal values.
If 1.8 is supplied, and the filter is applied, then one of these two annotations should be removed from view.

Verify that the correct one is removed using different comparators (>, <, =>).