choppy moving when using custom theme

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
8 years ago
5 years ago

People

(Reporter: LogosZer0, Unassigned)

Tracking

6 Branch
All
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a2) Gecko/20110702 Firefox/6.0a2
Build ID: 20110702042005

Steps to reproduce:

It's been like that since Aurora 6 got released. I didn't report it because I switched back to 5.0 (stable) but today I just redownloaded Aurora latest build and nothing has changed. As soon as I use a custome theme (not a persona skin, but a full theme), moving FF window gets a bit choppy. The "effect" is not huge, but very obvious if you compare with FF5 where the issue doesn't exist. 

 The issue occurs whether I use themes like Nasa Night Launch or Blackfox (or any of the series), and stops as soon as I go back to Aurora default theme (or to a persona skin, not surprising as persona skins are pretty light in general).

 Could have been my hardware, but again, I don't have this problem in FF5. Thanks.
(Reporter)

Comment 1

8 years ago
just adding that hardware acceleration is constantly disabled here.

Comment 2

8 years ago
Please post the graphics section from about:support
(Reporter)

Comment 3

8 years ago
here:

Graphics
      
Adapter DescriptionMobile Intel(R) 4 Series Express Chipset 
FamilyVendor ID8086Device ID2a42Adapter RAMUnknownAdapter Driversigdumd64 igd10umd64 igdumdx32 igd10umd32Driver Version8.15.10.2302Driver Date2-11-2011Direct2D EnabledtrueDirectWrite Enabledtrue (6.1.7601.17563, font cache n/a)WebGL RendererGoogle Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.611)GPU Accelerated Windows1/1 Direct3D 10
(Reporter)

Comment 4

8 years ago
... also wanted to mention, I gave a shot to aurora 7a2 yesterday, the issue I described seems to be getting worse with every new build, starting with 6.0 and later. I might have to stick to 5.0 if there's no solution... and I don't like that... not my style to run outdated software. Okay could also be that my hardware becomes really outdated now... but to the extend of not being supported by Firefox, I have doubts...

Comment 5

8 years ago
Graphics (Spaced for clarity):
      
Adapter Description Mobile Intel(R) 4 Series Express Chipset Family
Vendor ID8086
Device ID2a42
Adapter RAM Unknown
Adapter Drivers igdumd64 igd10umd64 igdumdx32 igd10umd32
Driver Version 8.15.10.2302
Driver Date 2-11-2011
Direct2D Enabled true
DirectWrite Enabled true (6.1.7601.17563, font cache n/a)
WebGL Renderer Google Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.611)
GPU Accelerated Windows 1/1 Direct3D 10

Is this the add-on you are referring to? https://addons.mozilla.org/en-US/firefox/addon/nasa-night-launch/

Does the issue occur if you do the following:

Create a new profile
Install only the nasa-night-launch add-on
Disable hardware acceleration
Test scrolling
(Reporter)

Comment 6

8 years ago
hi,

I tested that already, just the skin (and yes that's the add-on I meant) and got the same result (new profile, no extension except that theme). Again like I said I gave this theme just as an example as that's the one I mainly use, but I have the same problem with any other "full theme" on FF6/7 (full theme as opposed to default theme or persona skin).

 Oh yeah, the issue is not with scrolling, but with moving FF window, just moving it. 

ps: concerning hardware acceleration, it's always disabled here since FF4 already, as I got a window resizing issue this time when HWA is on... so I just gave up HWA long ago; HWA being constantly off, it's not bound to the theme issue I describe here.
(based on other bug reports, pretty sure logos is gone but will ask anyway)
Does this still reproduce for you when using a current version?
Flags: needinfo?(LogosZer0)
Whiteboard: [closeme 2014-06-11]

Comment 8

5 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(LogosZer0)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-06-11]
You need to log in before you can comment on or make changes to this bug.