Chrome extension: message from popup.js to content.js -

-

मेरे क्रोम एक्सटेंशन में, मैं popup.js से content.js । यह पॉपअप में एक घटना के आधार पर होने की आवश्यकता है, इसलिए इसे सामग्री या पृष्ठभूमि से संदेश पर ट्रिगर नहीं किया जा सकता है।

मैं यह परीक्षण करने के लिए सिर्फ निम्नलिखित कोड का उपयोग कर रहा हूं कि संदेश पारित किया जा रहा है या नहीं।

में popup.js : 

  chrome.tabs.query ({active: true, currentWindow: true}, फ़ंक्शन (टैब) { Chrome.tabs.sendMessage (टैब [0] .id, {ग्रीटिंग: "हैलो"}, फ़ंक्शन (प्रतिक्रिया) {चेतावनी (प्रतिक्रिया। फ़ेयरवेल);});});

में content.js : 

  chrome.runtime.onMessage.addListener (फ़ंक्शन (अनुरोध, प्रेषक, प्रेषण भेजें) { चेतावनी (प्रेषक.कैब? "कंटेंट स्क्रिप्ट से:" + sender.tab.url: "एक्सटेंशन से"); अगर (request.greeting == "हैलो") भेजेंसेस्पॉन्स ({विदाई: "अलविदा"});} ); ;

समस्या यह है कि संदेश केवल तब ही दिया जा रहा है जब मैं एक नया टैब खोलता हूं, तब नहीं जब मैं एक सक्रिय टैब में हूं।

यह विचार है कि उपयोगकर्ता पॉपअप में एक सेटिंग चुनने में सक्षम है, जिससे अलग डेटा के माध्यम से भेजने के लिए content.js का कारण बनता है। इसलिए जब भी कोई खास बटन क्लिक करता है, तब भी मुझे संदेश भेजने में सक्षम होना चाहिए।

क्या कोई कृपया मदद करता है क्योंकि इस बारे में हर दूसरे प्रश्न में मुझे संदेश पासिंग के बारे में Google पृष्ठ का लिंक दिखाई देता है। यह कोड वहां से सीधे है।


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