Chrome is masking console.log object
Before this Chrome used to directly reveal the value of key as image above.
But not sure if i accidentally made any changes, it now kind of masked the value with (...) which requires me to perform an extra action to click on the value to reveal it.
How can I get back to previous behavior
javascript
google-chrome asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
add a comment |
Before this Chrome used to directly reveal the value of key as image above.
But not sure if i accidentally made any changes, it now kind of masked the value with (...) which requires me to perform an extra action to click on the value to reveal it.
How can I get back to previous behavior
javascript
google-chrome asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
Is it really for all objects you log? if I recall correctly(...)is displayed if a getter is defined for that property, because requesting the value might result in an action.
– t.niese
Nov 13 '18 at 15:19
You are definitely right. It was my bad, if you could kindly put this as answer i will accept it :)
– Edward Chew
Nov 13 '18 at 15:22
You figured it out at the same time I wrote the comment. So answering the question yourself and accepting that one is perfectly fine. The only thing I would add is that this is done by chrome to avoid side effects on the state you want to debug, because a getter could modify existing objects and properties.
– t.niese
Nov 13 '18 at 15:28
add a comment |
Before this Chrome used to directly reveal the value of key as image above.
But not sure if i accidentally made any changes, it now kind of masked the value with (...) which requires me to perform an extra action to click on the value to reveal it.
How can I get back to previous behavior
javascript
google-chrome asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
Before this Chrome used to directly reveal the value of key as image above.
But not sure if i accidentally made any changes, it now kind of masked the value with (...) which requires me to perform an extra action to click on the value to reveal it.
How can I get back to previous behavior
javascript
google-chrome javascript
google-chrome asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
asked Nov 13 '18 at 15:12
Edward ChewEdward Chew
498
498
Is it really for all objects you log? if I recall correctly(...)is displayed if a getter is defined for that property, because requesting the value might result in an action.
– t.niese
Nov 13 '18 at 15:19
You are definitely right. It was my bad, if you could kindly put this as answer i will accept it :)
– Edward Chew
Nov 13 '18 at 15:22
You figured it out at the same time I wrote the comment. So answering the question yourself and accepting that one is perfectly fine. The only thing I would add is that this is done by chrome to avoid side effects on the state you want to debug, because a getter could modify existing objects and properties.
– t.niese
Nov 13 '18 at 15:28
add a comment |
Is it really for all objects you log? if I recall correctly(...)is displayed if a getter is defined for that property, because requesting the value might result in an action.
– t.niese
Nov 13 '18 at 15:19
You are definitely right. It was my bad, if you could kindly put this as answer i will accept it :)
– Edward Chew
Nov 13 '18 at 15:22
You figured it out at the same time I wrote the comment. So answering the question yourself and accepting that one is perfectly fine. The only thing I would add is that this is done by chrome to avoid side effects on the state you want to debug, because a getter could modify existing objects and properties.
– t.niese
Nov 13 '18 at 15:28
Is it really for all objects you log? if I recall correctly
(...) is displayed if a getter is defined for that property, because requesting the value might result in an action.– t.niese
Nov 13 '18 at 15:19
Is it really for all objects you log? if I recall correctly
(...) is displayed if a getter is defined for that property, because requesting the value might result in an action.– t.niese
Nov 13 '18 at 15:19
You are definitely right. It was my bad, if you could kindly put this as answer i will accept it :)
– Edward Chew
Nov 13 '18 at 15:22
You are definitely right. It was my bad, if you could kindly put this as answer i will accept it :)
– Edward Chew
Nov 13 '18 at 15:22
You figured it out at the same time I wrote the comment. So answering the question yourself and accepting that one is perfectly fine. The only thing I would add is that this is done by chrome to avoid side effects on the state you want to debug, because a getter could modify existing objects and properties.
– t.niese
Nov 13 '18 at 15:28
You figured it out at the same time I wrote the comment. So answering the question yourself and accepting that one is perfectly fine. The only thing I would add is that this is done by chrome to avoid side effects on the state you want to debug, because a getter could modify existing objects and properties.
– t.niese
Nov 13 '18 at 15:28
add a comment |
2 Answers
2
active
oldest
votes
Sorry I have just realized that it has nothing to do with Chrome.
The issue was I am using vue which use property getter, so chrome needs me to manually click on the (...) to invoke the getter function.
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
add a comment |
Go to DevTools settings (the cog wheel).
Check General > Sources > Display variable values inline while debugging.
Try with that or you can go with JSON.stringify
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
1
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284020%2fchrome-is-masking-console-log-object%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sorry I have just realized that it has nothing to do with Chrome.
The issue was I am using vue which use property getter, so chrome needs me to manually click on the (...) to invoke the getter function.
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
add a comment |
Sorry I have just realized that it has nothing to do with Chrome.
The issue was I am using vue which use property getter, so chrome needs me to manually click on the (...) to invoke the getter function.
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
add a comment |
Sorry I have just realized that it has nothing to do with Chrome.
The issue was I am using vue which use property getter, so chrome needs me to manually click on the (...) to invoke the getter function.
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
Sorry I have just realized that it has nothing to do with Chrome.
The issue was I am using vue which use property getter, so chrome needs me to manually click on the (...) to invoke the getter function.
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
answered Nov 13 '18 at 15:20
Edward ChewEdward Chew
498
498
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
add a comment |
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
Try Vue DevTools ;-)
– thibautg
Nov 13 '18 at 15:56
add a comment |
Go to DevTools settings (the cog wheel).
Check General > Sources > Display variable values inline while debugging.
Try with that or you can go with JSON.stringify
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
1
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
add a comment |
Go to DevTools settings (the cog wheel).
Check General > Sources > Display variable values inline while debugging.
Try with that or you can go with JSON.stringify
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
1
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
add a comment |
Go to DevTools settings (the cog wheel).
Check General > Sources > Display variable values inline while debugging.
Try with that or you can go with JSON.stringify
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
Go to DevTools settings (the cog wheel).
Check General > Sources > Display variable values inline while debugging.
Try with that or you can go with JSON.stringify
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
answered Nov 13 '18 at 15:14
Slobodan GajićSlobodan Gajić
104110
104110
1
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
add a comment |
1
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
1
1
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
I already have it checked but the issue preserved, thanks anyway :)
– Edward Chew
Nov 13 '18 at 15:18
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284020%2fchrome-is-masking-console-log-object%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is it really for all objects you log? if I recall correctly
(...)is displayed if a getter is defined for that property, because requesting the value might result in an action.– t.niese
Nov 13 '18 at 15:19
You are definitely right. It was my bad, if you could kindly put this as answer i will accept it :)
– Edward Chew
Nov 13 '18 at 15:22
You figured it out at the same time I wrote the comment. So answering the question yourself and accepting that one is perfectly fine. The only thing I would add is that this is done by chrome to avoid side effects on the state you want to debug, because a getter could modify existing objects and properties.
– t.niese
Nov 13 '18 at 15:28