Review / enhance functionality of _WD_Frame* functionality

[Danp2]

• Proper setting of @error flag
• Standardization with other UDF functions

[mlipok]

Is this still a valid issue ?

[Danp2]

_WD_FrameEnter should be fine after all the recent updates. Looking at _WD_FrameLeave, I think it would be wise to review the coding associated with processing the webdriver response.

[Danp2]

AFAICS, all browsers are returning the same result for a successful switch to parent frame.

Firefox

__WD_Post: URL=HTTP://127.0.0.1:4444/session/78ef96d8-6bbd-472a-a1da-f43a5880fc29/frame/parent; Data={}
__WD_Post ==> Success [0] : HTTP status = 200 ResponseText={"value":null}
_WD_Window ==> Success [0] : Parameters:   Command=parent   Option={}
_WD_FrameLeave ==> Success [0]

Chrome

__WD_Post: URL=HTTP://127.0.0.1:9515/session/df4215a669b23dbedcf1da8927935b6a/frame/parent; Data={}
__WD_Post ==> Success [0] : HTTP status = 200 ResponseText={"value":null}
_WD_Window ==> Success [0] : Parameters:   Command=parent   Option={}
_WD_FrameLeave ==> Success [0]

Edge

__WD_Post: URL=HTTP://127.0.0.1:9515/session/eb4e5d6887c1c4bd9f2c76912f53f41a/frame/parent; Data={}
__WD_Post ==> Success [0] : HTTP status = 200 ResponseText={"value":null}
_WD_Window ==> Success [0] : Parameters:   Command=parent   Option={}
_WD_FrameLeave ==> Success [0]

Opera

__WD_Post: URL=HTTP://127.0.0.1:9515/session/266228571a93c951178f846ac1451c51/frame/parent; Data={}
__WD_Post ==> Success [0] : HTTP status = 200 ResponseText={"value":null}
_WD_Window ==> Success [0] : Parameters:   Command=parent   Option={}
_WD_FrameLeave ==> Success [0]