LinkedIN edit profile action buttons don't respond to mouse click on touch enabled devices. |
|||||
Issue descriptionChrome Version : 49.0263.95 (on link) and 50.0.2661.32 (samus) are both affected URL :https://www.linkedin.com/in/nhendin?trk=nav_responsive_tab_profile Behavior in Safari 4.x/5.x: (don't have mac) Behavior in Firefox 3.x/4.x: Works fine, also works on Yoshi and Chrome beta for linux (goobuntu) What steps will reproduce the problem? (1) Log into LinkedIN (2) select "Edit Profile" (3) For an item in your profile, click the "Add Document" button in the frame below the text describing that profile entry. If working properly a text entry field will appear to paste a url into. If not working, that won't appear. So far I have tested on ChromeOS 49 on link (pixel 1) and 50 (samus) and both fail, however Chrome for linux v50 (goobuntu), AND chrome 50 for Yoshi (I had an old yoshi I was using for something else) both work. Firefox on my old ubuntu desktop works fine too. FWIW, one common thing between Samus / Link and not the other tests is HiDPI. I have attached screenshots from samus showing not-working and yoshi showing working.
,
Mar 24 2016
Looks like this happens on touch enabled device. You can use touch to open, but it does not respond to mouse click, in which case could be a bug on their site. This also happened on flip, and I assume this will happen on Windows touch device as well. rbyers@, can you , or someone you know, check if this is blink side issue or just a bug on linked in site?
,
Mar 24 2016
,
Mar 24 2016
This looks like a problem with the page. They are binding a touchend handler; and generating an internal event called "focusin" which then changes the class of the div to show the selection area. They aren't binding anything else. I need to see how it works on a plain non touch device.
,
Mar 24 2016
Here is the problematic code: "ontouchstart"in document.documentElement)?"touchend":"click" They are binding to only one device type.
,
Mar 24 2016
,
Mar 24 2016
Ah, so it works on non-touch enabled devices, I had not considered that 2 devices if failed on were both touch enabled. --neil.
,
Mar 24 2016
I've filed a "ticket" with them via their support channel pointing them at this issue. Hopefully I will get someone who is knowledgeable in this aspect for them to address the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nhendin@google.com
, Mar 24 2016