Closed Bug 1301861 Opened 8 years ago Closed 8 years ago

No pictures on twitter

Categories

(Web Compatibility :: Site Reports, defect, P1)

Firefox 51
Unspecified
Android
defect

Tracking

(firefox50 unaffected, firefox51 fixed)

RESOLVED DUPLICATE of bug 1301106
Tracking Status
firefox50 --- unaffected
firefox51 --- fixed

People

(Reporter: jan.manthay, Unassigned)

References

()

Details

(Keywords: regression)

For a while now Firefox Nightly 51 does not show pictures inside tweets. Example URL: https://mobile.twitter.com/mozilla The place where the pictures normaly are shown is free, like a placeholder. All of my three devices are affected: Amazon Kindle http://valid.x86.fr/a/wfewkq Asus Memopad HD 7 http://valid.x86.fr/a/995w1i Moto G 1st Gen. http://valid.x86.fr/a/q8elp7
I can reproduce on my Nexus 4. I'll try to get a regression range.
Priority: -- → P1
[Tracking Requested - why for this release]: Images not showing up on twitter
mozregression pointed to this: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=906c1f635c43ca24c685c7d1343d58eb0e4b0baf&tochange=bb8f2e88d99176437cdee6f4d50e6c5cd6a91f60 Regression from bug 1294660. Astley, can you investigate? This is easy to reproduce (for me, at least) - just load the given URL and scroll down, you'll see blank spaces where there are images. Long-pressing on the spaces will show a context menu that indicates that there are in fact images there that are not displaying.
Blocks: 1294660
Flags: needinfo?(aschen)
Hi kats, thanks for ni this bug and your effort on finding regression window. It's been clarified and resolved by Twitter per bug 1301106 comment 8. Set as dup now.
Status: NEW → RESOLVED
Closed: 8 years ago
Component: Graphics, Panning and Zooming → Mobile
Flags: needinfo?(aschen)
Product: Firefox for Android → Tech Evangelism
Resolution: --- → DUPLICATE
Version: 51 Branch → Firefox 51
Mark 51 as fixed as this is fixed in bug 1301106.
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.