Open Bug 1493530 Opened 7 years ago Updated 3 years ago

Boston globe ePaper freezes on surface pro 2017

Categories

(Core :: DOM: Events, defect, P2)

Product:
Core
Component:
DOM: Events
Version:
62 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: ricpicstudios, Unassigned)

References

(
URL
)

Details

(Keywords: webcompat:site-wait, Whiteboard: [sitewait])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 Build ID: 20180830143136 Firefox for Android Steps to reproduce: ran it Actual results: freezes...IE does not Expected results: not to freeze
I tried to enter this bug several times but I can't seem to have anyone take this seriously. I use Firefox as my browser with the exception of the Boston Globe ePaper.
"steps to reproduce" means that you describe step by step what I have to to do to reproduce the problem. Do I need an Account ?
Flags: needinfo?(ricpicstudios)
It appears you need an account. I thought there would be a sample edition but I have been unable to find one. Perhaps you can contact them. I'm sure they would cooperate given your goal. As for reproducing the issue, merely exercise the navigation (zoom, etc.) and it will break. I have no particular steps but it is easy to break when you peruse the paper. Zooming seems to be a common thread. Richard
Flags: needinfo?(ricpicstudios)
Hi Richard567 Can you give more detailed steps to reproduce? I was not able to reproduce this issue.
Component: Untriaged → General
Product: Firefox → Firefox for Android
Version: 62 Branch → Firefox 62
Hi there, To make it clear I am running on the latest(2017)Surface Pro i5/256GB in touch mode using the latest Windows 10 and Firefox. The issue has been present since ~Nov 2017. I have not found exactly the steps necessary to freeze Firefox. As I mentioned I am able to freeze it by just navigating through the ePaper pages and zooming articles. I am unable to read the paper without it freezing whereas in IE and Edge I experience no such problems. Also it freezes without extensions. I would be very interested to hear if you folks can't reproduce this issue using the above scenario. Thanks Richard
Surface Pro isn't Android.
Component: General → Untriaged
Product: Firefox for Android → Firefox
Version: Firefox 62 → 62 Branch
Hmm...never said it was. At least I never intended it would be logged in as such. If this was filed in the wrong place, would someone be so kind to transfer this issue to the appropriate place? BTW I would never use an Android OS.
Bump
Your bug report is difficult because a rare device is required (Windows touch device) and the bug is behind a paywall. You also have no clear and fast steps to reproduce. I would let you run our regression tool to find the change in Firefox that caused this if you could reproduce this very fast.
Thanks for your reply. I have to respectively disagree that this is a "rare device". Also given this hardware and use conditions, the issue is easily reproducible (see my previous comments). Please note that I had previously reported a "touch" bug on this device regarding tabs and Firefox freezing and this adequately addressed. As a retired Software Engineer I do understand about desiring reproducibility but one can easily cause Firefox to freeze/stall using this ePaper. As for being behind a paywall, as noted before I do believe the Boston Globe would provide access to an archived edition. At any rate I will drop this issue. In all honesty I was just trying to help. I will continue reading the paper using IE. Richard
Not the King's English....should have written I "respectfully" disagree.
I was not able to verify due to the specific device. We don't have in hand. Placing it Firefox: General Please feel free to change the component.
Component: Untriaged → General
Flags: needinfo?(ricpicstudios)
Product: Firefox → Core
Damira, I honestly don't have more to say. If Firefox is serious about addressing bugs that exists on a Microsoft Surface device then perhaps they can commit some resources to it. The bug manifests rather easily given the data I provided. As a retired Software Engineer I certainly understand the need for reproducibility but in this case it is rather apparent as one peruses the paper. Simply put I cannot use Firefox to read the paper without it freezing on me. BTW if it matters I am running the latest Firefox browser on an up-to-date Windows 10. I will have nothing further to say on this bug.
Flags: needinfo?(ricpicstudios)
I signed up for an account with the Boston Globe (email me if you want the credentials). Even with tracking protection off, I can't get https://epaper.bostonglobe.com/html5/reader/production/default.aspx to load in Nightly as it fails with "Error evaluating https://epaper.bostonglobe.com/html5/reader/production/app.js with message: InternalError: too much recursion".
URL: https://epaper.bostonglobe.com
(In reply to Andrew Overholt [:overholt] from comment #14) > I signed up for an account with the Boston Globe (email me if you want the > credentials). Even with tracking protection off, I can't get > https://epaper.bostonglobe.com/html5/reader/production/default.aspx to load > in Nightly as it fails with "Error evaluating > https://epaper.bostonglobe.com/html5/reader/production/app.js with message: > InternalError: too much recursion". Looks like this might be ARM64-specific (was trying it on a Lenovo Windows ARM device with a touchscreen). On a Surface Laptop, I got the epaper version loaded and was able to generally browse around with the touchscreen. At some point I got errors in the console and things stopped working: TypeError: a.scroller is undefined[Learn More] default.aspx:1:1769720 TypeError: b is undefined[Learn More] default.aspx:1:433033 TypeError: c.blur is not a function[Learn More] Maybe some sort of site-specific timing issue? Hsin-Yi, I'm going to take a stab in the dark and guess it might be (Touch?) Events-related. Alternatively, we could perhaps see if Adam or Mike know anyone at the Boston Globe.
Component: General → DOM: Events
Flags: needinfo?(miket)
Flags: needinfo?(astevenson)
Perhaps it is arm64 related -- I'm not able to reproduce on this (touch, intel 64bit) Lenovo Yoga. I don't have contacts at Boston Globe, but perhaps Adam can help us.
Flags: needinfo?(miket)
I am pleased this is being looked at. I generally got it to fail when zooming. As for it being touch related, you may try it with a USB mouse. If it doesn’t fail then the issue can be narrowed down to touch. Richard

I don't have contacts there but have started to reach out. Will update when I hear back.

Flags: needinfo?(astevenson)
Whiteboard: [sitewait]

Our contact has "forwarded the details to the tech team and they are on it."

Please note that one is able to read the ePaper on IE with no problems. This appears to be a Firefox issue.

Priority: -- → P2

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Keywords: webcompat:site-wait
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.