backporting minor UI changes to keep QA scripts working

[Gervase Markham]

Frédéric Buclin wrote:
> I'm not talking about new features. I'm talking about typos of the form
> product -> Product. Selenium is case sensitive, so I have to write
> regexp of the form /(P|p)roduct/ in many places, and some Selenium
> commands do not accept regexp, so I would have to write |if (version ==
> 2.20) then "product" else "Product" end| in as many places. That's
> ridiculous for this kind of tiny UI changes (actually, I'm only
> complaining about the UI to admin products).

Perhaps we could set a bar by permitting changes to templates which
involve only outputted text, and not HTML markup or TT code? This might
try and balance the requirements of Selenium with the requirement for
stability.

Gerv