Ad Words Payment page fails to load
Reported by
sfo...@gmail.com,
Feb 10 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.37 Safari/537.36 Example URL: N/A Steps to reproduce the problem: 1. Logged into Google Ad Words 2. Account balance was $0, clicked fix-it button which opens a new page 3. New page has this error "There was an error with your operation. If you were trying to make a change, it may not have saved. Please refresh this page to try again. If the error continues, log out of your AdWords account, then log in again and return to this page." 4. Payment button brings up a 'window' that never fully populates. 5. Attempted same thing on Firefox and it failed at first until Flash was allowed to run and then worked. What is the expected behavior? The page populates properly. What went wrong? The page didn't properly fill in everywhere. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? Yes 56 Does this work in other browsers? Yes Chrome version: 57.0.2987.37 Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0 I'm somewhat expecting this to be closed out and referred to Ad Words, but as it was specific to Chrome I thought it should be reported here first.
,
Feb 10 2017
Prudhvi, is there a way we can try to repro this? May be Abdul can help? Anthony user said "Attempted same thing on Firefox and it failed at first until Flash was allowed to run and then worked.". Adding "RBS" label for investigation.
,
Feb 10 2017
I am not sure about the ad words page, Since we don't have any testpage as far a I know. sforce@ by any chance did you see similar issue on any other webpage, if so please let is know the URL.
,
Feb 10 2017
This appears to be an Adwords issue triggered by the recent deployment of HTML5 by Default, which is rolling out in Chrome 56. The issue has been escalated internally and in the process of being reviewed/ resolved. For that reason, removing the ReleaseBlock-Stable label as this issue is not caused by anything specific to Chrome 57, and also changing the status to ExternalDependency since a fix will need to happen outside of Chrome.
,
Feb 11 2017
That is somewhat what I suspected - it being primarily an external issue - thank you for the attention to it.
,
Aug 14 2017
,
Aug 14 2017
I'm going to WontFix this issue, since there have been no additional comments and the star count remains low. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Feb 10 2017