Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nasty lag in IE 6 when screen is updated #695

Closed
nvaccessAuto opened this issue Jun 11, 2010 · 7 comments
Closed

Nasty lag in IE 6 when screen is updated #695

nvaccessAuto opened this issue Jun 11, 2010 · 7 comments

Comments

@nvaccessAuto
Copy link

Reported by jteh on 2010-06-11 08:30
Str:

  1. Open Internet Explorer 6 and visit http://www.nvda-project.org/
  2. Move around the page with up and down arrows.
  3. Result: Whenever the virtual cursor moves to a new object (which causes IE to scroll), there is severe lag.
  4. Expected: There should be no lag.
  • This is a regression introduced by display model (c90061b).
  • Specifically, we've tracked it down to ExtTextOutHelper.
  • If NVDA is restarted, performance goes back to normal. This is because it is using a separate DC and then bit blitting back to the window DC, but we don't track this other DC unless we're running when it is created.
  • This doesn't seem to affect IE 8.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-07-14 05:00
Solution: disable display model for the "Internet Explorer_server" window class.

@nvaccessAuto
Copy link
Author

Comment 2 by mdcurran on 2010-09-06 02:34
Defering until 2010.3 as some more research needs to be done.
We will probably disable nvdaHelperRemote!ExtTextOutHelper for Internet Explorer_Server windows, but the question is whether getting the window class name will be slow anyway, especially since this code will run on all IE versions.
Changes:
Milestone changed from 2010.2 to 2010.3

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2010-11-24 05:36
Changes:
Milestone changed from 2011.1 to None

@nvaccessAuto
Copy link
Author

Comment 4 by Bernd on 2012-07-13 21:35
what about closing this ticket as wontfix and drop support for IE 6?

@nvaccessAuto
Copy link
Author

Comment 5 by jteh on 2012-07-15 23:34
Dropping support for IE 6 isn't an option, as it is at least needed to get up and running on a Windows XP system. That said, we're not too concerned about this as a common use case. However, we'd definitely consider a patch.

@LeonarddeR
Copy link
Collaborator

Five years after the last post in this issue, I think it is time for a won't fix anyway. Although IE6 might still be required for some users to use some time, it is very unlikely that this will ever be considered worthwhile to fix.

@derekriemer
Copy link
Collaborator

or a p4, I doubt it would get a PR though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants