Ritika

> @colourmein13 it's not visible on the log level you used Yep, realized that a second after I posted.

Since Page Should (Not) Contain depends internally on is_text_present (xpath expression: `"xpath://*[contains(., %s)]" % escape_xpath_value(text)`), is it possible to alter that function to add case insensitivity and then perform a...

Yes, upper & lower case functions are part of Xpath 2.0 However, there is a workaround that works for Xpath 1.0: ``` //*[ contains( translate(., 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', 'abcdefghijklmnopqrstuvwxyz'), 'test' ) ]...

Here's a sample example I ran to check a non-ASCII character: ``` ` teXTĀ TeXTĀ textĀ texTā ` ``` xpath 1.0 expression: `//p[contains(translate(.,"TEXTĀ","textā"), "textā")]` This actually identifies all 4 p-tags,...

Do you want to use the xpath translate() solution or the Python string manipulation approach? How do you want me to proceed with providing an acceptable solution? Could you guide...

I believe keywords such as `Wait Until Element Contains` already have a case-insensitive implementation that involve conversion on the Python side. With regards to utf-8/utf-16/blns-- how exactly do you want...