Missing features, Flow Control and Store Variables

[babuto00]

Hello, first of all, thank you for your wonderful work! However what I miss are functions I used from Flow Control and Store Variable plugins in former Selenium IDE in FF. Would it be possible to include such functions in the new version? Without any using any plugins, I believe a lot of users would appreciate it. Thank you!

[corevo]

Yes, we plan on bringing these features built in the IDE Cheers, Tom

…

On 19 Feb 2018, 11:53 +0200, babuto00 ***@***.***>, wrote: Hello, first of all, thank you for your wonderful work! However what I miss are functions I used from Flow Control and Store Variable plugins in former Selenium IDE in FF. Would it be possible to include such functions in the new version? Without any using any plugins, I believe a lot of users would appreciate it. Thank you! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[bryanl-csi]

@babuto00 do you have a link for "Flow Control"? I'm not familiar with that one.

[idefix1]

I am not babuto00, but I guess he refers to this Firefox addon, which added flow control commands like gotoif, gotolabel and while to the old IDE.

There is also new Kantu IDE, and it already supports flow control in Chrome:
https://a9t9.com/kantu/docs/webextensions/selenium-ide#flowcontrol

[bryanl-csi]

Thanks!

Kind of surprised I never used that one.

[babuto00]

Yeah, it's that firefox addon idefix1 linked. It was pretty useful. Sorry for late response

[setiseta]

are there also plans for the commands: for and forxml??

[corevo]

for will be added, along side while,
forXml is a bit problematic, because it can read your filesystem, which is a bit of a security risk.
We'll have to take a look on how we can do this, while keeping our security policy as permissive as possible.

[setiseta]

thanks, sounds good.
yes filesystem is a bit critical.
at the moment i don't use forxml, but for.

[corevo]

Just dropping an update on our current thoughts,
We're going to add the following commands:

• if else end
• while do end

We'll need to give for a bit more thought before we implement it (UI terms mostly).
UPDATE: We will add times which will cover most of for's use cases atm

We're looking for a way to migrate the unstructured old flow control. (e.g. goto gotoIf label etc...)

[Jongkeun]

Do Store Variable controls include in #140 too?
For example, getEval, storeEval etc..

[corevo]

eval is a bit of a problem, but if also evals the target.
It's a problem we'll have to address, I don't know how, and I'm not sure whats gonna be the scope of the eval.
If we want a safer eval, we'll have to eval in an isolated environment, which means that storeEval and the likes are useless, since there is no access to the DOM.
But it might be enough for ifs.

[Jongkeun]

Why do you think eval's scope has a problem?
About security?

[corevo]

Yes, say we let you eval in the extensions scope, you can get the entire DOM as text.
And if we let you eval in the content side of things, you can add a keylogger to the tab.
The problem is that the only thing that stops a user from evaling something dangerous, is his responsibility to check what it does.
There are a lot of blogs that tell you, add this core extension to your IDE and it'll do magic for you, these kind of features are things that vendors (specifically Mozilla), won't stand for.
We have already been asked to remove all usage of eval in the extension.

[babuto00]

Hello, just checking in to see if there is any progress relating to the flow control (while command etc.)?
Thank you!