it injects a script that fails to talk to a back end
Reported by
cmarkta...@gmail.com,
Sep 1 2016
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. posting in google plus 2. 3. What is the expected behavior? I am talking to someone to a support that was not the back end of the one whom I am contacting. What went wrong? I am failing to speak to a back end WebStore page: http://support.kaspersky.com/interactive/google Did this work before? Yes I am not so sure Chrome version: 52.0.2743.116 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0
,
Oct 14 2016
Hi! Unfortunately, there's no discernable bug here. Can you explain, step-by-step, what you are trying to do, and what happened? Often, attaching screenshots can be helpful.
,
Oct 21 2016
This is a diserialization bug. Reproduction Step Checking here http://mxtoolbox.com/domain/support.kaspersky.com/
,
Oct 28 2016
Thank you for providing more feedback. Adding requester "elawrence@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 28 2016
Problems with servers listed in the MXToolbox analyzer do not represent bugs in Chrome.
,
Oct 28 2016
,
Oct 28 2016
,
Oct 28 2016
it is a kaspersky bug |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by cmarkta...@gmail.com
, Sep 7 2016