Currently if the value used for a filter starts with #, the comparison operator is automatically converted from 'is exactly' to 'matches this regular expression'. 

So, if one needs to use URL fragment (starts with #) for element identification, for example, that # needs to be escaped. 

The workaround to use will be to change the comparison operator with 'contains' and use the fragment portion without the # sign.