![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
pop up window from FAA website disables Firefox browser?
When I login to the FAA AMCS application if there is a message to be read, clicking on the "View" button causes a pop up window to appear greyed out that disables Firefox browser? I should be able to click a button on the window that says "Confirm" to indicate I've seen the notice, but I have to actually close Firefox, login from a different browser to be able to click on that message in order to return to Firefox in order to login again to their site.
Сви одговори (7)
URL is: https://medxpress.faa.gov/loginnet/Home.aspx but you have to login to a secure website. Here’s a screenshot of the initial message. The first image is a screenshot of the screen once I've logged in. The 2nd image is what happens when I click the “View” button.
Once this pops up, I cannot click the “Close” button or anything else, including the “x” in the upper right corner to close the page. I have to close the browser and login again.
Mike
I spoke with the FAA support staff and learned that this problem is specific to Firefox browser and they are aware of it, but haven't been able to fix it. The cause has been known for sometime and they don't know the cause, so I guess I'll give up on this one, but it's an interesting technical question that the Firefox authors might want to investigate.
Hmm, the way the dialog text is hard to read makes me thing they put a shaded overlay in front of the dialog (higher z-order) instead of behind it. Firefox is a bit notorious about not letting you click through an overlay to a button or link behind it (some browsers ignore an overlay when it's just transparent or colored space). But that's just a guess and there isn't any convenient end-user workaround for this situation (the inconvenient methods involve using the developer tools or add-ons that let you remove elements from pages).
If you are familiar with developer tools like the Inspector then you can check what element is active and possibly remove/hide the overlay if that is what causing this.
You can right-click and select "Inspect" to open the built-in Inspector with this element selected.
If anyone's interested I've copied what's in the console upon inspection:
This page is in Almost Standards Mode. Page layout may be impacted. For Standards Mode use “”. Home.aspx INS: content-ads.js loaded: https://medxpress.faa.gov/loginnet/Home.aspx content-scripts.js:1:3512 TSS: content-tss.js loaded: https://medxpress.faa.gov/loginnet/Home.aspx content-scripts.js:1:12900 INS: content-blocked-items.js loaded: https://medxpress.faa.gov/loginnet/Home.aspx content-scripts.js:1:32488 CONTENT_SHELL: Page allowed. Skipping shell injection blocks content-scripts.js:1:32150 GET TAB ID RESPONSE: Object { tabId: 1 } content-scripts.js:1:14393 TSS: excluded result: Object { excluded: true } content-scripts.js:1:23560 TSS: Excluding content tss (trigger: send-mesage) content-scripts.js:1:14930 Error: Promised response from onMessage listener went out of scope 5 background.js:842:170 This page is in Almost Standards Mode. Page layout may be impacted. For Standards Mode use “”. MessageFrame.aspx INS: content-ads.js loaded: https://medxpress.faa.gov/loginnet/MessageFrame.aspx?msgID=1…June%204%201%20PM%20-%203%20PM%20CT&msgCreatedDate=05/31/122 content-scripts.js:1:3512 TSS: content-tss.js loaded: https://medxpress.faa.gov/loginnet/MessageFrame.aspx?msgID=1…June%204%201%20PM%20-%203%20PM%20CT&msgCreatedDate=05/31/122 content-scripts.js:1:12900 INS: content-blocked-items.js loaded: https://medxpress.faa.gov/loginnet/MessageFrame.aspx?msgID=1…June%204%201%20PM%20-%203%20PM%20CT&msgCreatedDate=05/31/122 content-scripts.js:1:32488 CONTENT_SHELL: Page allowed. Skipping shell injection blocks content-scripts.js:1:32150 GET TAB ID RESPONSE: Object { tabId: 1 } content-scripts.js:1:14393 TSS: excluded result: Object { excluded: true } content-scripts.js:1:23560 TSS: Excluding content tss (trigger: send-mesage) content-scripts.js:1:14930 Error: Promised response from onMessage listener went out of scope 5 background.js:842:170
I can only copy a line at a time from the Inspector and this is the first line:
I suspect the last line in the code above (Error: Promised response from onMessage listener went out of scope 5 background.js:842:170) could contain the answer to why Firefox can't open it: "onMessage listener went out of scope"
If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block content (Adblock Plus, NoScript, DuckDuckGo PE, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block content.
- make sure your extensions and filters are updated to the latest version
- https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content.
- click the shield icon for more detail and possibly disable the protection
You can check the Web Console for relevant-looking messages about blocked content.