dilettante
MIS
I'm having this problem in IE 6.
Not sure whether it is an IE 6 bug or a bug/feature of HTML Applications.
In HTAs, the
(and
and
) act as no-ops. This is even true when I add the IE 5.5 attribute NAVIGABLE=YES (IE 5.5 introduced a new issue and this new attribute was the fix).
Here's a sample.
Create two files in the same directory:
test1.hta
test2.htm
Strictly speaking, the <HTA:APPLICATION> tag in test2.htm doesn't do anything. I included it out of desperation 'cause it is the only place that NAVIGABLE=YES might possibly go in the second page.
Click on test1.hta to start the ball rolling.
When it comes up, click on the link to test2.htm.
Next try clicking on the "Back" button to invoke
. Nuthin.
Click on the link to test1.hta and see that it reloads the first page.
Try "Back" button again. Still nuthin.
You can rename test1.hta to test1.htm (and fix the link in test2.htm) to see that this works fine in a normal browser window.
Any ideas?!?!
This is really annoying, because I need back/next buttons in an HTA I'm working on.
MS's own examples use this technique, though perhaps the difference is that they are using back/next buttons in a parent page that controls navigation within an IFRAME.
I was trying to use regular frames, with a navstrip frame (buttons) controlling the content within a main frame, along with a navbar frame at the left with regular links targeted at the main frame. The links work just fine (as do the links in the sample above). Just the buttons for back/next are screwed up.
I even have a "home" button in the navstrip frame that takes me back to my "splash" page, which is a non-frames page. This works fine, but uses
.
Pretty conventional layout.
Seems stupid to implement my own history buffer of URLs so I can use
but I may be stuck.
Not sure whether it is an IE 6 bug or a bug/feature of HTML Applications.
In HTAs, the
Code:
history.go()
Code:
history.back
Code:
history.forwardHere's a sample.
Create two files in the same directory:
test1.hta
Code:
<html>
<head>
<hta:application navigable=yes />
<script language="vbscript">
Sub btn_onclick()
history.back
End Sub
</script>
</head>
<body>
Now in 1.HTA
<input id=btn type=button value=back>
<a href="test2.htm">test2.htm</a>
</body>
</html>
Code:
<html>
<head>
<hta:application navigable=yes />
<script language="vbscript">
Sub btn_onclick()
history.back
End Sub
</script>
</head>
<body>
Now in 2.HTM
<input id=btn type=button value=back>
<a href="test1.hta">test1.hta</a>
</body>
</html>Click on test1.hta to start the ball rolling.
When it comes up, click on the link to test2.htm.
Next try clicking on the "Back" button to invoke
Code:
history.backClick on the link to test1.hta and see that it reloads the first page.
Try "Back" button again. Still nuthin.
You can rename test1.hta to test1.htm (and fix the link in test2.htm) to see that this works fine in a normal browser window.
Any ideas?!?!
This is really annoying, because I need back/next buttons in an HTA I'm working on.
MS's own examples use this technique, though perhaps the difference is that they are using back/next buttons in a parent page that controls navigation within an IFRAME.
I was trying to use regular frames, with a navstrip frame (buttons) controlling the content within a main frame, along with a navbar frame at the left with regular links targeted at the main frame. The links work just fine (as do the links in the sample above). Just the buttons for back/next are screwed up.
I even have a "home" button in the navstrip frame that takes me back to my "splash" page, which is a non-frames page. This works fine, but uses
Code:
top.navigate
Code:
----------------------------------
| Banner |
| |
----------------------------------
| [home][back][next][exit] |
----------------------------------
| Link | |
| Link| |
| Link| Main |
| Link | |
| Link| |
| Link | |
| Link| |
| Link| |
----------------------------------Seems stupid to implement my own history buffer of URLs so I can use
Code:
navigate