Closed
Bug 709742
Opened 14 years ago
Closed 13 years ago
Can't upload a media file in touch.facebook.com
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(blocking-kilimanjaro:+)
RESOLVED
FIXED
| blocking-kilimanjaro | + |
People
(Reporter: khris, Unassigned)
References
Details
(Keywords: top50, Whiteboard: [MTD])
Attachments
(1 file)
|
59.99 KB,
image/png
|
Details |
I think it is a fault of touch.facebook.com. Because when I change my user-agent with "Request desktop site", `Photo` button is enabled(in mobile site). And I can upload media files and it works.
It's not a bug in Fennec but I think it should be reported.
Updated•14 years ago
|
Whiteboard: [MTD]
Comment 1•14 years ago
|
||
Not sure, I'm pretty sure we support the technologies and API's they are using (i.e., local storage). Is there something Facebook is using on that page that Gecko does not yet support?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Component: General → Evangelism
QA Contact: general → evangelism
Comment 2•14 years ago
|
||
Updated•14 years ago
|
blocking-kilimanjaro: --- → ?
Comment 4•14 years ago
|
||
Facebook is the #2 site on alexa. Also happens a top app. This relates to mobile web compatibility story for k9o, so nominating for kilimanjaro.
Updated•14 years ago
|
blocking-kilimanjaro: ? → +
Comment 5•14 years ago
|
||
I sent a complaint to them via https://www.facebook.com/help/contact/?id=238478049542306. Not sure if some web form is the best way for this. Don't we have some Facebook contact in bugzilla which we can CC to such bugs?
Comment 6•14 years ago
|
||
This issue is still occurring on the latest nightly.
Updated•13 years ago
|
Component: Evangelism → Mobile
Product: Firefox for Android → Tech Evangelism
Comment 7•13 years ago
|
||
Is there anything we can change on the Mozilla end to support this? Thanks.
Comment 8•13 years ago
|
||
We may be able to get around this by spoofing the UA we send to Facebook to be the Android UA. We'll have to test well as this may introduce other issues.
Comment 9•13 years ago
|
||
Filed a bug internally at FB.
Comment 13•13 years ago
|
||
Has Facebook acknowledged the issue?
Comment 15•13 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #13)
> Has Facebook acknowledged the issue?
Yes. Harald is working with Facebook on a shortlist of outstanding issues that includes this one.
Comment 16•13 years ago
|
||
How about this issue?
Comment 18•13 years ago
|
||
I'm seeing different behavior here on FxAndroid today - haven't had the chance to fully test yet. qawanted for retest.
Keywords: qawanted
Comment 19•13 years ago
|
||
Note - FF OS vs. FxAndroid from what I quickly saw now get entirely different content served to each other.
Comment 20•13 years ago
|
||
Aaron has confirmed with a simple test pass that this is now working on FxAndroid. I'll file a separate bug though for FF OS, given that we'll still have to do outreach there separately.
Comment 21•13 years ago
|
||
Filed bug 867357 for the FF OS specific issue.
| Assignee | ||
Updated•7 years ago
|
Product: Tech Evangelism → Web Compatibility
| Assignee | ||
Updated•2 years ago
|
Component: Mobile → Site Reports
You need to log in
before you can comment on or make changes to this bug.
Description
•