Neil Harris wrote:
Paweł Dembowski wrote:
by the
way, the frame issue was several times discussed on irc.
It seems most browsers do a total redirect. Only a couple of editors
reported the framing issue.
I do not know if *we* can do something on this.
Ant
I get a frame both in IE and in Firefox.
Could this be because the frame-breaking code in
http://fr.wikipedia.org/skins-1.5/common/wikibits.js is executed in a
<head> context, rather than a <body> context?
http://www.thesitewizard.com/archive/framebreak.shtml specifically
states that the frame-breaker code must be executed in the <body>,
not the <head>.
-- Neil
Working with some small test pages stripped down from the source code
seems to disprove the above guesswork, as putting the script in <head>
seems to work fine. However, using Firefox's Javascript console, and
visiting wikipedia.fr, I get the following error:
Error: uncaught exception: Permission denied to call method
Location.toString
However, visiting
http://fr.wikipedia.org/wiki/Accueil does not.
Writing a genuine exception into the Javascript code certainly does
torpedo the frame-breaking effect, as expected. However, the
Javascript console does not give a source code line for the error, so
it is presumably a low-level internal exception that is being caught,
as part of something else.
Could this possibly be because of the broken HTML syntax of the
wikipedia.fr frame-trapper page, which does not terminate its <head>,
and has no <body> element at all?
-- Neil
The answer to my own question appears to be "no", based on playing with
reduced test cases (see attached file). However, I'm now pretty
convinced that the uncaught Javascript exception is the most likely
cause of the failure to break out of the enclosing frame.
-- Neil