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
{{ message }}
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Unfortunately IE11 doesn't support a mechanism for apply changes against running documents. Such a feature was added to Edge and I'm sure we'll consider it in the future :).
(Didn't mean to close this in such a hurry, sorry!)
The feature, editing a running document, exist in the JavaScript runtime for Edge (Chakra). It's similar to the V8 implementation in that it takes source content and a script id. I'll hunt around on MSDN to find the documentation. It's exposed in a similar manner to all the other diagnostic interfaces for Chakra, which is not at all like a JSON RPC.
Out of curiosity what's the scenario you had in mind? In a question I should have asked earlier.
One of my projects (amok) has a feature that spins up a file watcher on script parse and calls setScriptSource whenever the source changes, there's a bit more to it but thats the gist of it.
Now currently only chrome based browsers are supported, but am always looking to support more especially If I don't have to maintain the protocol bridge myself 😄
One of my next goals is to enable attaching to Edge (#48). Once that is done I can look into how much work it is to implement setScriptSource only when we are attached to Edge.
Activity
andysterland commentedon Jul 28, 2015
Unfortunately IE11 doesn't support a mechanism for apply changes against running documents. Such a feature was added to Edge and I'm sure we'll consider it in the future :).
caspervonb commentedon Jul 29, 2015
Just to be clear, It is currently implemented in Edge? Are the semantics the same as V8's implementation? Any resources with more info on this?
Until then, how about at-least implementing canSetScriptSource to always return false if it is not doing so already.
andysterland commentedon Jul 29, 2015
(Didn't mean to close this in such a hurry, sorry!)
The feature, editing a running document, exist in the JavaScript runtime for Edge (Chakra). It's similar to the V8 implementation in that it takes source content and a script id. I'll hunt around on MSDN to find the documentation. It's exposed in a similar manner to all the other diagnostic interfaces for Chakra, which is not at all like a JSON RPC.
Out of curiosity what's the scenario you had in mind? In a question I should have asked earlier.
caspervonb commentedon Jul 29, 2015
One of my projects (amok) has a feature that spins up a file watcher on script parse and calls setScriptSource whenever the source changes, there's a bit more to it but thats the gist of it.
Now currently only chrome based browsers are supported, but am always looking to support more especially If I don't have to maintain the protocol bridge myself 😄
alexcope commentedon Jul 31, 2015
One of my next goals is to enable attaching to Edge (#48). Once that is done I can look into how much work it is to implement setScriptSource only when we are attached to Edge.
caspervonb commentedon Aug 1, 2015
Sounds great 👍
caspervonb commentedon Jan 11, 2016
Been a while, any update on this? Edge support is still pending?
alexcope commentedon Jan 11, 2016
Other projects have taken higher priority for now. There is no ETA on when work will resume on this project. Sorry.
ckuetbach commentedon Jan 13, 2016
This is a great project. I am doing a lot of work with embedded WebViews and it helps a lot to debug the IE inside a MS Office WebApp for Word.