GWT 历史和 IE6/7
我在 GWT 组上问过这个问题，但没有成功，所以现在我正在尝试 Stack Overflow :)
GWT 的历史和 IE6 / 7 似乎存在一些问题，我正在尝试确认这是一个实际问题与 GWT 一起，而不仅仅是我做过的愚蠢的事情。
我遇到的问题如下：
假设您有一些 GWT 应用程序可以插入到您现有的网站中。它有内部历史并且运行良好。我们就说它是一棵树吧。它是什么并不重要，重要的是它声明了您可以后退和前进。此应用程序的一部分是指向您网站其他部分的链接。单击其中之一即可退出 GWT 应用程序。
现在，单击这些链接之一后，请使用“后退”按钮。您返回到 GWT 应用程序，该应用程序加载良好，并且使用 URL 中的任何内容重新创建状态。
如果您再次点击返回，我会在 IE6 / 7 和 FF / Chrome / IE8 中得到不同的结果。在 IE6 / 7 中，第二个“返回”将我发送到 GWT 应用程序之前的页面。在 FF / Chrome / IE8 中，这一秒的返回让我回到 GWT 应用程序的状态，这自然是我想要的。
我检查了我的代码，据我所知，第二个“返回”直接转到之前的页面。无论如何，我的历史处理程序从未被调用过。
还有其他人遇到过这个吗？或者知道哪里讨论过这个问题吗？我用谷歌进行了广泛的搜索，但没有结果。
I've asked this question on the GWT group with no luck, so now I'm trying Stack Overflow :)
There seems to be some problem with GWT's history and IE6 / 7, and I'm trying to confirm this is an actual problem with GWT and not just something stupid I've done.
The problem I run into is the following:
Imagine you have some GWT app that plugs in to your existing website. It has internal history and works fine. Let's just say it's a tree. What it is isn't important, just that it has state that you can go back and forwards in. Part of this app is links to other parts of your website. Click one of those and you exit the GWT application.
Now, use the "back" button after you've clicked one of these links. You return to the GWT application which loads fine and the state is recreated using whatever is in the URL.
If you the click back again, here's where I get differing results in IE6 / 7 and FF / Chrome / IE8. In IE6 / 7 this second "back" sends me to the page before the GWT app. In FF / Chrome / IE8 this second back sends me back in the state of the GWT app, which is what I want, naturally.
I've checked my code, and as far as I can see, this second "back" just goes directly to the page before. My history handler is never called, at any rate.
Has anyone else run into this? Or know of anywhere this problem is discussed? I've googled extensively with no results.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
GWT 小组对于获得潜在错误的确认来说太吵闹了，它主要是针对初学者的。
当我开始假设 GWT 中存在错误并尝试从 GWT 组获得帮助时，我采取的方法是在 GWT 问题跟踪器中创建一个问题，并在 GWT 贡献者组中交叉发布。
以下是创建问题的 URL：
http://code.google.com/p/google-web- toolkit/issues/list
确保您首先在问题列表中搜索可能的重复项。
我还没有在 GWT 中使用历史记录，因为我们的应用程序在 IFrame 中运行，这就扼杀了实现历史记录的可能性。
The GWT group is to noisy to get confirmations of potential bugs, it's mostly for beginners.
The approach I take when I start to assume that there is a bug in GWT, and after trying to get help from the GWT group, is to create an issue in the GWT issue tracker and cross posting in the GWT contributors group as well.
Here is the URL for creating an issue:
http://code.google.com/p/google-web-toolkit/issues/list
Make sure that you first search the issue list for possible duplicates.
I've not yet played with history in GWT since our apps are running in an IFrame and that just kills the possibility to implement history.