How to get some kind of walkable DOM Document out of CEF?

[KatrinaS]

Hiya, the title really plus as an extra maybe how add some kind of like change listener to the Context that updates the Browsers view of the Document,, I know about the Javascript and yes that seems easy enough, but surely there's a better more, I dunno, more industry standard way, I don't mind having to get down and dirty into the CEF source to provide some plumbing and JNI to return some kind of Element tree or whatever, but C/CPP is not my first language and I really have no idea where that Rabbit hole starts, where is the single root (or roots) of where that all starts?

[KatrinaS]

I see that there is Functions and Window Binding / RenderProcessHandler but this doesn't seem to be the same / JCEF CefRenderHandler(Adapter), like that isn't RenderProcessHandler

[magreenblatt]

JavaScript is the industry standard way.

[KatrinaS]

There's no way (that I am aware of) to return a fully fleshed out window.document, Element, Node or whatever, Object, but of course if you have written the Document you don't need it

Edit, edit. CEF seems to be able to (potentially) return Objects via (I think) CefV8Accessor,, why can't we (I) just plumb in GetValue("document.documentElement.childNodes");,, calling Setters on perhaps a zillion Elements seems clunky via Javascript but that said, it'll be the same amount of calls on the Document but without (perhaps) the overhead or more overhead

[KatrinaS]

And (on having a cursory squizz) why is dom_document_impl.cc not plugged in / exposed?

[KatrinaS]

The thing just needs return something that implements (more or less), there's a lot of overlap :

javax.swing.tree.MutableTreeNode;
javax.swing.tree.TreeNode;
org.w3c.dom.Attr;
org.w3c.dom.DocumentFragment;
org.w3c.dom.NamedNodeMap;
org.w3c.dom.Node;
org.w3c.dom.NodeList;
org.w3c.dom.TypeInfo;
org.w3c.dom.UserDataHandler;

And catches / throws :

org.w3c.dom.DOMException;

Don't make me have to maul your code with cackhandedness

[magreenblatt]

This isn’t something that we are interested in for JCEF. If you need such a representation you could just parse the HTML file contents in your application.

[KatrinaS]

CEF obviously has it, it seems a glaring and crippling omission just for MuH bElOvEd jAvA but okay

[magreenblatt]

This was answered in your previous thread at viewtopic.php?f=17&t=19502#p53834

[KatrinaS]

I beg to differ but okay, I can have access to everything as long as it's a String and if I want access to the actual DOM I have to plumb it myself or parse a String that's already been parsed by CEF,, gotcha This unreasonable coveting of the DOM is ridiculous