On 09/24/2014 10:11 AM, Chris McMahon wrote:
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:
Yeah, that's what I understood as well (that he was talking about
changing from <input> to a <textarea>).
He said, "We could make an intermediate Flow step definition", but
indicated he wasn't sure how to do so, which is why I provided that example.
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.
That doesn't seem correct behavior by Selenium, if so. <input> and
<textarea> are both different forms of text input. <input> (or <input
type="text">, which is equivalent) is for one-line text input, whereas
<textarea> is multi-line text input.
You can see from http://jsfiddle.net/58j0f0wj/
that a simple <input> (no
attributes) if a one-line text input, not a button (the same is true of