-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Promised response from onMessage listener went out of scope #5066
Comments
The outcome of the step 3 is not guaranteed as testing on another Backrop website gave the same error much later and probably as a result of hovering on different elements on the website. Not sure which one exactly tigers the error, but could be hovering the main navigation menu block. |
Does Backdrop have anything to do with this? I'm not sure, because chrome.js is part of Firefox, not Backdrop. @alanmels What's your Firefox version? |
Somehow, they addressed this issue on https://www.drupal.org/project/linkit/issues/2886455#comment-14042215 without touching Firefox.
The newest: |
I did a search on https://www.drupal.org/project/linkit/issues/2886455 for "firefox" and "chrome.js" and nothing came up @alanmels 🤔 ...wrong link? |
They are not discussing particularly Firefox or Aside from all, could you please confirm you can replicate the error or is it just me? |
I can't reproduce. Could it be that some FF plugin interferes? Also, I don't know what sort of bug this could be. Is there any problem on your Backdrop site besides that console nagging? The Drupal issue you referred to handles totally different stuff (Linkit module and entity translation). |
@alanmels I also wasn't able to reproduce on latest MacOS, initially with FF v87, then after upgrading to v88. I used a fresh installation of Backdrop via https://backdropcms.org/demo, and switched to "Console" while inspecting the home page. I waited more than a couple of mins each time, but the only error in the console was this:
I should note that:
|
Just wanted to note this has been raised here: #4276 |
I just found this issue from search engine results. I am getting the same error messaging on an unrelated project. It appears, according to Mozilla, to be error messaging about missed events in a browser extension.: https://bugzilla.mozilla.org/show_bug.cgi?id=1643186 I suggest disabling all your Firefox extensions and then attempting to reproduce the error. |
Thanks for taking the time to chime in @prettydiff 🙏🏼 @alanmels do you agree that this is browser-related? We had nobody else report this, and we cannot reproduce it. |
I am facing same problem here, using ajax to transfer some js variables to the backend raises this bug. |
@yesminee have you already tried to disable all browser extensions? Our conclusion so far is, that the problem isn't directly related to Backdrop, but has something to do with browser internals. |
I am experiencing the same in Firefox developer tools. I don't spend all my time with that open so who knows it may be happening all the time. Nonetheless, I followed advice to use another browser and in the case of Brave (a chrome variant) I see a different message:
I am not sure if the two are related or if this is a separate issue? |
The following suggests the issue on Firefox may be related to Screenshot components, |
Sorry for missing this question, @klonos. To say frankly, I moved on and not sure if it was completely browser issue or some combination of browser and Backdrop's response to what browser was expecting. I don't mind if you close the issue. |
I have resolved the Firefox issue: In my case it was directly related to the Awesome screenshot extension. Disabling that one extension eliminates the issue in Firefox. I realized it might be this because in the past I noticed that extension would occasionally kick in with a keyboard shortcut combined with the comment in the Firefox queue that it may be related to Screenshot components. This is great because I don't use that extension anyway, it's a hangover from the past. I much prefer the Nimbus extension. My observation may lend support to the view it is an extension issue, just which one may be hard to tease out for each person. Maybe, the other observation apparent in Chrome should be a new issue? |
Off-topic: my favorite open source screenshot/screen-recording software that aren't browser extensions:
|
@klonos Thanks for suggestions. I downloaded flameshot and may give it a try but I really like Nimbus for browser screen captures. It can capture part or all of the page including scroll and supports annotations. Very useful. As for this thread I am inclined to close this issue. Just hope everyone has had a chance to see that it can be resolved with removing the offending browser extension. |
Description of the bug
A freshly installed Backdrop website is giving the following error on Firefox's Developer Tool inspector:
The line 88 looks as:
and the function - as:
The whole file can be seen by pasting this to your Firefox's address bar:
Steps To Reproduce
To reproduce the behavior:
Additional information
Some entries beginning from comment #42 and further down could be relevant.
The text was updated successfully, but these errors were encountered: