On www.directv.com, you are unable to scroll on Fennec. In addition, if you turn the phone to landscape and back to portrait, the image is cutoff. I've marked this as a blocker because it is a major OEM issue. If we have fixes for the website, we might be able to get them done, but in product is better.
Component: General → General
Product: Testing → Firefox for Android
Target Milestone: --- → Firefox 51
Version: Version 3 → 51 Branch
This is almost certainly a website issue. Mike leads the webcompat team.
Kats is our scrolling expert.
Thanks, taking a look. They're using Sencha touch, so things could get interesting.
I thought we were in better shape with sencha touch? https://bugzilla.mozilla.org/show_bug.cgi?id=895485 Does it depend on how old their version is?
Yeah, unclear at the moment. Still digging around.
Ext.versions reports: Ext v 4.1.0 Touch v 2.1.0 And it looks like Sencha Touch v2.2 was the base version to support "not just webkit": https://www.sencha.com/forum/showthread.php?260471-sencha-2-1-is-not-working-on-firefox-browser&p=954537&viewfull=1#post954537 (announcement link from thread seems dead tho) There are some resources out there for "fixing" Sencha Touch apps that relied on the overflowpaint event that Blink removed, I don't know if they will be helpful: https://www.joshmorony.com/the-chrome-43-update-broke-sencha-touch-apps-heres-how-to-fix-it/ Similar patch here: http://trevorbrindle.com/chrome-43-broke-sencha/#comment-6054, with more discussions about orientation paint bugs. My first guess would be that Sencha Touch relies on this (non-standard) overflowchanged event to control scrolling: https://cloudup.com/c_w0Bjw33nH, and somewhere in v2.2 they got rid of this, or provided alternate codepaths. v2.1 is a mess... unfortunately upgrading their version of Sencha Touch is probably required. They *might* be able to attempt some of the patches mentioned in the previous blog posts, but I have no idea if the APIs were stable across releases. Not a great situation. Sencha Touch (especially old versions) is basically a pile of non-standard "designed with iPhone in mind" hacks.
(/overflowpaint event/overflowchanged event/ in my previous comment)
...spoofing as Android fixes both issues as reported. I'm gonna spin off a bug to ship a UA override and then we can proceed with outreach. Let's move this to Tech Evangelism as well.
Component: General → Mobile
Product: Firefox for Android → Tech Evangelism
Target Milestone: Firefox 51 → ---
Version: 51 Branch → Firefox 51
Some movement on acquiring contacts at DirecTV. The Mikes have been added to the conversation...
platform-rel: --- → +
Mike, this was fixed by a UA override -- still want to keep it open?
Do we typically keep bugs open when evangelizing? Although in this case, they won't even see the problem to fix... I'll leave it to you. I'm fine with closing.
> Do we typically keep bugs open when evangelizing? Well, until the issue has been resolved. > Although in this case, they won't even see the problem to fix... Yeah, that's the tradeoff of doing overrides. If there's reason to think Directtv will actually update their site, we should keep it open. Otherwise, there's not much point.
Marking fixed since added an override. Maybe our backchannels to directv will come through some day.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.