4 ms·
something that got "broken" for me in recent version of firefox (I think starting with 32) is that doing a console.log of a very long string does not display th
by allan_s 12y ago
something that got "broken" for me in recent version of firefox (I think starting with 32) is that doing a console.log of a very long string does not display the whole string anymore
i.e it will print
"a looooooong string [..]" (with the [..])
same if i try to observe the variable in the debugger. And I cant find a way to get the full string in anyway, I understand for a lot things you dont want to print accidentally a 200k characters longs string as it will use a lot of memory for maybe nothing, but in my current use case (getting long xml documents to copy paste them in a beautifier / send to colleague as attachments for bug report etc.) it breaks my workflow (I'm posting here because google does not seems very talkative about this issue)
- kbrosnan 12y agoThis is https://bugzilla.mozilla.org/show_bug.cgi?id=1027997 https://bugzilla.mozilla.org/show_bug.cgi?id=1027997 'workaround…is to click the value to edit it and then copy and paste somewhere else'
- serve_yay 12y ago:/
- Excavator 12y agoI think allan_s is talking about the value as displayed in the console proper, which can be expanded by clicking the "[…]" part: http://i.imgur.com/qgBXdGZ.png http://i.imgur.com/qgBXdGZ.png Tested by doing console.log(('test').repeat(100000))
- allan_s 12y agothank you, actually I didn't thought about clicking on it, maybe making [...] appears in an other color ? also the "edit and click value" on debugger was not working for me (also "cutting" the value to a certain limit)