I'm using Firefox 45.0.1 for testing my ASP.NET MVC web application. ELMAH shows following HTTP cookies being sent: __qca, __utma, __utmz, _ga, __utmb, __utmt
The only JS I'm using is modernizr, jQuery and bootstrap.
I'm not using Google Analytics in my application.
The only search engines in my Firefox are Wikipedia and Stackoverflow.
EDIT: Do not have Google Toolbar installed in Firefox
Where are these cookies coming from?
Are they appearing because of some Firefox extension I've installed? Or are they appearing because I'm signed into Google in another tab (how can that happen??) ?
Related
I am using an iframe in angular 14 application
the iframe src is application in the site in the IIS (same domain)
its work perfect in android
but in ios the iframe go to 404 page in the application
the application become one inside the other example
I did a lot of searching on Google and couldn't find any solution
I have developed a web application in angular 12 and ionic, and there is direction served from google api but when i click to get google direction, very often web page reloads in iphone safari browser.
Please help if you have solved similar problem.
I developed a webapp which is accessing a user's Google Calendar and which was
working fine using Google's OAuth in the browser. But when a user puts it to his homescreen on iOS, it says something like "OAuth is no more supported in embedded browsers".
After searching the web I found out, this message is caused by Safari which reports a different user agent when opening it from homescreen.
But still I could not find any solution to that problem. Seems like I have to change the authentication completely to get it working.
Is there a way to "fix" Safari or is there a another authentication method? (Already saw Firebase, but I am not sure if it will work in for my situation).
When I open the mail link with default browser as Google Chrome in Outlook,
it's opening in browser. I am expecting the link to be opened in application.
The way outlook lets users choose chrome as the destination for links effectively disables the universal linking functionality provided by the system. Basically, outlook isn't opening the raw link, which would lead to your app, it is building a mobile chrome URI per chrome's custom scheme. Until iOS provides users a method to choose a different browsers, apps rolling their own solution will continue to break system expectations.
I've been looking into adding Google sign-in on my Polymer-based website using the google-signin component seen here: https://github.com/GoogleWebComponents/google-signin
When I attempt to sign in through Chrome in iOS, nothing happens. I'd assume this is a problem on my end, except that I also cannot sign into the Google I/O 2015 website (another Polymer-based website): https://events.google.com/io2015/
Is this a known problem or something that's just occurring on my end?