I am using the following javascript line to open a facebook app requests dialog:
FB.ui({ method: 'apprequests',
message: 'A request especially for one person.',
data: 'tracking information for the user'
});
When I click on the button that is to open this dialog in Firefox, it works just fine. However, in Chrome, the new window pops open, and immediately closes before any user action is taken.
Anyone know how to fix this?
Thanks
I had the same issues with chrome.
I fixed the problem by deactivating some add ons in the chrome settings, which may have been maleware, adblocker etc... now everything works as expected.
Related
i had took a look to another threads about chrome and custom protocol apps, but i couldn't resolve a doubt i've got. In my web app, when you click a button it fire a new tab with an webpage (window.open(url, "_blank")). The new tab is opened with the url (annother web app with https protocol). This url fire a javascript function on load that verifies some things and then generate a custom url, for example myurl://base64code, and put it in an existing iframe in this way windows.frames['myframe'].location.href=theCustomProtocolUrl. i tried in different ways (location.replace, create a new iframe and set the url, etc) and i always have the same problem. If i refresh (ctrl f5) the page it always show the dialog or if i open the link with the developer console opened. But if i click my button and the page is opened in a new tab it doesn't work only if i refresh (ctrl+f5). This works perfectly on IE11, it launch the app directly.
Any ideas why chrome, and edge, works like this?
UPDATE: I have found the reason, is i use the protocolcheck.js (https://gist.github.com/vladimirtsyupko/cfcd332476b16683bb0b) library.
First i tried to open a protocol with the timeoutHack (it use blur event) and then, after failing, it fires the other url (in this case https) and the dialog doensn't appear. I found a bug with blur event on chrome > 85 https://bugs.chromium.org/p/chromium/issues/detail?id=1137801
Thanks in advance
Clicking on a link to our webpage using
Link
opens a new tab and closes it immediatly. This happens on all browsers apparently. Deactivating adblock and alike does not change anything.
Using the url without target="_blank" or right click -> open in new Tab however works fine.
The web page is an angular project and does not use any sort of trackers. Furthermore this behavior started only recently, so I assume it's due to some change in the page.
Any hint why this happens or where to start debugging this?
Found it.
I had a line window.close(); due to a workaround for a popup for facebook login, implementing this:
Facebook Login not working in PWA app if app is in stand alone state
I am trying to add the "add to Homescreen" prompt function to my website. Now I've read the google developer articles and I have everything set up.
Now, If I try to manually add my page to the homescreen with the button "Add to homecreen" in the Chrome devtools > Application > Manifest , nothing is happening. A few times the console showed an error, but after fixing it nothing happens. I don't get the Add to shelf banner, but I don't get an error displayed in the console. Lighthouse doesn't show any error either. In fact, lighthouse shows a score of 92 in pwa.
Is this now meaning that everything is working? Is there an other debug function I've overseen?
Edit: If I press the button and than reload the page, after I press reload and the page is acctually loaded, the console displays:
Site cannot be installed: the page has requested the banner prompt be cancelled
I was having this same issue: Chrome Dev Tools Add to Homescreen was not working on ANY PWA. After days struggling trying to figure out where the problem was I finally found that Chrome main menu has an option to install the app, and that option is working fine. So you don't need to use Chrome Dev Tools option.
If you are testing in localhost, try http://localhost instead of 127.0.0.1.
I don't know why, but I have the same issue when using 127.0.0.1.
After changing to localhost, it works correctly.
The Chrome GA debugger does not appear to work. I can't find any info about how to fix it either.
There is an icon on the top screen. No window on the bottom, no readout. No feedback.
Compounding the problem is that searching for 'analytics debugger does not work' returns only results about setting up analytics or problems associated with GA or Chrome.
I'm starting this thread because none currently exists.
Anyone had this issue?
Are you sure you understand what it is supposed to be doing?
I just installed it. It adds a browser action button that changes state between off and on when clicked. It also reloads the current tab when clicked, but you have to reload other tabs if you need it to take effect there.
The information that GA module outputs goes to the page's JavaScript console. The extension does not automatically open it. You can open it with Ctrl+Shift+J
I found the answer.
You have to open the Chrome javascript console. I doesn't launch automatically.
I am using facebook's js SDK. I use FB.init to initiate the fb object and FB.getLoginStatus to check user's status. Everything works fine when load the page. But when i click some link inside my page and then try to go back to my last page by clicking back button of browser FB.getLoginStatus is not get invoke the callback. This problem occurs only in Chrome's. In all other browsers it works fine.
If i clear the browser catch and then go back then everything is working fine
I also remove the all extension that may causes a problem.
Thanks in advance.