[missing] EmbedElement is missing contentDocument

[DartBot]

This issue was originally filed by kbeck...@gmail.com

---

In this example http://xn--dahlstrm-t4a.net/svg/html/get-embedded-svg-document-script.html
It is possible to access the contents of an SVG embedded with the embed Tag:
    
        function findSVGElements()
        {
            var elms = document.querySelectorAll(".emb");
            for (var i = 0; i < elms.length; i++)
            {
                var subdoc = elms[i].contentDocument;
                if (subdoc)
                    subdoc.getElementById("svgbar").setAttribute("fill", "lime");
            }
        }

Dart is missing the contentDocument property and thus this code can not be re-produced in Dart..

Karsten

[iposva-google]

Added Area-HTML, Triaged labels.

[efortuna]

Added this to the Later milestone.

[kevmoo]

Removed Area-HTML label.
Added Area-Library, Library-Html labels.

[kasperl]

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

[kasperl]

Removed Oldschool-Milestone-Later label.

[alan-knight]

Removed Priority-Unassigned label.
Added Priority-Medium label.
Changed the title to: "[missing] EmbedElement is missing contentDocument".

[DartBot]

This comment was originally written by robe...@hahn.email

---

Same issue with <object> tag.

[DartBot]

This comment was originally written by robe...@hahn.email

---

I just got informed that the access to contentDocument was intentionally blocked by the Dart team because of security issues.
However, I do want to give you a valid use-case which requires the use of accessing contentDocument.

See my question at Stackoverflow: http://stackoverflow.com/questions/29868564/extending-object-in-dart

[alan-knight]

From the StackOverflow question, you can't add the call to _blink, and you probably don't want to anyway.

Normally, if you call via JS Interop and get back an Element, we will convert that to a Dart element. So if you get contentDocument then it would be converted. If that doesn't happen, then there might be various reasons. It might be that we don't have a Dart type that matches that constructor. If that's true, then we might return Dart objects for other things that you do get from the contentDocument. But there are cases, like if things are cross-frame, where we don't recognize the objects. I'm not quite sure what happens there, but it might be that the constructors show as different. If that's the case I don't think there's an easy answer.