Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - JavascriptBinding root #3570

Closed
bbday opened this issue May 18, 2021 · 4 comments
Closed

Feature Request - JavascriptBinding root #3570

bbday opened this issue May 18, 2021 · 4 comments

Comments

@bbday
Copy link

bbday commented May 18, 2021

I know at the moment is possible setup JavascriptBindingApiGlobalObjectName with custom name but it happear on
Object.getOwnPropertyNames(window) then is easy way to find it.

I think a better idea if we can choice where we can place root of object like in window.navigator or window.history or other objects, than can improve so much hidding service.

@amaitland
Copy link
Member

with custom name but it happear on
Object.getOwnPropertyNames(window) then is easy way to find it.

#3571 will allow for disabling creation of the cefSharp/CefSharp objects.

@bbday
Copy link
Author

bbday commented May 19, 2021

thanks for answer the issue is i use EvaluateScriptAsPromiseAsync i think you can do something like add temp object when promise start then will delete after execution (delete X).
Best idea to be paranoic is like wrote before create temp object in other root path like window.navigator

@amaitland
Copy link
Member

issue is i use EvaluateScriptAsPromiseAsync

You can likely achieve the same result using the DevTools protocol. You can execute DevTools commands directly (#3165)

https://chromedevtools.github.io/devtools-protocol/tot/Runtime/#method-runScript

i think you can do something like add temp object when promise start then will delete after execution (delete X).

That would be problematic for multiple concurrent calls.

If you (or someone else) would like to sponsor development then I'm happy to discuss further.

@amaitland
Copy link
Member

Closing as this isn't something I'm planning on implementing currently.

If someone would like to discuss sponsoring development then happen to discuss reopening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants