return value of console evaluation should be shown after any console logs from the code executed

VERIFIED FIXED in Firefox 46

Status

()

Firefox
Developer Tools: Console
VERIFIED FIXED
4 years ago
2 years ago

People

(Reporter: ColCh, Assigned: bgrins)

Tracking

(Blocks: 1 bug)

31 Branch
Firefox 46
Points:
---

Firefox Tracking Flags

(firefox46 verified)

Details

(Whiteboard: [console-spec])

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140716183446

Steps to reproduce:

Just try to log simple stuff:

JS code to execute in console:

var a = 10; console.log(a); a = 20; a;




Actual results:

It displays return value at first. 

Result is: 

20
10


Expected results:

should show console.log. 


Result is: 

10
20
(Reporter)

Comment 1

4 years ago
Expected result - should show logging stuff in right order (just like execution order). Result should be "10, 20"
Component: Untriaged → Developer Tools: Console
OS: Windows 8.1 → All
Hardware: x86_64 → All
Summary: Wrong log order → return value of console evaluation should be shown after any console logs from the code executed
(Assignee)

Updated

3 years ago
Blocks: 1111089
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Comment 2

3 years ago
Created attachment 8698762 [details]
MozReview Request: Bug 1044365 - Do not force webconsole evaluation result to show up immediately after the input;r=vporof

Review commit: https://reviewboard.mozilla.org/r/28109/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/28109/
Attachment #8698762 - Flags: review?(vporof)
(Assignee)

Updated

3 years ago
Assignee: nobody → bgrinstead
Status: NEW → ASSIGNED
Comment on attachment 8698762 [details]
MozReview Request: Bug 1044365 - Do not force webconsole evaluation result to show up immediately after the input;r=vporof

https://reviewboard.mozilla.org/r/28109/#review25471

This looks good to me, but I'm not entirely confident reviewing webconsole frontend code, so you might want to pass this by panos as well.
Attachment #8698762 - Flags: review?(vporof) → review+
(Assignee)

Comment 4

3 years ago
Comment on attachment 8698762 [details]
MozReview Request: Bug 1044365 - Do not force webconsole evaluation result to show up immediately after the input;r=vporof

Additional request from Comment 3
Attachment #8698762 - Flags: review?(past)
Comment on attachment 8698762 [details]
MozReview Request: Bug 1044365 - Do not force webconsole evaluation result to show up immediately after the input;r=vporof

https://reviewboard.mozilla.org/r/28109/#review25637

Since this behavior appears to exist since ancient times and I can't find any rationale for it, let's avoid all these complications and do the simple thing.
Attachment #8698762 - Flags: review?(past) → review+

Comment 8

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/2903b0280572
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox46: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 46
(Assignee)

Updated

2 years ago
Whiteboard: [console-spec]
(Assignee)

Updated

2 years ago
Duplicate of this bug: 1214400

Comment 10

2 years ago
I have reproduced the bug in Nightly 34.0a1 (2014-07-25) on windows 7 32 bit comment 0

Bug is fixed now on Latest Developer Edition 46.0a2 (2016-03-05)(Build ID:20160305004010)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:46.0) Gecko/20100101 Firefox/46.0


[testday-20160304]
Successfully Reproduced this bug with Firefox Nightly 34.0a1 (2014-07-25) on Linux, 64 Bit with the instructions from comment 0 

This Bug is now verified as fixed Latest Firefox Developer Edition 46.0a2 (2016-03-05)

Build ID: 20160305004010
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
QA Whiteboard: [testday-20160304]
Status: RESOLVED → VERIFIED
status-firefox46: fixed → verified
You need to log in before you can comment on or make changes to this bug.