You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mentioned this problem in a different issue, which is closed by now, so I will try again with this specific problem in a dedicated isse.
The problem is simple to describe: Whenever there are double quote characters used in the web page / tab title, any configured command line will not work, because unexpected double quotes obviously mess up the command line syntax.
A proper, yet simple command line like like this will fail if there is a " in the web site / tab title:
What can we do to make this work? I was thinking of an option to replace double quotes with single quotes, but that is a rather low tech approach. Maybe an option to encode the values of the place holder(s) to BASE64 is the better approach, anybody can decode BASE64 encoded strings and we don't have any issues any more with special characters?
What do you think? o)
Thank you!
The text was updated successfully, but these errors were encountered:
Hello Sir! o)
I mentioned this problem in a different issue, which is closed by now, so I will try again with this specific problem in a dedicated isse.
The problem is simple to describe: Whenever there are double quote characters used in the web page / tab title, any configured command line will not work, because unexpected double quotes obviously mess up the command line syntax.
A proper, yet simple command line like like this will fail if there is a " in the web site / tab title:
What can we do to make this work? I was thinking of an option to replace double quotes with single quotes, but that is a rather low tech approach. Maybe an option to encode the values of the place holder(s) to BASE64 is the better approach, anybody can decode BASE64 encoded strings and we don't have any issues any more with special characters?
What do you think? o)
Thank you!
The text was updated successfully, but these errors were encountered: