Firebase web push notification in iframe is only working in firefox - firefox

I am using firebase for web push notification it is working perfect when I used it in same domain, but I have only one ssl domain and many non ssl website. So I have plan to use it in iframe and integrate this facility in all my non ssl websites too.
URL is
https://htmlcodeplay.com/notification/notification/index.html?websiteid=3
I have integrate it through iframe like below
<iframe src='https://htmlcodeplay.com/notification/notification/index.html?websiteid=3'></iframe>
I have integrate this lines into my blogger https://allinworld99.blogspot.in. But it is working perfectly in Firefox browser but not in chrome browser. No errors also displayed.
As per this link Does my web application require SSL for Firebase Cloud Messaging for Web to work?. It should not work, but how it is working in firefox browser.

I am not able to find a reference right now, but you want to do
embed a "push notification webpage" inside another via iframe
is blocked by Chrome for security reasons.

Related

Google Oauth2 in embedded browser (web view)

I added Google OAuth2 to my website. I noticed that when the website was opened in a embedded browser (web view), redirecting to google auth page (see the link below) will fail with error:
"403 disallowed_useragent".
Here is the link:
https://accounts.google.com/o/oauth2/v2/auth?client_id=813505898895-9vocl0haapnp562pn1hmut2sibregabn.apps.googleusercontent.com&response_type=code&scope=openid%20profile%20email&redirect_uri=http%3A%2F%2Fwww.antgora.com%2Fauth1%2Fsign-in%2Fgoogle&state=6515338772758876.%2F
I get that Google no longer allows OAuthrequests to Google in web view. But here is the strange thing. The google sign in demo
developers.google.com/identity/sign-in/web/sign-in work fine when opened in web view. I managed to find the client_idand redirect_uri used in the demo and replace them into the my google auth link (see the updated link below), the updated link can now magically open in web view.
https://accounts.google.com/o/oauth2/v2/auth?client_id=831371170934-udapit5jhjj56pft5l2drc9gjhfeclf3.apps.googleusercontent.com&response_type=code&scope=openid%20profile%20email&redirect_uri=storagerelay%3A%2F%2Fhttps%2Fgoogle-developers.appspot.com%3Fid%3Dauth58372&state=6515338772758876.%2F
Notice that I changed only client_idand redirect_url and nothing else. Later I found more client_idsthat also works with webview. I am wondering is there any specific settings for these client_ids to work?
Also I want to know what's the recommended fix to:
"403 disallowed_useragent"?
My website has no native app. And most likely, people will just open the website they received on online chat in a webview. I'd like to avoid showing the :
"403 disallowed_useragent"
error when they click *sign-in by Google*.

Record Firefox Web Browser session from my mozilla addon

I am developing a mozilla addon and now I have to record the browser session for a specific time as a video and sent it to the server. The recording of the web session will be triggered and stopped from my addon. How would I record the web session? Whether any jquery plugins are need to be added to my addon or is there any other source that addon sdk provides?
I got this working in an addon with about: pages, but I had to trick it into thinking it was https. The addon is a 27mb due to the inclusion of ffmpeg.js for converting video to different formats. So right now to download it you have to from my dropbox - https://www.dropbox.com/s/soemrqn2smmcge2/dist.xpi?dl=0
The code is here on github - https://github.com/Noitidart/Screencastify/
I used webrtc.

Javascript Origins for Embedded Feeds in Mobile Webview

I have developed an app which loads a html document from the mobile app storage that contain Yammer Embedded Feed javascript.
Recently, our company's Yammer admin received a message from yammer, telling that all Yammer Embedded Feed javascript will not work unless the domains have been specified in the "Javascript Origins" section.
However, since we are loading the html page directly from mobile, it is just like opening a html page in web browser with "file://" as domain. Can I add "file://" in the "Javascript Origins"? I have tried to "alert" the "window.location" and it returns "about:blank" on the mobile browser.
Thanks!
I answered this question over on the O365 Network, but let me add the answer here too in case someone has a similar question in the future.
The recent push to update your Yammer app's JavaScript Origins (documented/instructions here http://naomimoneypenny.com/2015/02/11/yammer-apps-javascript-origins-update/) affects only those using the JS SDK (specifically https://c64.assets-yammer.com/assets/platform_js_sdk.js).
It does not affect those using the Embed feed (specifically https://c64.assets-yammer.com/assets/platform_embed.js)

Kendo UI Without Server Side been hosted

OK Planing to Build small twitter App with Kendo UI . just wondering if that mean part of the app will be hosted in my server in order to get that work ?
I don't want host any part of the app at the server . i want this App to work directly Forward and backward from the app at user Device to twitter API
Please don't tell me it's just script will be hosted and the App that going to be created with Phonegap or whatever is just a Browser . Please don't tell me that
I am not sure I understand your question right but you can create a JavaScript only (no-server side code required) twitter client. You can embed all required JavaScript files and deploy them using PhoneGap.

Google Play badge with https

I need to integrate on my website a Google Play badge for linking to an Android app on Google Play, with https.
The badge generator offers the badge in http version: http://developer.android.com/distribute/googleplay/promote/badges.html.
On the other hand, this page gives the possiblity to download the desired badge.
Google doesn't seem to provide these images with an "https" url, which creates warning on the browser if the user is accessing the website with https.
I was wondering if I am allowed to host the image of the Google badge on the website that is using it, and therefore being able to access the image through https connection when desired.

Resources