Issue 251857 in chromium: Site incompat: Jcrew active elements do not work on CROS but work on browser

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
CC: jasonlk...@chromium.org, angel...@chromium.org, m...@chromium.org,
joshwood...@chromium.org
Labels: Type-Bug Pri-2 Cr-Blink-Rendering OS-Chrome Hotlist-ConOps

New issue 251857 by melissad...@chromium.org: Site incompat: Jcrew active
elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857


Google Chrome 28.0.1500.47 (Official Build 206229) beta
Platform 4100.44.0 (Official Build) beta-channel link

What steps will reproduce the problem?
1. Go to jcrew.com on a Chromebook
2. Click on an item of clothing (ex:
http://www.jcrew.com/womens_feature/NewArrivals/shirtstops/PRDOVR~84643/84643.jsp#)
3. Attempt to select the item in a different color (the pink is cute,
right?) and select a size (small, maybe?)
4. Note that neither of these options actually register on the site-- the
hover image changes, but the box/indicator validating your size and color
selection never actually changes (remains on navy and no size is selected)
5. Attempt to reproduce this on Chrome browser on another device (ex: Mac)
-- you are able to successfully select the top in a color and size and add
to cart

Site made a slight design change last night, but regardless of this UI
change, the end user should be able to proceed and purchase on Chrome
browser and on a Chromebook. Are we handling this improperly? Site incompat
issue? Rendering?

https://feedback.corp.google.com/#/Report/956658504?context=ri

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #2 on issue 251857 by wiltz...@chromium.org: Site incompat: Jcrew

active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

Weird. I can repro, and it works fine on a Retina macbook (so not hi DPI
related). No obvious errors in the console. I don't know what's up -- we
aren't shipping a different rendering architures on CrOS than recent Mac
builds at this point. Overriding the useragent to be Firefox didn't change
anything either, so I don't think they're UA sniffing (although who knows).

The next step would be to try to debug their live site on a Pixel and
figure out what that border isn't showing up as a generic web development
debugging exercise, but I don't think there's anything particularly in my
area -- anyone familiar with web development should be able to do this.

[chro...@googlecode.com]

Comment #3 on issue 251857 by joshwood...@chromium.org: Site incompat:

Jcrew active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

Are there any Blink-related people that typically look into bugs like this?
(Sorry, I generally don't handle bugs like this one.)

[chro...@googlecode.com]

Comment #4 on issue 251857 by wiltz...@chromium.org: Site incompat: Jcrew

active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

Not really, but it's in the (giant) Blink-Rendering bucket which is
probably the right spot. Typically bugs like this need to be trimmed down
to reduced test cases.

[chro...@googlecode.com]

Updates:
Cc: komoro...@chromium.org
Labels: -Cr-Blink-Rendering Cr-Blink

Comment #5 on issue 251857 by joshwood...@chromium.org: Site incompat:

Jcrew active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

Gotcha. Seems like you've helped narrow it down a bit. Any ideas on how we
can narrow further? Adding @komoroske, in case he has ideas.

[chro...@googlecode.com]

Comment #6 on issue 251857 by komoro...@chromium.org: Site incompat: Jcrew

active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

I just poked around on my Pixel and verified the problem but can't figure
out what's going wrong. They've got a large amount of script that
presumably (among other things) handles the click and some internal state.

I don't have another machine to test on.

Did this used to work on Pixel? ... Not that that would help us out much,
given that bisect-builds doesn't work for ChromeOS

It's very odd to me that it doesn't repro in Chrome on other OS's.

[chro...@googlecode.com]

Comment #7 on issue 251857 by melissad...@chromium.org: Site incompat:

Jcrew active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

The site previously worked on a Pixel (trust me, I'm a frequent shopper,
which is how I stumbled across it :) ) and then they made a slight UI
change and bam. No shopping for me.

But I filed because it seems odd that it works on all other devices (even
mobile-- both clank as well as bling) and all other platforms. So there's
something funky on the CrOS side.

I contacted Jcrew as well and they said they're looking into it as well,
but no surprise, they don't have a Chromebook on site to repro with.

[chro...@googlecode.com]

Updates:
Labels: Cr-Blink-JavaScript

Comment #8 on issue 251857 by komoro...@chromium.org: Site incompat: Jcrew

active elements do not work on CROS but work on browser
http://code.google.com/p/chromium/issues/detail?id=251857

I just spent another 5 minutes trying to debug this. I did a DOM click
breakpoint, but their code JS is compiled (and complex!) and it's hard to
trace what it's _supposed_ to do.

Adding the V8 label on a random guess that something is going wrong in V8
land (given that the click appears to actually happen).