Screen blurring when scrolling

Screen blurring when scrolling

Something new on my PC when using Opera 10.51 is for the screen to "blur" when scrolling.

The "blur" occurs either directly above or below any application I have running that stays "on top" of the maximised Opera window.

Normally "DU Meter" is running the whole time on the bottom right of the screen and it is above this that I first spotted the "blurring". I then tried "JR Screen Ruler" and "Pixie" a colour picker, and got the same "blurring" effect.

It only happens in Opera 10.51, not previous versions, nor other browsers, nor other applications.

An easy solution is to turn off the "on top" utilities but I would prefer Opera 10.51 not to blur.

Has anyone else had this happen? Any suggestions?

Tony
Melton Mowbray

Its a known issue. It still affects 10.52, but perhaps not to the same degree. I find a problem with the progress bar overlay if scanning an image, but FastStone Capture's toolbar is now OK on its own.

This is trivial, isn't it?

Using Opera 10.51 build 3315 and Opera 10.52 build 3370.
My sig cannot be edited due to forum changes.

Originally posted by Pesala:

This is trivial, isn't it?

So you're saying that anything that doesn't result in a crash is trivial? Aside from the still standing MDI problems this was by far the most disruptive to my regular workflow in earlier 10.5x releases.

Originally posted by TonyBeckett:

Has anyone else had this happen? Any suggestions?

The 10.52 snapshots fixed this for me, for example this here. Some people report it still occurs now and then, though. You should do a separate install, backup your data etc. because snapshots may always be at risk from messing things up. That said, since it's an RC it should be fairly stable. Just don't blame me if it messes something up if you didn't properly backup your data.

Originally posted by Frenzie:

So you're saying that anything that doesn't result in a crash is trivial?

Don't be silly. I would have thought that you had some practical experience of beta testing and would know the difference between a trivial cosmetic issue and one that seriously interferes with the use of the product.

Here are definitions of bug priorities from JIRA — a professional bug tracking system. Copy to a note for future reference.

• Blocker — Blocks development and/or testing work, production could not run
• Critical — Crashes, loss of data, severe memory leak
• Major — Major loss of function
• Minor — Minor loss of function or other problem where there is an easy work-around
• Trivial — Cosmetic problem like mispelt words or misaligned text.

Thus this is a trivial issue, as it just corrupts the screen temporarily. Zoom in/out with the scroll wheel to redraw the screen if you really need to keep an application floating on top — otherwise, minimise the application. (Using a shortcut to zoom to your preferred zoom level will also redraw the screen as will opening the panels)

Originally posted by Pesala:

Thus this is a trivial issue, as it just corrupts the screen temporarily. Zoom in/out with the scroll wheel to redraw the screen if you really need to keep an application floating on top — otherwise, minimise the application. (Using a shortcut to zoom to your preferred zoom level will also redraw the screen as will opening the panels)

Why didn't you say that in the first place? Saying it's trivial at best alludes that there may be one or more easy solutions. The obvious solution is of course not to run anything on top, but that's pretty much a non-solution since that's the problem in the first place. The zooming in/out is a good workaround that I wasn't aware of. Does zooming from 100% (or whatever) to 100% (or whatever) also result in a redraw?

Originally posted by Pesala:

Minor — Minor loss of function or other problem where there is an easy work-around
Trivial — Cosmetic problem like mispelt words or misaligned text.

Seems more like minor to me then. Saying all cosmetic issues are by definition trivial seems to be begging the question.

Thanks for the comments.

Glad to say that todays 10.52 upgrade has cured the minor/trivial problem!

Tony

This is an unacceptable bug, back to 10.50 for me.

Originally posted by chris4400:

This is an unacceptable bug, back to 10.50 for me.

Why?

Originally posted by TonyBeckett:

Glad to say that todays 10.52 upgrade has cured the minor/trivial problem!

Originally posted by chris4400:

This is an unacceptable bug, back to 10.50 for me.

I thought it was also present in 10.50? Regardless, 10.52 and 10.53 solve the issue, like TonyBeckett and Pesala said.