New issue
Advanced search Search tips

Issue 632971 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Google Adsense URL not showing in Mail

Reported by aftabmun...@gmail.com, Jul 30 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Send Mail from another account to your gmail account which includes Google Adsense Code.
2. Check your mail, it will display unread(new) mail in list with adsense code(Screenshot1.jpg)
3. But when you open that mail, you will see that the code with "<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>" 
will converted to 
"<script async src="//"></script>" (Screenshot2.jpg)

What is the expected behavior?

What went wrong?
One of my friend send me the Google Adsense code in Gmail.I received new mail in list with adsense code(Screenshot1.jpg) 
but when I open that mail, the code with "<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>" 
is converted to 
"<script async src="//"></script>" (Screenshot2.jpg)

I dont know why is this so. You can check my attached scrrenshot.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? No firefox

Chrome version: 51.0.2704.106  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0
 
screenshot1.JPG
116 KB View Download
screenshot2.JPG
80.5 KB View Download

Comment 1 by kojii@chromium.org, Aug 1 2016

Labels: Needs-Feedback
Thank you for reporting the issue. It looks like this issue belongs to gmail rather than Chromium, could you please ask at:
https://productforums.google.com/forum/#!forum/gmail
?

Comment 2 by kojii@chromium.org, Aug 1 2016

Cc: kojii@chromium.org

Comment 3 by tkent@chromium.org, Aug 22 2016

Status: WontFix (was: Unconfirmed)
Closing because this doesn't look a Chrome's bug.

Sign in to add a comment