Page MenuHomePhabricator

Fundraising banner doesn't stay at top of page when user scrolls
Closed, ResolvedPublic

Description

English Wikipedia main page logged out with obstructionist donation banner, December 4, 2012

The current fundraising banner (I don't know its name) on the English Wikipedia doesn't stay at the top of the page when a user scrolls down the page. This is a problem, as the banner quickly begins to obstruct page content, which is unacceptable.

Fundraising banners should not follow a user as he or she scrolls through the page. They should remain at the top of the page as they have in every prior fundraiser and with every other banner campaign deployed. Screenshot of the inappropriate behavior attached.


Version: unspecified
Severity: major

Attached:

en-wiki-logged-out-donation-banner-following-me-2012-12-04.png (800×1 px, 305 KB)

Details

Reference
bz42671

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 12:44 AM
bzimport set Reference to bz42671.

I think it could be solved by a meta sysop.

This is a major problem that upsets /thousands/ of Wikipedia readers, even though the fundraising campaign is enabled just in 5 countries.

I guess that someone would better fix it before the campaign is enabled worldwide, or there'll be massive trouble and displeasure being actually voiced by thousands of our readers.

(In reply to comment #1)

I think it could be solved by a meta sysop.

Probably. I think it's simply a matter of changing a CSS position declaration. The problem is probably more social than technical.

(In reply to comment #3)

Browser info welcome...

I was testing with Mac OS X/Safari last evening. I'm experiencing the exact same behavior on Windows 7/Firefox today.

Are you unable to reproduce the issue? That's the only way I can see how browser info would be relevant here.

(In reply to comment #4)

Are you unable to reproduce the issue? That's the only way I can see how
browser info would be relevant here.

Browser issue is always pretty relevant when it comes to rendering issues, no matter if I had time to test this with a bunch of browsers or not...

pgehres wrote:

As renamed, this bug is resolved. It was intentional, but that "feature" has been removed.