Closed
Bug 977111
Opened 11 years ago
Closed 11 years ago
m.lowes.com - unable to enter zipcode into input
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 977259
People
(Reporter: miketaylr, Assigned: miketaylr)
References
()
Details
(Whiteboard: [mobile-compat-form][notcontactready][clientsniff])
Site: http://m.lowes.com/pd_123099-426-MWF_0__?productId=3256622
Unable to enter zipcode into input
:: Steps To Reproduce
(Make sure you're on network data--it just guesses where I'm at when I'm connected to wifi)
1. Go to http://m.lowes.com/pd_123099-426-MWF_0__?productId=3256622
2. Try to put in your zipcode in the input up top
:: Expected Result
Can enter zipcode
:: Actual Result
Can't enter zipcode
:: Additional Information
Software Version: stable
Reporter's User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → miket
Assignee | ||
Updated•11 years ago
|
Summary: Unable to enter zipcode into input → m.lowes.com - unable to enter zipcode into input
Assignee | ||
Comment 1•11 years ago
|
||
The reason this doesn't work is due to Bug 977259--keypress events never make it to the input.
For whatever reason though, only non-Chrome mobile browsers go down the codepath that we've hit a bug on.
In http://m.lowes.com/wcsstore/B2BDirectStorefrontAssetStore/mobile/web/js/mobile-min.js?[20140221]:
if (Lowes.User.device() === "android") {
$('input[pattern="[0-9]*"]').each(function() {
var m = $(this), l = m.attr("type"), k = parseInt(m.data("maxlength"));
if (!(k && k > 15 && d.indexOf("Chrome") > -1)) {
m.on("focus", function() {
this.type = "number";
}).on("blur", function() {
this.type = l;
});
}
});
}
I found another bug while trying to track this one down, with the Lowes.User.version method:
version: function() {
agent = window.navigator.userAgent;
switch (a.User.device()) {
case "ios":
return window.Number(agent.substr(agent.indexOf("OS ") + 3, 3).replace("_", "."));
case "android":
return window.Number(agent.substr(agent.indexOf("Android ") + 8, 3));
case "windows":
return window.Number(agent.substr(agent.indexOf("Windows Phone ") + 14, 3));
}
},
Our UA string has an "Android;" token, not "Android "--so indexOf will return -1. And navigator.userAgent.substr(7,3) is "/5." Casting that to a number yields NaN.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [mobile-compat-form] → [mobile-compat-form][notcontactready]
Assignee | ||
Updated•11 years ago
|
Whiteboard: [mobile-compat-form][notcontactready] → [mobile-compat-form][notcontactready][clientsniff]
Comment 2•11 years ago
|
||
Probably obvious comment: we should not recommend they change their code to work around our temporary text input bug. We might want to contact them about detecting Android version NaN, but if it doesn't cause problems it seems pretty low-pri.
I'd just close this as dup of the core bug..
Assignee | ||
Comment 3•11 years ago
|
||
Agreed, let's do that.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Tech Evangelism → Web Compatibility
Updated•1 years ago
|
Component: Mobile → Site Reports
You need to log in
before you can comment on or make changes to this bug.
Description
•