I have problens sharing my AB tests. I see the Variants working on Chrome, but if I use for example Incognito mode or Firefox it does not show. I have tested using the share preview links and even logging in on these browsers and launching the preview from the Test page.
For example, here is a simple console log. The left is Chrome incognito and the right is regular Chrome. I've traced the console log code (the function inserted by GO) and it just shows in regular Chrome.
Any idea what is going wrong?
Thanks
Try to disable third party cookie blocking while browsing incognito mode:
Related
I've been hired into a company that uses ASP.NET for all of their external and internal sites. I'm not too familiar with ASP.NET.
I'm currently working on a external site that runs perfectly in Internet Explorer.
When using the site on chrome, I have certain pages that give me the 404 - File or directory not found.
What can I do to help prevent this error code from showing up when using this site the chrome?
From your description, I understand that your site is a legacy site that is compatible with the IE browser but it is not working properly with modern browsers.
The 404 error information generally informs us that something is not found but if the site works fine in the IE browser then it could be possible that the issue is something else. In that case, this is too little information to predict the cause of the issue.
You may need to provide detailed information about which exact piece of code has the issue. Which version of the Asp.Net project and which kind of project(Web application, web API, etc.) it is. You may need to modify your code or project to make it work with modern browsers including Google Chrome.
At present, if you don't want to make any changes in your code then you could try to use the IE mode in the MS Edge browser to load your legacy site.
You could configure the IE mode manually or using the group policy.
To quickly check it, Launch the Edge browser. Paste edge://settings/defaultBrowser in the address bar and press the Enter key. Add your page to the Internet Explorer mode pages. Visit your site, it should load properly in the IE mode in the Edge browser.
We have an Application Developed in ASP.NET inside which we have added an embedded Power Bi Dashboard using iFrame.
The Dashboard is working as expected in Chrome but facing the following issues with IE and Edge.
On IE the Dashboard is not being Displayed when viewed from the Embedded Application and upon clicking the power bi Sign-In button (shown within the Iframe), the application as a whole gets redirected to app.Powerbi.com/.... When you click the back button and refresh, still the sign-in prompt is shown in the iframe.
On Edge, the behavior is same as in IE, except that you click the back button from the app.powerbi.com website and then refresh the page, then the report renders correctly within the Iframe.
I tried clearing the Cache and Cookies, tried adding *.microsoft.com site and *app.powerbi.com to trusted sites list(per power bi forums) but still not working.
I suggest you check for the latest Windows updates and try to install it. Then after again try to test this issue on your side.
If the issue persists then hard refresh the page. Clear all the data for that site and again try to load the page.
I tested the issue with IE 11.1.18362.0 and Microsoft Edge 44.18362.1.0. As per my testing results, both browsers display the Power BI dashboard in ASP.NET site without any issue.
Output in IE 11:
Output in MS Edge:
If the issue persists then try to check the console to see whether there is any error or warning message. It can help to narrow down the issue.
I am building a website.
I built it locally, it works both in Chrome and in Firefox (when navigating the files locally)
I uploaded the files to amazon s3
and here's where I get some funky behavior.
if I use the amazon endpoint url to access the site:
it doesn't display properly in chrome, but it does in firefox. (what I mean by doesn't display properly is that parts of my css aren't being loaded in chrome, but they are being loaded in firefox)
if i navigate the local files on my machine:
it works just fine in both chrome and firefox. Everything is displayed perfectly fine and all of the css gets pulled in and rendered.
I guess what I'm curious about is, would behavior like this be an issue with Chrome or with Amazon AWS?
If parts of my css aren't even being pulled in by chrome (as in, when I open the developer tools, the css lines don't appear and I just get the default css associated with tags), it seems like this would be an issue with either chrome or AWS.
but when I use navigate the files locally in chrome, everything works just fine. So now I can eliminate Chrome as the culprit and point the finger at AWS.
But then when I use the aws endpoint in Firefox, it works just fine again...
So AWS isn't to blame either?
Im just curious why I'm getting different behavior based on how i choose to open the files, even though the files are the same both locally and on amason s3
UPDATE: So I sent an invalidation through cloudfront distribution.
Now when I visit the domain that I own and run the site off of, everything works both in chrome and firefox.
But the Amazon AWS Endpoint is still displaying improperly in Chrome despite the fact that the regular domain works... In the end, nothing is broken when the end user visits the site or when I edit the site locally, so it seems that the amazon endpoint is to blame.
If anyone has any ideas, now I'm just curious what the hell is happening inside of AWS
For my ASP.NET website, we are passing parameters in URL
e.g.: www.example.com/?parametername=parametervalue&utm_parameter=value2
In my code I'm trying to access this using
context.Request.Querystring["parametername"]
This works fine for firefox(normal and private mode), IE and chrome(only incognito mode).
For normal mode in chrome its not capturing the querystring parameters. Moreover this is happening only to few people while it works for rest of the team even in chrome.
Is there any setting in chrome browser that could have caused this?
Incase any one comes across such a problem you can use the app Fiddler. This helps in capturing and showing all detailed information about the url and its cookies set by web clients.
This helped me in identifying that problem was on my server side and not something that chrome was doing. Hope this helps someone.
When I try to hit my test webpage, I get a 503 error.
In the browser tab, the icon associated with my page. However, when I use Chrome Developer Tools, I don't see how that image is appearing.
I cleared my cache prior to hitting the page. Also, I had looked at the HTML and Network tabs, but do not see how the file is getting retrieved.
It is still an issue. See here. It has been pushed off for some time.