Closed Bug 1264218 Opened 9 years ago Closed 6 years ago

No response after tapping on some webpages

Categories

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

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: bli, Unassigned)

References

Details

(Whiteboard: [needscontact][zh-CN])

Attachments

(2 files)

Attached image webkit-1.png
Environment: ---------------------- Samsung GT-N5110 Android 4.1.2 Firefox 46.0b8 Nightly 48.0a1(2016-04-12) layout.css.prefixes.webkit - true 1. Goto the following webpage: http://h5.m.taobao.com/awp/core/detail.htm?locate=guessitem-item&spm=a215s.7406091.guessitem.guessitem-27&scm=2027.10987.28895.0&id=44382630754&pvid=b1a1b1ed-cb0e-43fa-b67e-e2b80a3d6d59#sku Pls refer to the attachment p.s. This is a webpage that allow users to choose the size/color of the product. 2. Tap on one of those icons that represent sizes/colors. ==> None of the sizes/colors are successfully chosen. Pls refer to the attachment. This issue can be reproduce not only on this page but also on many similar pages.
Somehow this issue fell through the cracks...
Blocks: 1259345
Whiteboard: [needsdiagnosis]
Eric, could you help me find the right button that isn't working according to this report?
Flags: needinfo?(etsai)
It seems like the page has possibly been redesigned... Bingqing, do you have another example of this bug we can investigate? Thanks!
Flags: needinfo?(bli)
Attached image screenshot.png
Pls try with following url: https://item.m.jd.com/product/1773994.html?sid=65c1c0d889bb6e9cb87081eeced3d566 Since the webpage is in Chinese, I indicated the places you should tapping on in the screenshot. So once you open this page, scroll down a little bit, and then pls refer to the screenshot attached.
Flags: needinfo?(bli)
Follow the instruction in https://bugzilla.mozilla.org/show_bug.cgi?id=1264218#c4 . Test Firefox mobile 51.0.2, 52.0b2, 53.0a2 (2017-02-07), 54.0a1 (2017-02-07). The test steps: 1. Open the URL in jd.com 2. Tap to show size detail (all versions above can show) 3. Tap to choose different size (no version can choose different size) 4. Scroll down in detail, tap to add number of item, select different warranty (all version above can do) 5. Switch preference layout.css.prefixes.webkit to false, close all tabs and restart app 6. Do step 1 to 4, the results are the same for me, even on Firefox desktop with responsive mode. 7. Works on Chrome mobile 55, UC browser 11.2.0.915 and Chrome 55 Desktop with responsive mode. Summary: in the 4 Firefox mobile versions mentioned above, toggle preference layout.css.prefixes.webkit doesn't make any difference. @Bingqing, do you still use Firefox 46.0b8 and Nightly 48.0a1(2016-04-12) for test today or you have latest version but different result than me?
Flags: needinfo?(etsai) → needinfo?(bli)
Whiteboard: [needsdiagnosis] → [needsdiagnosis][zh-CN]
(In reply to Eric Tsai from comment #5) > @Bingqing, do you still use Firefox 46.0b8 and Nightly 48.0a1(2016-04-12) > for test today or you have latest version but different result than me? I used the latest version, and the result is the same. I filed this bug because of being told compatibility issues could be fixed by enable preference layout.css.prefixes.webkit. So I emphasized the preference in the description. Since now we are discussing wether compatibility mode is still needed in MozillaOnline Fennec build, we can ignore the preference. Or maybe file another bug to track?
Flags: needinfo?(bli)
Hi Bingquing, The root cause of this bug is using touch/click event but it's not defined. While tap on different size: > onclick="updateColorSizeSpec()" updateColorSizeSpec is defined in https://st.360buyimg.com/item/js/5.6/ware/view.min.js?v=jd20170119173755 In updateColorSizeSpec, we found: > if (event.target) { > if (event.target.parentNode && event.target.parentNode.id) { > if (event.target.parentNode && (event.target.parentNode.id && event.target.parentNode.id == "color")) { > // skip the long long event handle process > } catch (e) { > } Chrome or IE allow access global event variable but not in Firefox. But they catch the exception so we see nothing in console. This is not a style compatibility issue about webkit prefix preference. https://bugzilla.mozilla.org/show_bug.cgi?id=218415 would be helpful to solve this bug. But yes, tap without responding is a compatibility issue using Firefox for us. So I would like to remove the webkit strings in bug title to prevent misleading. BTW, the first URL about on taobao works for me using Firefox now.
Depends on: 218415
Summary: No response after tapping on some webpages while layout.css.prefixes.webkit is true → No response after tapping on some webpages
Component: CSS Parsing and Computation → Mobile
Product: Core → Tech Evangelism
Target Milestone: --- → Future
Version: 46 Branch → unspecified
(In reply to Eric Tsai from comment #7) > Hi Bingquing, > > The root cause of this bug is using touch/click event but it's not defined. > > While tap on different size: > > onclick="updateColorSizeSpec()" > > updateColorSizeSpec is defined in > https://st.360buyimg.com/item/js/5.6/ware/view.min.js?v=jd20170119173755 > > In updateColorSizeSpec, we found: > > if (event.target) { > > if (event.target.parentNode && event.target.parentNode.id) { > > if (event.target.parentNode && (event.target.parentNode.id && event.target.parentNode.id == "color")) { > > // skip the long long event handle process > > } catch (e) { > > } > > Chrome or IE allow access global event variable but not in Firefox. But they > catch the exception so we see nothing in console. This is not a style > compatibility issue about webkit prefix preference. > > https://bugzilla.mozilla.org/show_bug.cgi?id=218415 would be helpful to > solve this bug. > Thanks for your help, Eric, I saw Mike Taylor took that bug, I'll keep tracking. > > BTW, the first URL about on taobao works for me using Firefox now. Yes, taobao had redesigned some webpages. But we still have some compatibility issues with taobao. I saw that :miketaylr added you to the cc list of the email, in which I briefly described compatibility issues I met. So pls refer to the email. We'll keep tracking and trying to contact with taobao and other websites to solve those issues. And bugs will be filed if needed.
(In reply to Bingqing Li from comment #8) > We'll keep tracking and trying to contact with taobao and other websites to > solve those issues. And bugs will be filed if needed. Yes, please file bugs and cc :miketaylr and :etsai. :)
Gonna set to needscontact, but ultimately we need to implement the global event object in Gecko.
Whiteboard: [needsdiagnosis][zh-CN] → [needscontact][zh-CN]
Priority: -- → P1
Seems like this URL has expired.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
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.

Attachment

General

Creator:
Created:
Updated:
Size: