Yes, this has happened randonly, but frequently to me as well fr at least as long as I can remember and dates back to earlier 7.x versions as well. I think it is just part of the mess that browse mode is in right now. Insert backslash usually does not do anything for it. Using some method of having the system load the page in again is usually necessary. In a lot of cases that is harmless, but of course remember in some cases reloading a page can duplicate a transaction, etc that you do not want to do. That is what makes it more than a minor issue that wouldn't matter too much. As we all know though, browse mode has so many problems right now in so many ways that I don't think you will see any fixes really until its replacement.
On 1/9/11, C.Richcreek <[email protected]> wrote: > This happens to me everyday that I am on the net . I use the incert > backslash, the F5 and the control shift A keys and sometimes nothing atall > works. Using IE8 as advised by one of the GW Micro tech that I won't mention > right now. I guess that it will just keep being like this until we get that > Brows Mode rewrite.Happy New Year? ofcorse, Craig R > > -------------------------------------------------- > From: "jim grimsby Jr." <[email protected]> > Sent: Thursday, January 06, 2011 1:02 PM > To: "Don H" <[email protected]> > Cc: "gw-info" <[email protected]> > Subject: Re: WE saying only top and bottom > >> hi, what happens if you refresh the buffer with insert back slash. >> hth >> >> Jim Grimsby JR. >> Skype name: Jim.Grimsby >> Skype number: 909-498-4711. >> E-mail: [email protected] >> Twitter: Jgrimsby >> >> -------------------------------------------------- >> From: "Don H" <[email protected]> >> Sent: Thursday, January 06, 2011 10:17 AM >> To: <[email protected]> >> Subject: WE saying only top and bottom >> >>> I reported the problem to GW where at least in my case when using IE 8 in >>> >>> what seems to be a random way WE will only announce top and bottom after >>> the page loads. If you close IE and try the same web site it works fine >>> thus I can't give GW a step by step to cause the problem. >>> Is anyone else experiencing this problem on a more consistent manner so >>> as to provide GW a method of duplicating it? >>> If you reply to this message it will be delivered to the original sender >>> only. If your reply would benefit others on the list and your message is >>> related to GW Micro, then please consider sending your message to >>> [email protected] so the entire list will receive it. >>> >>> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can >>> manage your list subscription at http://www.gwmicro.com/listserv. >>> >> If you reply to this message it will be delivered to the original sender >> only. If your reply would benefit others on the list and your message is >> related to GW Micro, then please consider sending your message to >> [email protected] so the entire list will receive it. >> >> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can >> manage your list subscription at http://www.gwmicro.com/listserv. >> >> > If you reply to this message it will be delivered to the original sender > only. If your reply would benefit others on the list and your message is > related to GW Micro, then please consider sending your message to > [email protected] so the entire list will receive it. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > manage your list subscription at http://www.gwmicro.com/listserv. > > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
