I am not sure if I asked the question in right way. But here is the scenario -
In a website we use Infragistic's controls. Which loads fine on ie9 but when we open the site in ie11 then the controls is not visible but just a text Table Control.
Below is an image -
I did some research and found out if I change the user agent string to Internet Explorer 9 on Developer's tool window then it loads the controls as expected.
Below is how it looks after changing the user agent string -
This is the setting -
Is there a way to change this user agent string somehow without a code change ? like setting on web.config ?
Thanks in advance.
Rohit
Related
I can't preview my Google Optimize experience. Google optimize throws below error:
This happens to me quite often too. The suggestion Google gives is wrong. Clearing cookies and restarting the browser does not fix it. Sometimes rebooting does, but that's a huge disruption.
What I found to work pretty reliably is to end the preview (dropdown), then click the EDIT button to go to the editor. Come back to the setup page, then try Debug again. Debugger should work again.
This is how it worked for me:
In Chrome go to Clear Browsing Data (chrome://settings/clearBrowserData).
Make sure you select checkboxes Cookies and Cached images and files.
Submit the form by hitting the button "Clear data".
Go to preview experience.
For me it started working when I gave the Google Optimize plugin access to all pages (not just the page running the experience).
I think I've found a fix for this. Go to the top right corner of chrome (the three dots) Settings > Privacy & Security > Cookies & other data > and add the url in the bottom section called "sites that can always use cookies"
Example
There can be multiple reasons.
Most obvious: enabled cookies like mentioned by others. should help
If it does not work even when cookies are enabled and you have restarted the browser then more chances are that the issue is in the Experience/Test that you are trying to preview. This can be due to:
A preview is already running in another tab. Turn off preview
2.You have set the experience to run on certain URL patterns and you are trying to preview on a page that does not qualify the criteria.
You have set some Audience rules which are not being met fully. For example: You have set the Audience Device type to mobile and you are trying to preview on a Desktop. Although Optimize will load the preview in a mobile mode but it will not be able to run the experience properly.
In my case the issue was due to wrong device type. I hope it helps.
It's also possible to get this "Unable to preview experience. Please make sure to enable cookies and restart the browser" error message if the content you're trying to modify doesn't exist when Optimize tries to modify it.
I had Optimize set to modify on page load, but the page I was working with was a form, where the text I wanted to modify didn't exist until I clicked through to the second step of the form (still on the same URL).
I was able to just run the study instead on another similar page that had all the text loaded at the start. I'd guess that setting Optimize to trigger from a custom event triggered upon loading the second step of the form instead of "on page load" would also have resolved the issue.
If you are using chrome then:
Click the context menu in the browser toolbar to the right of the
address bar.
Choose Settings.
Select/Search the "Security and Privacy" section.
Choose "Cookies and Other Site Data" Ensure that "Allow all cookies" is selected.
I am experiencing a lot of troubles with the new browser Edge in Windows 10. I am getting problems when I try to response.redirect a user after login to a default page.
The problem is that it outputs the content of the header to the page instead of redirecting me to the correct page. (see attached image) and if I refresh the page I get redirected correctly and the page shows up as it should.
The problem only appears when I try to use HTTPS along with my application and it only appears in Edge, all other browsers even previous versions of internet explorer works perfectly.
The code I use to response.redirect user is and to be sure iv'e added the https manually before I used Response.Redirect('~\Default.aspx)' which also works but just to be sure I added the https prefix manually using the below code.
Dim url As String = String.Format("https://{0}{1}", Request.ServerVariables("HTTP_HOST"), "/Default.aspx")
Response.Redirect(url)
I've stepped through the code and the content of the url looks like
https://localhost:44300/Default.aspx so it should work and it looks exactly like it does in every other browser where it works.
Image of the issue
Any known issues with Edge? I've also tried forcing compatbitlity mode IE9 / IE8 which doesnt seem to work in Edge with no luck, so I am running out of options.
The only way I can get this to work is to stop using https and force the use of http.
Any advice on what I can try next or perhaps do to fix this?
Best regards Marcus
I am using iFrame to load a url in a popup within a page.I want log in to the website and perform some operations.
All this happens in the same page within an iFrame in a modal.
Except IE all browsers work fine.But in IE after one or two steps the the website is directed to the home page.
I am not able to find why this is happening.
Any help is appreciated.
IE is know to be different, but I wont get into that old debate here.
Since you are logging in from an iFrame, there may be something regarding session variables which is making it fail.
Session in Iframe working in Firefox but not in Internet Explorer
Other than that, I suggest debugging using debug bar to see what type of XHR requests are being made, and then determine the exact point of failure.
I am using C# and ASP.net - Website
In my website, I need to set the IE browser by default for a particular page each day.
Is there any way to set it permanently?
There's no special treatment per page in visual studio. If you choose IE as default, then you have it for the entire project; it is also not permanent, changable whenever you want.
I have no one else to count unless this fantastic community, I know this is a non-programmer question but I can't figure it out why this is happening.
To a client I developed, using 960.GS a layout with a simple login user page / choose product / register products using .NET (ASP.NET 3.5) and all was ok, they agreed and I started ...
I then imported the HTML files I did and started to replace input with asp:TextBox's and the button into an asp:Button, really simple/basic stuff, but soon I click "View in Browser" I got my code all scrambled!
even if I see a XHTML 1.1 Strict Validated code, and CSS 2.1 Validate code
to try to get what's wrong, I put the ASPX file aside and open only the HTML page.
results are very different:
Opening directly in Firefox, with no web server:
alt text http://www.balexandre.com/temp/2009-11-22_1116.png
if I run the same page (exactly the same code) [HTML page, no ASP.NET page] through Cassini (Visual Studio Web Server) it shows .. ohh well...
alt text http://www.balexandre.com/temp/2009-11-22_1117.png
as well if I run that html page from IIS 7.5
alt text http://www.balexandre.com/temp/2009-11-22_1129.png
all 3 files above are the same page, being run through 2 different servers Cassini, IIS and the normal HTML render from Firefox.
using Firebug, all css loads well
screen cast: http://bit.ly/7ZBkuh (20 sec)
Does anyone have any idea for this behavior?
All help will be greatly appreciated, Thank you.
This looks like a css overflow problem. Are there any differences between the resultant markup/css from the browser (not the source file in the url bar) - eg, by comparing the "View page source" result? I suspect there will be. And i suspect that it's css related not markup.
It might help to run a diffing tool against your original HTML file and the output produced by your ASPX page. It will definitely be expected to see some differences, but it might still help you highlight what's going wrong.
This is only a guess, but perhaps the CSS styles that you are seeing in the ASP.NET-hosted pages are defined in the page, and the CSS styles that you are not seeing are defined in a separate CSS file?
If that is indeed the case, then the problem could be due to the way you have configured ASP.NET authentication in web.config. It may be serving up the HTML file but blocking the CSS file.