Currently, we are utilizing Selenium 1.0.1 for testing our web application by employing css and xpath selectors. In our experience, css selectors tend to be more reliable and function seamlessly in both FireFox and IE. However, on February 24th, a glitch arose where the contains function ceased to work as expected. Coincidentally, on the day prior, we integrated jquery into the problematic page.
The origin of this issue remains uncertain - it could have been triggered by the introduction of jquery or potentially stemmed from a browser update on that very day. Notably, the malfunction is persistent across both Internet Explorer and FireFox, suggesting an alternate cause.
Below is the CSS selector currently utilized: css=table#dashLayout_gauge0 option:contains('New Range')
In the past, this selector would successfully return the targeted element. However, presently Selenium fails to locate the said element using this specific selector. As a workaround, rewriting the selector with XPath has enabled functionality solely in FireFox, albeit not in IE.