Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

I'm having a problem with scrolling, pages render as lines after scrolling down.

  • 5 svar
  • 22 har dette problem
  • 2 visninger
  • Seneste svar af Oxylatium

more options

Since updating to Firefox 49.0.1 on Vista (I know, switching to 10 this month!) longer web pages will render incorrectly. After scrolling down 3 to 5 page heights in distance the page renders as a smear of vertical lines. If it's halfway through a picture, the picture is smeared so a single row of pixels turns into vertical lines taking up the page (see my attachment). Scrolling down further will eventually get past it, but an area of the page is missing. Also, switching tabs does seem to clear the bug. I tried a Refresh of Firefox and it cleared it at first, then the problem returned when I turned the menu bar and bookmarks toolbar to visible again. This happens a lot with longer pages such as Twitter and Instagram feeds and forums. Switching tabs gets around it but it's annoying! Thanks, Billy

Since updating to Firefox 49.0.1 on Vista (I know, switching to 10 this month!) longer web pages will render incorrectly. After scrolling down 3 to 5 page heights in distance the page renders as a smear of vertical lines. If it's halfway through a picture, the picture is smeared so a single row of pixels turns into vertical lines taking up the page (see my attachment). Scrolling down further will eventually get past it, but an area of the page is missing. Also, switching tabs does seem to clear the bug. I tried a Refresh of Firefox and it cleared it at first, then the problem returned when I turned the menu bar and bookmarks toolbar to visible again. This happens a lot with longer pages such as Twitter and Instagram feeds and forums. Switching tabs gets around it but it's annoying! Thanks, Billy

Valgt løsning

It's probably bug https://bugzilla.mozilla.org/show_bug.cgi?id=1304360

Could you type about:support in the location bar and paste the section "graphics".

As workaround, you can set layers.allow-d3d9-fallback preference (in about:config) to false and restart Firefox.

Læs dette svar i sammenhæng 👍 0

Alle svar (5)

more options

Image failed to upload, I'll try again.

more options

Valgt løsning

It's probably bug https://bugzilla.mozilla.org/show_bug.cgi?id=1304360

Could you type about:support in the location bar and paste the section "graphics".

As workaround, you can set layers.allow-d3d9-fallback preference (in about:config) to false and restart Firefox.

more options

Thanks Oxylatium. Sure, here is Graphics:

Graphics Features Compositing Direct3D 9 Asynchronous Pan/Zoom wheel input enabled WebGL Renderer Google Inc. -- ANGLE (Intel(R) G45/G43 Express Chipset Direct3D9Ex vs_3_0 ps_3_0) Hardware H264 Decoding No; Hardware video decoding disabled or blacklisted Direct2D Blocked for your graphics driver version. DirectWrite false (7.0.6002.23845) GPU #1 Active Yes Description Intel(R) G45/G43 Express Chipset Vendor ID 0x8086 Device ID 0x2e22 Driver Version 8.15.10.2202 Driver Date 8-25-2010 Drivers igdumdx32 igd10umd32 Subsys ID 02851028 RAM Unknown Diagnostics AzureCanvasAccelerated 0 AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo failures [GFX1]: D3D11 device creation failed: 0x887a0004 Decision Log D3D11_COMPOSITING failed by runtime: Failed to acquire a D3D11 device DIRECT2D Blocklisted; failure code BLOCKLIST_FEATURE_FAILURE_DL_BLACKLIST_g984 D3D11_HW_ANGLE disabled by env: D3D11 compositing is disabled Failure Log (#0) Assert D3D11 device creation failed: 0x887a0004

more options

So far the workaround you've suggested seems to work. Marking as solved. Thanks Oxylatium.

more options

This bug should be fixed in FF50+.