WE are having a gwt application which was working properly till IE10 versions.
But unfortunately the same application is not running as expecetd in IE11.
Th issue is --->we have a simple login page which takes credentials.This page succesfully gets authenticated in all IE verison till IE10.
We are clueless why the same login pag eis not working in IE11.
I included '' in my hml file.
we are not yet lucky.how to solve this?
thanks in advance.
Have you compile the code using Break Point does your compiler is compiling the onclick event of the button use for login because authentication issue is not related to UI i think something is going wrong on back code of button.May be possible the application is not able to find the button id.
Related
I'm trying to add Google Signin to our login page. I've followed the code supplied by Google, as well as a GitHub project that I used for code example. Both work perfect on Chrome, FireFox, Safari, but I can't get it to work on IE11 or Edge.
The GitHub project is at https://github.com/googleplus/gplus-quickstart-javascript. This project uses Google's newer apis.google.com, however I've also tried plus.google.com as suggested in another post. Neither work.
I added a data-onfailure function to the button, and get an error "popup_blocked_by_browser" even though the popup blocker is turned off in the browser. Even though I get this popup error, I do get a popup that asks which Google account to use, but when I choose one, I get the "The webpage your are viewing is trying to close the window" message. If I choose Yes, the window closes, but I don't get logged in.
Anyone have any advice for getting this to work in IE or Edge?
I ran into this problem on IE 11 with Windows 10.
I fixed it and then it happened again after receiving Windows Updates - annoying!
Here is what fixed it for me; it was an IE Setting.
Go to:
IE -> Internet Options -> Security
Check "Apply" and then "OK" To exit.
IE Settings Screen Shot
Finally, restart IE.
I am testing my website in all browser, and suddenly I encounter this problem in safari browser version 5.1.7. The app crashes and there is always a popup which as shown below when I clicked to another link on my website. I am using windows 7 OS. Why is this happening? Is this because of my code?
Any answer is very much appreciated.
I'm having an issue with Sahi Open Source logging into Mailtrap.io
the script is quite simple:
_navigateTo("https://mailtrap.io/");
_setValue(_textbox("email"), "emailHere");
_setValue(_password("user_password"), "passHere");
_click(_submit("Log in"));
however only first line of code executes.. as soon as I reach mailtrap.io then controller looses grip on html... In case I launch new browser from Sahi Dashboard and navigate to mailtrap.io, then Controller window is not coming up on Alt+doubleClick..
I added SSL cert. Anyone had this issue before? Anyone successfully using sahi with mailtrap?
Cheers.
I got it to work i think.
First I installed Sahi OS 5.0 and opened the firefox browser. With the SSL Manager I added security exceptions for sahi.example.com and mailtrap.io
On navigation to mailtrap I got an error:
Content Security Policy: The page's settings blocked the loading of a resource
This is a browserfeature and can be turned off in the about:config https://stackoverflow.com/a/27324485/1359903
Now the script runs and the controller can access the sites elements. I hope this works for you too.
Regards
globalworming
I am part of the developer team for a quite a large online system using ASP.NET(4).
Asp.net Ajax completely breaks down for Webkit browsers and we are getting full page postbacks when we should be getting partial only for the UpdatePanels.
I am starting to believe it has something to do with my Application Configuration, mainly for the following reasons.
If I move the ajax enabled controls to a new project they will work as expected for all browsers, including Webkit.
I created a static .aspx file with nothing but an UpdatePanel,ScriptManager and a button making a literal visible on click.
I get no Javascript errors from any browser, and i see an http request for the asp.net-ajax (ScriptResource.axd) in both Firebug and Chrome Developer tools
I tried ye'old safari fix from this highly referenced thread
Edit: After a bit more testing and http sniffing i noticed a major difference between the test application and the actual application. The test application generates 2 additional .axd files which are not generated from the actual application. These WebResource.axd, seem to contain data related to the async postback. However this is only the case for Webkit browsers. The WebResource.axd files are generated for Firefox as i can see them in firebug
What i am asking from the community, is any ideas or suggestions as to what could be the cause of this problem and if i am correct to assume that the problem is probably on the server side
Thanks for any help
The problem was due to a deprecated config file that's used to limit the content that bots/spiders/crawlers receive, which was loading by mistake thanks to our lovely inhouse CMS
In short if u get behavior similar to my case, check your or configs
I was having a similar issue however my problem was with all browsers and not just webkit. I ended up going through and tearing up the web.config file and found out that a line: <xhtmlConformance mode="Legacy"> was preventing webresource.axd from working properly. The fix was to simply remove that line from my web.config file.
For a little more information on xhtmlConformance, visit http://technet.microsoft.com/en-us/librarY/ms228268(v=vs.85).aspx.
If you scroll all the way to the bottom you'll notice it explicitly states that it causes issues with webresource.axd and scriptresource.axd.
I am running a site using Umbraco 4.
In Safari (Mac) when I refresh the page I get a completely blank page; the page appears to have finished trying to load.
I'm using a lot of JavaScript so I tried to removing all JavaScript but the error still persists.
The site is here
http://www.dreamguts.com/
I would really appreciate any input.
I have done some digging on this and it would appear to be a bug in Webkit:
https://bugs.webkit.org/show_bug.cgi?id=26621
The bug report suggests that disabling the WebCore cache via Debug menu may help.
Tim