javascript - inserting iFrame to EmberJS templet gives "Metamorph that is not in the DOM" error -

-

मंदिर के लिए एक आइफ्रेम डालने के बाद: 

  & lt; iframe id = "ytplayer" Type = "text / html" width = "450" ​​height = "275" {{बाइंड-एटिर src = "वीडियो यूआरएल"}} फ़्रेमबॉर्डर = "0" स्वीकार्यलस्क्रीन & gt;

मुझे यह त्रुटि मिली: 

  अनक्यूट त्रुटि: मेटॉम्रफ़ पर कार्य नहीं कर सकता जो कि डोम में नहीं है।

मैं समझता हूं कि यह त्रुटि एचटीएमएल के भीतर हैंडलबार अभिव्यक्ति को लेकर आती है, लेकिन इसे बदलती है: 

  & lt; iframe id = "ytplayer" प्रकार = "Text / html" width = "450" ​​height = "275" src = "someurl" फ्रेमबॉर्ड = "0" स्वीकार्यलस्क्रीन & gt;

समस्या को हल नहीं किया केवल एक चीज जो समस्या का समाधान करती है वह मंदिर के पूरे आइफ्रेम को हटा रही है, जो कि वास्तव में एक इच्छा समाधान नहीं है।

कोई मदद कृपया?

सुनिश्चित करें कि आप iframes के लिए अंत टैग शामिल करते हैं। ऐसा लगता है कि जब आप अंत टैग को शामिल नहीं करते हैं, एम्बर उत्पन्न प्रारंभिक / अंत टैग के बीच मेटा स्क्रिप्टिंग का एक गुच्छा खुल जाएगा, जो एक आइफ्रेम के मामले में पहुंच योग्य नहीं होगा। नीचे दिए गए कोड के साथ अपना कोड बदलने की कोशिश करें। 

  & lt; iframe id = "ytplayer" प्रकार = "text / html" width = "450" ​​height = "275" {{बाइंड-एट्र = "VideoUrl"}} फ्रेमबार्डर = "0" स्वीकार्य लिक्विड & gt; & lt; / iframe & gt;

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more