Comment 6 for bug 1314924

Please note that setting "gfx.xrender.enabled" to false cannot be a permanent solution. It makes graphic rendering extremely sluggy over network connections, where X client and server are not on the same machine (and that's what X was designed for).

We deploy firefox in a client/server setup (Linux Terminal Server Project, LTSP), for 800 users. Their firefox display is extremely slow with xrender disabled. Scrolling down a page is a pain. Currently I need to tell mu users: "You can have gray boxes in the address field, or you can have slow scolling. What would you like?"

Setting "gfx.xrender.enabled" to false does *not fix* the issue, it just hides it by the cost of losing other features.