'%o' appearing in the info console message
Reported by
kenorb@gmail.com,
Oct 8 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3235.0 Safari/537.36 Steps to reproduce the problem: I can see the following log entry: [58713:1547:1006/224312.603018:INFO:CONSOLE(0)] "[DOM] Input elements should have autocomplete attributes (suggested: "current-password"): %o", source: https://accounts.google.com/ServiceLogin?service=cl&passive=1209600&osid=1&continue=https://calendar.google.com/calendar/render?pli%3D1&followup=https://calendar.google.com/calendar&scc=1#main_7 (0) I'm not sure if the message it-self is the problem, however I've noticed the %o which I believe it's a placeholder for the variable. What is the expected behavior? What went wrong? I believe %o should not appear in the above message, but it should be populated by some variable. If that's not the case, please close it. Did this work before? N/A Chrome version: e7f0416cefe3af6fee4921a25611b0af4cedf868 Channel: canary OS Version: OS X 10.12.0 Flash Version: File: https://cs.chromium.org/chromium/src/components/autofill/content/renderer/page_passwords_analyser.cc?rcl=6abc19e88235609c7b8fc9df464beed2b667a773&l=464
,
Oct 9 2017
@Reporter: Could you please provide sample URL on which you are seeing the mentione log entry. This would help in triaging further from chrome TE end.
,
Oct 11 2017
I believe the URL is included in the log entry (see source), I didn't notice this on some other regular pages, it's probably related to specific input element attributes setup. Currently I'm on canary build, before I had the custom debug build to analyse some crashes, so at the moment I'm not monitoring the log entries. I just thought it's just something obvious by looking at the code, as %o basically means the placeholder for an octal number which shouldn't be displayed.
,
Oct 11 2017
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 12 2017
As there is no consistent repro steps available to check this issue from Chrome-TE end, hence adding appropriate component for further triage. Could some one look in to this issue
,
Oct 12 2017
Reporter, can you bisect the bug yourself using the script from https://www.chromium.org/developers/bisect-builds-py ?
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Oct 9 2017