I deploy a html5 based web chat application.
I'm an admin not an author of the web chat app.
I log in as user1 and minimize a web browser or switch back to the chat tab.
I configured an option to play a sound when a new user enters a room.
It seems that sound notification is suspended until the user1 open the chat tab again.
So far I saw this behaviour on Chrome on Windows and macOS + Safari on macOS.
I guess that it's some sort of "user comfort protection" or performance saving function.
Can someone give me an idea if it is a browser or OS related?
Can this be disabled?
I welcome any clue how to troubleshoot this problem.
thank you, Jan
Related
We are running a captive portal WIFI solution.
When people connect to it websites such as Google and Facebook are blocked.
We want to allow users to go to our partners websites but they have network requests to Google and Facebook.
The only way around this that I can think of is running a headless chrome instance on our server and allow our users to connect to that. Our users would need to control the headless instance from their browser.
Is this possible?
Does any one have any other suggestions of how I can get around this problem?
I'm currently working om something like that https://github.com/KaanDoesNothing/Browser-Proxy
I am currently developing a kiosk application and have been trying to use the "Manage kiosk applications..." option in the Chrome://extensions page when developer mode is on.
Whenever I choose an application in the manage kiosk applications popup it just saying invalid application. I've tried local IDs, Chrome Web Store IDs and still nothing works.
In the manifest I've allowed kiosk mode and have another version with kiosk only enabled but that still doesn't work.
This is not a hosted app, all the assets are local and the Chromebook is not managed.
I've tried other solutions such as logging out and pressing ctrl+alt+k at login. I've wiped the chromebook and restarted fresh.
Any help would be appreciated.
If you're not hosting the app in the Chrome Web Store, Managing Kiosk Applications should be done by entering the app ID and the URL of the third-party web server in the Specify a Custom App dialog and click Add.
You may check Create a Chrome Kiosk App to know more details on how to create, publish and add the app as kiosk app.
Kiosk apps can only be installed from the "Manage kiosk applications..." menu if they are published in the Chrome Web Store as either "Public" or "Unlisted". If the app is published as "Private" it will fail to load.
I have Windows Phone 8 emulator running and a sample app is registering and I receive the URI but when I try to send a notification, I'm not receiving in the emulator. I used to be able to use the sample app with WP7 emulator and it was working and I'm able to access internet on the WP8 but not the notification. Any pointers to fix this will be great!
This is what I saw happening:
1- If I didn't open the app after receiving multiple notification it looks like the OS will not show notification anymore.
2- if you try to send too many notifications.
3- If the app is open the notification will not show as a toast.
4- Sometime I had to open the browser and go to website to force the device to connect to the internet, probably because the phone was on wifi.
It's a pretty open question, since there might be multiple problems, but start with this (source: MSDN):
The push client service on Windows Phone Emulator must be ready before
you can use push notification APIs. Push client service on the
emulator takes two minutes to activate after you start the emulator,
starting from when the Start screen first appears.
I'm developing a Google Chrome Extenstion, I wonder if there is anyway to show desktop notifications even if Chrome is closed, maybe some sort of background process or service? Kindly advice and guide me if it is not possible also. Thanks.
If you request a "background" permission your extension's background page will be able to show notifications even with Chrome windows closed.
When any installed hosted app, packaged app, or extension has "background" permission, Chrome runs (invisibly) as soon as the user logs into their computer—before the user launches Chrome. The "background" permission also makes Chrome continue running (even after its last window is closed) until the user explicitly quits Chrome.
If you use Google Chrome, you can enable a new Gmail feature that shows desktop notifications for new messages. Go to "Settings", and enable chat notifications and mail notifications to see a small bubble when you get a new message.
Secondly: Using WCF or Windows Services:
you have to develop simple client on machine polling a central service for alerts. Each alert should have a unique id so each client can deal with idem-potency
I Hope that this will be helpfull to you
Regards: Azeem Raavi
I'm running into what seems to be a serious usability problem for users trying to use a Google Drive app from more than one account. In order for an app to be able to use Drive APIs on a user's behalf, the user must install the associated Chrome Web Store app while logged in as that user. The problem is that the Chrome Web Store seems to look for an app being installed per browser, whereas the Drive API needs the app to be installed per user.
As far as I can tell, the only way to install the same app for multiple users in the same (Chrome) browser is to install with one user, then log in as the second user, uninstall the app (which the CWS says is already installed), and then reinstall it (so that Drive will mark the app as installed for the second user). This is a very confusing experience, because during this process the app and the CWS are sending the user mixed messages about whether the app is installed.
I'm not sure if there's a canonical app to test for system bugs like this. Is DrEdit live somewhere? But if you want to see the problem behavior in our implementation, install the Graphing Calculator by Desmos.com as one user, launch it and log in using google drive and verify that everything is working. Then log out from the app, and use https://accounts.google.com to log in to google as a different user, and try using the app again. The app will tell you that it isn't installed (that's what Drive's APIs are telling us) and direct you to the CWS, which claims that the app is installed.
We are aware of the issue. And I agree this is a really bad experience for users using the same Browser (and the same Chrome session). One of the issue is that the account you are logged-into chrome can be different than the account you are logged into Google Web (Gmail, Chrome Web Store, Drive etc...) Therefore the Chrome Web Store has to make a choice to either use the apps's install status on the Browser or the Web Google account.
If you write an FAQ for your users maybe you can suggest that the most effective way to install the app for the second user is to simply install it using another browser like Firefox. Especially since Firefox won't be impacted by this issue because the app doesn't get installed on Firefox, only on the Drive account :)
The bug is filed internally, now we can only wait for it to be prioritized and fixed/sorted-out. We are also working on some other way for apps to have an install flow that doesn't involve the Chrome Web Store so that it will be less impacted by all of he Chrome Web Store/Chrome browser intricacies.
I'll make sure to ping our eng team on that issue again.