Vaults question - Downloaded from the Wizards Community, all coding removed by Solauren

Vaults question

Post/Author/DateTime Post
#1
stanles
Dec 27, 2006 15:05:16 This is a question for anybody who uses the Vaults and uses Internet Explorer, or anybody who can solve the problem.

It appears, and I can confirm this, that anybody who uses Internet Explorer on the main Vaults page has a new window open for them with the page. This appears to only occur on the main page. This doesn't occur in Internet Explorer on the copy of the pages on my computer. It doesn't occur with Firefox on pandius.com at all.

I've tried to look on my control pages for the website, but can't find anything obvious which is causing this. Does anybody else out there know what might be happening or should I just go to the support people for the website?
#2
agathokles
Dec 27, 2006 16:09:45
I've tried to look on my control pages for the website, but can't find anything obvious which is causing this. Does anybody else out there know what might be happening or should I just go to the support people for the website?

Uhm, the only non-strictly html thing I can see is a bit of javascript at the beginning of the page. From the function and file names, it seems it should perform some animation, but it actually doesn't seem to have any effect (on Firefox, at least). Could you check whether that piece (the tag) appears on your local source (the one that doesn't have problems)?

GP
#3
stanles
Dec 29, 2006 16:18:30
Uhm, the only non-strictly html thing I can see is a bit of javascript at the beginning of the page. From the function and file names, it seems it should perform some animation, but it actually doesn't seem to have any effect (on Firefox, at least). Could you check whether that piece (the tag) appears on your local source (the one that doesn't have problems)?

GP

nah the javascript functioning should be independant of everything else, and yes it does appear in the local source which doesn't have any problems. It won't have an effect for you if you've un-enabled javascript, which is easy enough to do in Firefox.
#4
maddog
Dec 29, 2006 19:13:23
This is a question for anybody who uses the Vaults and uses Internet Explorer, or anybody who can solve the problem.

What version of IE? v5.5? v6.0? v7.0?
--Ray.
#5
stanles
Dec 30, 2006 1:39:42
What version of IE? v5.5? v6.0? v7.0?
--Ray.

I'm finding it on v6.0
#6
maddog
Dec 30, 2006 10:05:11
I'm finding it on v6.0

Interesting. I tried IE6 and didn't see anything wrong. Do you have any "special" addons for IE (Yahoo Toolbar? Google Toolbar?) or is it a plain vanilla IE6?

--Ray.
#7
zombiegleemax
Dec 31, 2006 6:46:23 I use IE6 and I've no problem nowseeing vaults...
#8
gawain_viii
Dec 31, 2006 10:15:26 I use both IE 6 and 7 on 2 different computers. I have never not had the front page links open in a seperate window. I had always assumed it was intentional due to a TARGET="_new" in the link's tag.
After looking at the source, I don't know what the cause is. It doesn't look like it should be the script, as the script identified in the header is only called by the mouseover in the PA graphic and not all the text links.

Roger
#9
culture20
Dec 31, 2006 12:35:32 Hmm, unless Shawn changed something in between your post and when I looked at the page, I only see a in the source.
That got me thinking (since I always use lower-case):, so I did a search for "case sensitive" and "_Top":
http://www.htmlhelp.com/reference/html40/head/base.html

So I'm guessing that IE treats "_Top" like "anything but _top _parent _self or _blank" which means that it attempts to match "_Top" to a named window, and when it fails, opens a new window named "_Top". Silly IE stick to common web standards like the rest of browsers.
#10
gawain_viii
Dec 31, 2006 15:14:05 I must've missed that. Yes, the base tag would apply to all the links on the page; and if a link can't find a page (or frame) called Top (it is not case sensitive) then it renames the current window as Top... except the _ designator specifies a new window... this that is the cause. Remove the underscore and that issue will be resolved.

On another note, however, I understand that some people don't like multiple windows opening all over the place, but I tend to like the fact that a link from the index page opens seperately... that way I can more easily cross-reference an almanc entry with an atlas entry without going through the trouble of manually openening a second window and typing the url a second time. But I suppose that's just because I'm lazy.

Roger
#11
stanles
Jan 01, 2007 21:39:45
Hmm, unless Shawn changed something in between your post and when I looked at the page, I only see a in the source.
That got me thinking (since I always use lower-case):, so I did a search for "case sensitive" and "_Top":
http://www.htmlhelp.com/reference/html40/head/base.html

So I'm guessing that IE treats "_Top" like "anything but _top _parent _self or _blank" which means that it attempts to match "_Top" to a named window, and when it fails, opens a new window named "_Top". Silly IE stick to common web standards like the rest of browsers.

The idea of that line was to ensure that anything which opened the index.html page opened it a new window itself. I'll try it without that and see what happens.
#12
stanles
Jan 02, 2007 12:11:21
I must've missed that. Yes, the base tag would apply to all the links on the page; and if a link can't find a page (or frame) called Top (it is not case sensitive) then it renames the current window as Top... except the _ designator specifies a new window... this that is the cause. Remove the underscore and that issue will be resolved.

On another note, however, I understand that some people don't like multiple windows opening all over the place, but I tend to like the fact that a link from the index page opens seperately... that way I can more easily cross-reference an almanc entry with an atlas entry without going through the trouble of manually openening a second window and typing the url a second time. But I suppose that's just because I'm lazy.

Roger

Yeah I got complaints about it so that's why I thought to try and remove it. I removed the line in entirety and it seems to work fine now in IE.

Post/Author/DateTime	Post
#1 stanles Dec 27, 2006 15:05:16	This is a question for anybody who uses the Vaults and uses Internet Explorer, or anybody who can solve the problem. It appears, and I can confirm this, that anybody who uses Internet Explorer on the main Vaults page has a new window open for them with the page. This appears to only occur on the main page. This doesn't occur in Internet Explorer on the copy of the pages on my computer. It doesn't occur with Firefox on pandius.com at all. I've tried to look on my control pages for the website, but can't find anything obvious which is causing this. Does anybody else out there know what might be happening or should I just go to the support people for the website?
#2 agathokles Dec 27, 2006 16:09:45	I've tried to look on my control pages for the website, but can't find anything obvious which is causing this. Does anybody else out there know what might be happening or should I just go to the support people for the website? Uhm, the only non-strictly html thing I can see is a bit of javascript at the beginning of the page. From the function and file names, it seems it should perform some animation, but it actually doesn't seem to have any effect (on Firefox, at least). Could you check whether that piece (the tag) appears on your local source (the one that doesn't have problems)? GP
#3 stanles Dec 29, 2006 16:18:30	Uhm, the only non-strictly html thing I can see is a bit of javascript at the beginning of the page. From the function and file names, it seems it should perform some animation, but it actually doesn't seem to have any effect (on Firefox, at least). Could you check whether that piece (the tag) appears on your local source (the one that doesn't have problems)? GP nah the javascript functioning should be independant of everything else, and yes it does appear in the local source which doesn't have any problems. It won't have an effect for you if you've un-enabled javascript, which is easy enough to do in Firefox.
#4 maddog Dec 29, 2006 19:13:23	This is a question for anybody who uses the Vaults and uses Internet Explorer, or anybody who can solve the problem. What version of IE? v5.5? v6.0? v7.0? --Ray.
#5 stanles Dec 30, 2006 1:39:42	What version of IE? v5.5? v6.0? v7.0? --Ray. I'm finding it on v6.0
#6 maddog Dec 30, 2006 10:05:11	I'm finding it on v6.0 Interesting. I tried IE6 and didn't see anything wrong. Do you have any "special" addons for IE (Yahoo Toolbar? Google Toolbar?) or is it a plain vanilla IE6? --Ray.
#7 zombiegleemax Dec 31, 2006 6:46:23	I use IE6 and I've no problem nowseeing vaults...
#8 gawain_viii Dec 31, 2006 10:15:26	I use both IE 6 and 7 on 2 different computers. I have never not had the front page links open in a seperate window. I had always assumed it was intentional due to a TARGET="_new" in the link's tag. After looking at the source, I don't know what the cause is. It doesn't look like it should be the script, as the script identified in the header is only called by the mouseover in the PA graphic and not all the text links. Roger
#9 culture20 Dec 31, 2006 12:35:32	Hmm, unless Shawn changed something in between your post and when I looked at the page, I only see a in the source. That got me thinking (since I always use lower-case):, so I did a search for "case sensitive" and "_Top": http://www.htmlhelp.com/reference/html40/head/base.html So I'm guessing that IE treats "_Top" like "anything but _top _parent _self or _blank" which means that it attempts to match "_Top" to a named window, and when it fails, opens a new window named "_Top". Silly IE stick to common web standards like the rest of browsers.
#10 gawain_viii Dec 31, 2006 15:14:05	I must've missed that. Yes, the base tag would apply to all the links on the page; and if a link can't find a page (or frame) called Top (it is not case sensitive) then it renames the current window as Top... except the _ designator specifies a new window... this that is the cause. Remove the underscore and that issue will be resolved. On another note, however, I understand that some people don't like multiple windows opening all over the place, but I tend to like the fact that a link from the index page opens seperately... that way I can more easily cross-reference an almanc entry with an atlas entry without going through the trouble of manually openening a second window and typing the url a second time. But I suppose that's just because I'm lazy. Roger
#11 stanles Jan 01, 2007 21:39:45	Hmm, unless Shawn changed something in between your post and when I looked at the page, I only see a in the source. That got me thinking (since I always use lower-case):, so I did a search for "case sensitive" and "_Top": http://www.htmlhelp.com/reference/html40/head/base.html So I'm guessing that IE treats "_Top" like "anything but _top _parent _self or _blank" which means that it attempts to match "_Top" to a named window, and when it fails, opens a new window named "_Top". Silly IE stick to common web standards like the rest of browsers. The idea of that line was to ensure that anything which opened the index.html page opened it a new window itself. I'll try it without that and see what happens.
#12 stanles Jan 02, 2007 12:11:21	I must've missed that. Yes, the base tag would apply to all the links on the page; and if a link can't find a page (or frame) called Top (it is not case sensitive) then it renames the current window as Top... except the _ designator specifies a new window... this that is the cause. Remove the underscore and that issue will be resolved. On another note, however, I understand that some people don't like multiple windows opening all over the place, but I tend to like the fact that a link from the index page opens seperately... that way I can more easily cross-reference an almanc entry with an atlas entry without going through the trouble of manually openening a second window and typing the url a second time. But I suppose that's just because I'm lazy. Roger Yeah I got complaints about it so that's why I thought to try and remove it. I removed the line in entirety and it seems to work fine now in IE.