MJ> Your argument is based principly on the premise that every page on the web is either a text chat interface or owned by Facebook. JG> No my argument is not based on this at all. My argument is based on the fact that there is no brows mode buffer. My argument is based on the fact that line counts are not provided by the dom or any accessibility API there for window-eyes would have to get this information by hand. This would start to be a problem when you have the type of pages I described. It would very likely cause system lags while it was trying to provide this information. Not only that do to the fact that you don't have a virtual buffer any more the jump to line commands are no longer useful. Not only this but the line next and previous commands are used on all web pages having this information does not give you any kind of advantage. MJ> There are a fair number of pages where the information is pretty static if not totally so.
JG> Yes this is true. More and more often though this is the acception rather then the rule. You can't assume this is going to be the case. If we could then there would have been no need to replace the buffer. MJ> You say after a page update the information would no longer be valid. Surely, it wouldn't take much to implement a sort of update ping or message which would be triggered each time the page was updated. Jg> It would be extra code that would not really accomplish much as I explained. Not only that but do you want this refresh update check for figuring out how many lines are on a page to run every time a page is updated. If you were on a page that did update quite a lot as I said this would add load to the system. Maybe if you would explain exactly what you want to do with this line count. I don't see what advantage having this information gives you any longer. >Um mat if the information is not going to be correct after a page updates >then what is the point of having the information. Not only that but your >contention that a page setels down after a few secons is not correct. >Consider a chat web page that is being updated every few secons as a user >posts information to it. consider facebook or twitter that is being updated >every few secons as information comes in to it. not only that but the >summery feature is intended to let you know what keys are available on a >page. You know that no matter what you can review buy line so having this >information seems to me to be pointless. Exactly what advantage do you see >in having this information considering the fact it will be quickly wrong? > > >-----Original Message----- >From: mjw [mailto:[email protected]] >Sent: Monday, November 24, 2014 10:41 PM >To: GW Micro Product Discussion Listserv >Subject: RE: control shift s in browse mode > >It was a useful feature for a variety of reasons. The algorithm Doug >refers to would be unnecessary to the feature in the new version 9 >because I for one wasn't asking for live update of the number of >lines. the user would be aware that a dynamic page is not static and >page content along with the number of lines may change. That said, >most dynamic pages I can think of tend to settle after a few seconds >of being loaded into the browser. > >Matt >At 03:51 25/11/2014, you wrote: > >As a user, I think it should be a feature the user decides to turn on or > >off. I understand this could slow the rendering of web pages down, but I > >also think it could be useful. Sometimes I currently use that information >to > >try and guestimate how long the web page is or how long it will take me to > >read. Plus, what if you wanted to create a mobile site and want to make it >a > >certain length vs. the regular site. It could just be used more as a > >measuring stick for us. Perhaps there are other uses as well though. I > >haven't downloaded the beta yet so will this hotkey speak the number of > >links, frames etc.? That's definitely useful. > > > > > >Andre > > > >-----Original Message----- > >From: MJ Williams [mailto:[email protected]] > >Sent: Monday, November 24, 2014 7:19 PM > >To: gw Micro Product Discussion Listserv > >Subject: Re: control shift s in browse mode > > > >With respect, I disagree, it makes much sense to have line numbers, > >even with dynamic pages. For example, if the user was also informed > >that the content was dynamically updated he would be able to decide > >what to do with the information. > >Sincerely, Matthew > >At 01:05 25/11/2014, you wrote: > > >Matt, > > > > > >No, line numbers are no longer available. Giving line numbers with > > >today's dynamic pages doesn't make sense any longer. Many pages > > >continue to grow as you go down it. So line numbers are no longer > >relevant. > > > > > >Doug > > > > > >On 11/24/2014 7:59 PM, MJ Williams wrote: > > >>In browse mode, Control shift s used to read out, among other > > >>things, the line number and the total number of lines on the page. > > >>Is there a substitute for it in v9? The hotkey no longer returns > > >>the same information. > > >>Matt > > >>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. 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.
