On Google Chrome (37.0.2062.122, OSX / Windows), an iframe with an URL containing a fragment causes the parent elements to scroll up.
It\'s only happening in Chrome (tes
As other answers have already mentioned, the issue here is specific to JSFiddle. I can show you that with ease by simply including the same code within a StackOverflow snippet on this question:
iframe {
position: absolute;
top: 0;
right: 0;
bottom: 0;
left: 0;
width: 100%;
height: 100%;
}
This issue happens with every fragment URL passed into an iframe
on JSFiddle. Because of this, we can replicate this issue simply be creating a separate JSFiddle demo and linking to that in our iframe
.
I've created this new JSFiddle demo here: http://fiddle.jshell.net/JamesD/k5vk2u9h/1/show/light/#test.
As you can see, the fragment here is #test
. This issue is now replicable in a new JSFiddle demo using the following markup:
The height
and width
attributes are irrelevant as the issue still appears without them.
The other answer here suggests that the fix is to modify JSFiddle's own HTML in order to re-render the page correctly. This isn't a great solution as in a real world situation (i.e. when linking someone to a JSFiddle demo), they may not have the expertise to achieve this.
We can get around this by using JavaScript. As the new HTML document I've created is on the same domain (http://jshell.net) we can execute JavaScript within the iframe
itself. Manually setting the location.hash
property will also trigger this issue, so what we can do instead is scroll the iframe
directly to the element we wish to focus on.
Firstly, remove the fragment from the URL in the src
attribute of our iframe
:
As mentioned above, the fragment I've used is an element whose id
is "test". This means the easiest way to get our element is to select it by its id
attribute:
var frame = frames[0],
elem = frame.document.querySelector('#test'),
Here, frame
is a reference to our iframe
within our own document, and elem
is our #test
element. We can get our matched element's position by using getBoundingClientRect()
:
position = elem.getBoundingClientRect();
This will give us a ClientRect object like the following:
With this we now know that our #test
element is positioned 3034px from the top of our iframe
. Using this, we can now scroll the page ourselves to this position using window.scrollTo()
(where the window
of our iframe
in this case is held in our frame
variable):
frame.scrollTo(0, position.top);
Note that this solution will only work if the iframe
points to a URL hosted on the same domain or if CORS has been enabled on the page the iframe
is embedding.
After doing all this though, the best bet is to simply notify the developers of JSFiddle that this is a bug. I've raised this as an issue on their GitHub repository here: https://github.com/jsfiddle/jsfiddle-issues/issues/547.