I have a strange issue with Internet Explorer [sic!].
When navigating through my pages, the back-button alwasy shows «processing» as the last entry - and after that the pages I really accessed. I always have to click the back-button twice (at least) to make the browser access the last visited page.
The pages have some jQuery in it as well as a linked in follow-button (that sometimes shows < > instead of the button when I click the back-button).
The linkedIn-Button is added via Javascript and resides in an iFrame - and I read some posts that iFrames can break IE's back-button. Alas, when I remove the linkedIn-Button, the problem persists...
I might also add, that the page is called with https (which might cause other problems in IE?)
Any ideas???
Related
For context, the problem I'm facing is that our business still has to use Internet Explorer 11 for some of our stuff. As a result, loads of people are trying to open newer sites (like mine) which are only accessible on newer browsers like Edge and Chrome. I have not accommodated for IE when building because it will be phased out completely from our business in the next 6 months.
I've tried to force users to open the link (to my site) in Edge, by using the link href edge-browser:http://google.co.uk/ however the problem with this is that if the user is already using Edge browser, Edge doesn't recognise the edge-browser: prefix and the link just times out! Very infuriating.
I'm wondering if anyone has a work-around, or whether there might be a way to script a button that tries the Edge link first and if it times out after 3-4 seconds, reverts to the second link instead? What about if there is a way of detecting which browser the user is using, and only showing them the appropriate link? I've trialed having two links present but our employees don't understand the difference or which link to press, and are complaining that the formatting of the site is all wrong when accessing via IE.
Let me know what you think - sorry, I am not very tech-savvy when it comes to browsers.
I have an intranet site with two hidden iframes that are made visibile once a user clicks on the corresponding nav menu option on the parent page. Both of these iframes point to pages I have created and contain code for page hits. I used lazy loading for each of these, and that prevented the iframe from incrementing their respective page hits until the page/iframe was actually made visible; but running Edge in IE Mode has now nullified that. Loading the site now increments all page hits regardless if the iframes are visible or not.
I've searched all over for any tips or tricks to get this working in IE Mode, but I haven't found anything yet. This all works perfectly in Chrome and Edge, but my company is running Edge with IE Mode; so here I am.... in search of answers. Thank you in advance!
I know this question was asked before, but I couldn't find an adequate solution that still works.
I have a little plugin, that consists of an iframe that has another iframe inside it. This structure makes sense since the first iframe only contains some text + button clicking on which opens the second iframe with the actual website (couple interconnected webpages)
It works pretty well on every browser except safari. On safari the actual website doesn't seem to be able to keep the session and on every request/page load it treats you as a completely new visitor.
What makes it weirder is that safari sometimes working just fine. For example I installed this plugin on 3 websites and 1 of them is actually working.
I know that safari just acts weirdly when it comes to session within an iframe, so I really wanted to see if this problem was already solved or is it still a huge issue for people who develop plugins similar to mine
I have the same issue. The iframe needs to be loaded as the parent page and save a cookie. Then the iframe will function as expected. Safari drops all cookies from a different domain in an iframe.
You can test this... clear your history and try a webpage that has the iframe (different domains for parent and iframe)... then load the iframe directly as a the parent page and use it... then go back to the original site and the iframe will work as expected.
I have found other applications that generate an iframe by JavaScript and the iframe keeps the data stored somehow with cookies.
I want my website's browser tab to be brought to front, when it is referenced by a hyperlink, regardless of any browser setting that may forbid this behaviour. I am aware that this is potentially a bad (or at least annoying) thing, however, my users are not allowed to change their browser settings (due to company policy) and are confused that apparently nothing happens, when they hit a hyperlink that references my website (although the existing tab is correctly updated of course but remains in the background).
There is one more constraint: Closing and reopening the tab is not an option, it must remain open as most hyperlinks will just add an anchor to the existing url which does not require a reload of the website.
I am open to any virtuosic HMTL or JavaScript tricks if there are any ;-)
Not sure this is something you can do with HTML/JS as you are trying to change the user's browser behaviour not your website's.
I'm still confuse by that :
...nothing happens, when they hit a hyperlink that references my website
(although the existing tab is correctly updated of course but remains
in the background).
Isn't it a normal browser behaviour with which people using the Internet are used to ?
I am having an issue where dynamically-created links are working on all devices I have tested (in all desktop browsers, on my iPhone, on my iPad, and on my Samsung Galaxy Tablets Chrome Browser), but will not work when clicked on Android phones (I've tested on three Android phones running Chrome, sorry don't have the Chrome versions, but one phone is really new and the others are 1-2 years old at most).
I am dynamically-creating the links to add items to a cart (inside of a larger dynamically-created entity) in a loop.
The link in question is constructed basically like this:
var itemHTML = "";
...
itemHtml += '...<span>\n'
...
Where gAddLink is just a standard URL. I am then inserting that itemHTML (in addition to other HTML) onto the page dynamically using document.write().
Since this is being dynamically created on page load (for reasons out of scope for this question, but it is a necessity), I know I have to have a click handler set up as so:
$('.elementToInsertTo').on('click', '.add2CartLink', function() { ... });
Where '.elementToInsertTo' is the parent element that is NOT dynamically created, and is present on the page at page load. There are multiple of these parents, hence why I can't use an element ID. Don't think it makes a difference though.
Again, I can confirm that the function call in this click listener works everywhere except Android phones (as far as I can tell). Any idea why this may be? I've read StackOverflow pages all day, but nothing seems related to this. I've read a bunch about JS closures (which may still be the issue) and the like, but none of that seems to be relevant since the link click listener is working on most all devices I have tested on (even the Android tablet's Chrome browser, which is the part that really is confusing to me).
If you happen to have seen this issue before or have any idea why this may be happening, please write it out before reading the next part, so as not to confuse or bias you.
Ok, now to the part that is even more mind-boggling, though I hope this only helps figure this out and doesn't confuse the situation.. I connected one of the phones to my computer with a USB and did some remote debugging using Chrome developer tools as described here (https://developers.google.com/chrome-developer-tools/docs/remote-debugging). I could confirm there that the click listeners were not working (they weren't being triggered)... (and now here comes the crazy part) UNTIL I did some element inspection on the link (i.e. the link was highlighted on my phone as I was inspecting the DOM-element in my browser, again using Chrome dev tools) and then clicked the link. This made it so that the click listener worked! What?? To debug further, if I inspected any of the DOM elements on the page and clicked the link, the click listener worked. If I changed tabs away from the dev tools tab, or simply stopped inspecting the DOM elements in Chrome Dev tools, the link click listener no longer worked. I really don't know what to make of this, but I'm hoping this part of information narrows down what may be going on with the Android phones and the click listeners.
Happy to try to provide any other info I can, though I am without the Android phone for testing at the moment.
Thanks!
Tap was still needed (thanks for both suggestions), but the issue was with a 3rd party JS library stopPropogation() call. Apparently this only happened on Android phones, but regardless, after removing the line, the click (on computers) and tap (on mobile) now works everywhere. Thanks!