I'm creating a HTML page where I have a textbox and on button click if validation is true navigate to next page otherwise show alert.This functionality works fine in Firefox and Chrome but not in IE9.What happens is it just navigates to the next page no matter what the validation is.If i allow the activex to view the contents then it checks for the validation before navigation.This is a great security threat.How do I stop this navigation if it's validation is false.Any Suggestion?
Related
i had took a look to another threads about chrome and custom protocol apps, but i couldn't resolve a doubt i've got. In my web app, when you click a button it fire a new tab with an webpage (window.open(url, "_blank")). The new tab is opened with the url (annother web app with https protocol). This url fire a javascript function on load that verifies some things and then generate a custom url, for example myurl://base64code, and put it in an existing iframe in this way windows.frames['myframe'].location.href=theCustomProtocolUrl. i tried in different ways (location.replace, create a new iframe and set the url, etc) and i always have the same problem. If i refresh (ctrl f5) the page it always show the dialog or if i open the link with the developer console opened. But if i click my button and the page is opened in a new tab it doesn't work only if i refresh (ctrl+f5). This works perfectly on IE11, it launch the app directly.
Any ideas why chrome, and edge, works like this?
UPDATE: I have found the reason, is i use the protocolcheck.js (https://gist.github.com/vladimirtsyupko/cfcd332476b16683bb0b) library.
First i tried to open a protocol with the timeoutHack (it use blur event) and then, after failing, it fires the other url (in this case https) and the dialog doensn't appear. I found a bug with blur event on chrome > 85 https://bugs.chromium.org/p/chromium/issues/detail?id=1137801
Thanks in advance
Clicking on a link to our webpage using
Link
opens a new tab and closes it immediatly. This happens on all browsers apparently. Deactivating adblock and alike does not change anything.
Using the url without target="_blank" or right click -> open in new Tab however works fine.
The web page is an angular project and does not use any sort of trackers. Furthermore this behavior started only recently, so I assume it's due to some change in the page.
Any hint why this happens or where to start debugging this?
Found it.
I had a line window.close(); due to a workaround for a popup for facebook login, implementing this:
Facebook Login not working in PWA app if app is in stand alone state
I have a single page PHP application that fetches data from a third party API and outputs the items in a product grid. Clicking on one of the products leads to an external url which opens in the same window.
When using the back button in Chrome to go back på the application after clicking the external link, the page reloads for some reason. I'm only experiencing this problem in Chrome, therefore I'm wondering if it could be a Chrome related bug?
Found the issue. It was caused by using a window load event incorrectly.
First, this issue only occurs in any version of IE and works correctly in Firefox and Chrome.
I have a form which is on a page inside an iframe. I am submitting the form to a page on our other web site. When the form page is on top (not in an iframe) all works fine. If I place this same form in an iframe and submit the form, a new window opens as expected however none of my form values arrive at the target page. This smells like an IE bug or security/permissions setting. Again, it works perfectly in Firefox and Chrome.
I am seeing the issue whether I add target="_blank" to the form tag or I add it say via jQuery after the form loads.
I am using ajax to populate parts of my html pages (when the page load or based on user click).
When I press the back and forward button using Firefox (4) or Safari (5.0.5) everything is fine. But when I press them using chrome I only get the last ajax result (if I press back) instead of the last page in the history.
I tried working with the history.pushState and popstate event but The popstate event is fired when the page load and not when I press the back button which is counter intuitive.
Use History.js it normalizes the behavior between browsers and optionally provides a hash fallback for html4 browsers.