920550 - New OS X style vertical scrollbar is hidden by articles in Digg Reader

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Sun]

Attachment: 屏幕快照 2013-09-25 下午10.31.31.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

1. Open Digg Reader
2. Scroll content in news list on the right.


Actual results:

The new style OS X scrollbar doesn't show on the whole right side, just a little on the top


Expected results:

The new style OS X scrollbar show on the whole right side

Comment 1

[Sun]

Attachment: 屏幕快照 2013-09-25 下午10.31.47.png

Comment 2

[Stephen A Pohl [:spohl]]

This appears to be caused by the <article> element of class " expanded api feeditem-read feed-item-focused" having a higher z-index (z-index: 2) than the scrollable element. This is similar to bug 891136 and the solution was for the website to:
1. Give the scrollable element a higher z-index than the element with the articles.
2. Make the scrollable element 'pointer-events:none'.

It is possible that Digg Reader made the z-index of the scrollable element lower than the z-index of the element with the articles to avoid the scrollable element catching pointer events meant for the articles. Step 2 works around this problem.

CC-ing roc in case I missed something. Otherwise, this looks like a tech evangelism bug to me.

Comment 3

[Sun]

In Firefox 25 beta 2, the bug 891136 is fixed, but vertical scrollbar in Digg reader still not display correctly.

Comment 4

[Stephen A Pohl [:spohl]]

(In reply to Sun from comment #3)
> In Firefox 25 beta 2, the bug 891136 is fixed, but vertical scrollbar in
> Digg reader still not display correctly.

You're correct. Bug 891136 tracked the work on our side. After that patch landed, Google Docs still had to make changes on their end to make use of the fix. Digg Reader will need to do the same. Steps for Digg Reader are outlined in comment 2.

Comment 5

[Timothy Nikkel (:tnikkel)]

Does this still happen? We changed to code recently to fix things like this.

Comment 6

[Mike Taylor [:miketaylr]]

This is fixed, just signed up and tested.