You need to
before you can comment on or make changes to this bug.
When closing and reopening the inspector the console groups are messed up and in the wrong order and logs are lumped into the last group. See the attached screenshot and test.
1) Load the test case.
2) Open the inspector's console.
Notice the order of the groups does not match the file.
Reloading the page while the inspector is open gives the correct results.
Created an attachment (id=22539) [details]
Created an attachment (id=22540) [details]
Created an attachment (id=22541) [details]
Also in the messed up state, expanding/collapsing one of the top level groups, toggles all of the groups in that level, not just the clicked one.
Created an attachment (id=22726) [details]
I forgot to test for this in the way. This fixes the issue. I realized you can't properly do this without recording where the group ended, so now there's StartGroup and EndGroup message levels.
(From update of attachment 22726 [details])
The patch seems technically correct, but there are some style issues.
+ //if (arguments.isEmpty())
+ // addConsoleMessage(new ConsoleMessage(source, StartGroupMessageLevel, exec, String(), lineNumber, sourceURL, m_groupLevel));
We don't comment out code. Just remove it.
Attach a new patch that removes this and i'll r+ it.
Created an attachment (id=22793) [details]
removed commented out code
Landed in r35788.