img ismap does not send coordinates in HTTP request under gmail
Reported by
ddeso...@monetate.com,
Jun 3 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Steps to reproduce the problem: 1. Send the following HTML content as an e-mail to a gmail account 2. Click the image in the sent mail under Chrome or Chromium 3. Observe that the url of the page does not contain click coordinates in the query string. What is the expected behavior? The request triggered as a result of clicking the link should contain click coordinates as a query param. ismap works under the simple case: 1. open the attached html directly in chrome 2. click the image 3. observe that the request contains click coordinates What went wrong? It appears that under Chrome, in certain scenarios, it does not honor ismap and send click coordinates with the appropriate request. Did this work before? N/A Chrome version: 51.0.2704.79 Channel: stable OS Version: OS X 10.11.5 Flash Version: Shockwave Flash 21.0 r0 I've observed this under Chrome, Chromium and Safari. And confirmed the layout identified the ismap attribute and enclosing anchor as expected for this to work. It works as expected under Firefox, which makes me believe either this is specific to webkit origins or some special work around in the application I'm not seeing. I apologize in advance if this ends up not being applicable to this project.
,
Jul 22 2016
Confirmed. Markup in Gmail conversation view is same in Chrome and Firefox.
,
Jul 24 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 28 2017
,
Jul 30
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by shrike@chromium.org
, Jun 3 2016Status: Untriaged (was: Unconfirmed)