Closed
Bug 759729
Opened 14 years ago
Closed 12 years ago
Can't interact with overstock.com
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(blocking-fennec1.0 -)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| blocking-fennec1.0 | --- | - |
People
(Reporter: blassey, Unassigned)
References
()
Details
(Whiteboard: [country-all] [js])
STR:
1) Load overstock.com
2) Click on anything (other than "Account" or "Sign in")
ER:
Navigate to the thing you click on
AR:
item highlights, but nothing else happens
Comment 1•14 years ago
|
||
I see the following in logcat:
I/Gecko ( 8851): WARNING: Not same origin error!: file /Users/kats/zspace/mozilla-git/dom/base/nsJSEnvironment.cpp, line 346
E/GeckoConsole( 8851): [JavaScript Error: "ReferenceError: event is not defined" {file: "http://ak2.ostkcdn.com/js/jqtouch-167.min.js" line: 1}]
I'm guessing the second error is responsible; probably touch events are getting prevented and then erroring out. This will need to be investigated more.
Blocks: clicksdontwork
URL: http://overstock.com
Updated•14 years ago
|
blocking-fennec1.0: ? → -
Component: General → Evangelism
QA Contact: general → evangelism
Comment 2•14 years ago
|
||
Really quickly looking at the jquery source I see a touchstart event handler that looks like:
function D(ay) {
H();
if (event.changedTouches && event.changedTouches.length) {
au = event.changedTouches[0];
aw = au.pageX;
av = au.pageY
}
i.e. they're depending on a global event object. (Apple.com does this too!)
Updated•13 years ago
|
Component: Evangelism → Mobile
OS: Mac OS X → Android
Product: Firefox for Android → Tech Evangelism
Hardware: x86 → ARM
Comment 3•12 years ago
|
||
Tested on Firefox for Android "Android; Mobile; rv:23.0"
Everything is working. Closing as WFM.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [country-all] [js]
| 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
•