Chrome is masking console.log object












1















previous Chrome behavior which directly shows value of keys



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



enter image description here






javascript google-chrome







share|improve this question























  • 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


















1















previous Chrome behavior which directly shows value of keys



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



enter image description here






javascript google-chrome







share|improve this question























  • 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
















1












1








1








previous Chrome behavior which directly shows value of keys



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



enter image description here






javascript google-chrome







share|improve this question














previous Chrome behavior which directly shows value of keys



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



enter image description here






javascript google-chrome




javascript google-chrome






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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





















  • 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














2 Answers
2






active

oldest

votes


















3














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.






share|improve this answer
























  • Try Vue DevTools ;-)

    – thibautg
    Nov 13 '18 at 15:56



















0














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






share|improve this answer



















  • 1





    I already have it checked but the issue preserved, thanks anyway :)

    – Edward Chew
    Nov 13 '18 at 15:18











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
});


}
});














draft saved

draft discarded


















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









3














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.






share|improve this answer
























  • Try Vue DevTools ;-)

    – thibautg
    Nov 13 '18 at 15:56
















3














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.






share|improve this answer
























  • Try Vue DevTools ;-)

    – thibautg
    Nov 13 '18 at 15:56














3












3








3







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.






share|improve this answer













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.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 13 '18 at 15:20









Edward ChewEdward Chew

498




498













  • 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





Try Vue DevTools ;-)

– thibautg
Nov 13 '18 at 15:56













0














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






share|improve this answer



















  • 1





    I already have it checked but the issue preserved, thanks anyway :)

    – Edward Chew
    Nov 13 '18 at 15:18
















0














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






share|improve this answer



















  • 1





    I already have it checked but the issue preserved, thanks anyway :)

    – Edward Chew
    Nov 13 '18 at 15:18














0












0








0







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






share|improve this answer













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







share|improve this answer












share|improve this answer



share|improve this answer










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














  • 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


















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

Bressuire

Image
Subprefecture and commune in Nouvelle-Aquitaine, France Bressuire Subprefecture and commune Chateau de Bressuire and the Eglise Notre-Dame Coat of arms Location of Bressuire Bressuire Show map of France Bressuire Show map of Nouvelle-Aquitaine Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Country France Region Nouvelle-Aquitaine Department Deux-Sèvres Arrondissement Bressuire Canton Bressuire Government  • Mayor .mw-parser-output .nobold{font-weight:normal} (2014–20) Jean Michel Bernier Area 1 180.59 km 2 (69.73 sq mi) Population (2014) 2 19,300  • Density 110/km 2 (280/sq mi) Time zone UTC+01:00 (CET)  • Summer (DST) UTC+02:00 (CEST) INSEE/Postal code 79049 /79300 Elevation 98–236 m (322–774 ft) (avg. 173 m or 568 ft) 1 French Land Register data, which exclude...
Read more

Vorschmack

Image
Vorschmack Ukrainian Jewish-style vorschmack served on rye bread Course Hors d'oeuvre Region or state Eastern Europe Associated national cuisine Ashkenazi Jewish, Finnish, German, Ukrainian, Polish, Russian Main ingredients Ground meat and/or fish Cookbook: Vorschmack   Media: Vorschmack Vorschmack or forshmak (Yiddish: פֿאָרשמאַק ‎, from archaic German Vorschmack , "foretaste" [1] or "appetizer" [2] ) is an originally East European dish made of salty minced fish or meat. Different variants of this dish are especially common in Ashkenazi Jewish and Finnish cuisine. Some varieties are also known in Russian and Polish cuisine. Contents 1 In Jewish cuisine 2 In Russian cuisine 3 In Polish cuisine 4 In Finnish cuisine 5 See also 6 References In Jewish cuisine According to Gil Marks, the German name points to the possible Germanic origin of this dish. [1] William Pokhlyobkin descr...
Read more

Quarantine

Image
For other uses, see Quarantine (disambiguation). Signal flag "Lima" called the "Yellow Jack" which when flown in harbor means ship is under quarantine. A simple yellow flag (also called the "Yellow Jack") had historically been used to signal quarantine (it stands for Q among signal flags), but now indicates the opposite, as a signal of a ship free of disease that requests boarding and inspection. A quarantine is used to separate and restrict the movement of people; it is 'a restraint upon the activities or communication of persons or the transport of goods designed to prevent the spread of disease or pests', for a certain period of time. [1] This is often used in connection to disease and illness, such as those who may possibly have been exposed to a communicable disease. [2] The term is often erroneously used to mean medical isolation, which is "to separate ill persons who have a communicable disease from those who are healthy...
Read more