Last modified: 2014-09-22 22:31:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72063, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70063 - Initial focus blocks page up/down
Initial focus blocks page up/down
Status: NEW
Product: Wikimedia
Classification: Unclassified
Blog (Other open bugs)
wmf-deployment
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-26 20:33 UTC by Nemo
Modified: 2014-09-22 22:31 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nemo 2014-08-26 20:33:04 UTC
1) Load any URL to the blog, e.g. https://blog.wikimedia.org/
2) Press page down

I. Observed: nothing happens.
II. Expected: the page scrolls down.

3) Click some block of text (but not one covered by JavaScript slideshows), or on the white side.
4) Press page down

III. Observed: works.

Verified in Firefox and Chromium.
Comment 1 Tilman Bayer 2014-09-11 04:52:47 UTC
Thanks, looking into it. (For our internal reference: Filed as https://wordpressvip.zendesk.com/requests/33251 )
Comment 2 Tilman Bayer 2014-09-22 22:31:50 UTC
FYI, according to our support at Automattic, the problem appear to be caused by the CSS/layout of our theme, specifically the block from style.css (http://ur1.ca/i85b2 ) reproduced below. According to the, when one removes that block, scrolling works as expected, although of course the layout is broken. It's not yet clear how to fix it though, so this will need to be worked on later, unless someone can provide a solution here (Moiz, any immediate insights?).

--

/* block */
.shell { width:942px; margin:0 auto; position:relative; }

/* absolute wrapper required for panel behaviour on mobile devices */
.page-wrapper { position:absolute; left:0; top:0; width:100%; height:100%; overflow-x:hidden; overflow-y:scroll; z-index: 2; background-color:#fff; -webkit-overflow-scrolling: touch; }

.page-sidebar { position:absolute; left:-250px; top:0; height:100%; width:250px; overflow-x:hidden; overflow-y:auto; -webkit-overflow-scrolling: touch; z-index: 1;}

.page-header { position:relative; z-index: 5; }
.page-main { padding:22px 0 30px; width:100%; position:relative; z-index: 1; }
.page-footer { background:#3a3a3a url(images/page-footer.png) repeat-x; padding:75px 0 50px; color:#666; font-size:14px; line-height:22px; width:100%;  }

.content { float:left; width:570px; }
.sidebar { float:right; width:340px; }

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links