Hi Matt,
I think what S was referring to was that Flow has some input elements that are a little unusual. When you delete/hide/suppress a topic in Flow, you have to give a reason. The reason field is a little unusual. I handled a few of those here: https://gerrit.wikimedia.org/r/#/c/161411/3/tests/browser/features/step_defi...
In this case, we have an input with no type at all that has to be clicked in order to transform or "morph" it into a text input. (It's fun to watch that element in the browser console when it gets clicked btw)
In this case, unless I am mistaken, Selenium recognizes the "closed" input element as a "button", which is normal behavior, and recognizes the same element "open" as a text input.
I don't think that's what's going on in my bug report below.
On Tue, Sep 23, 2014 at 9:39 PM, Matthew Flaschen mflaschen@wikimedia.org wrote:
On 09/22/2014 04:21 PM, S Page wrote:
We could make an intermediate Flow step definition When I enter "Foo" in morphing |field_name|
that turns into step I click in the <input field element> and it becomes a <textarea element> and I send_keys "My reply here" in the <textarea element>
but I'm not sure how in Ruby/Watir
For an example of such a meta-step, see https://git.wikimedia.org/ blob/mediawiki%2Fextensions%2FFlow.git/0e79d9d2f8edcb9e80b9f8200f9b62 7760d88c85/tests%2Fbrowser%2Ffeatures%2Fstep_definitions% 2Fflow_steps.rb#L26 .
Matt Flaschen
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee