1334822 - New console logger for server messages does not allow for adding line number

Status: RESOLVED WONTFIX

(DevTools :: Console, defect)

Description

[iamsentme]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125172221

Steps to reproduce:

My computer is Ubuntu 16.04, and it updated Firefox to v43 yesterday.

When set the X-ChromeLogger-Data header for server message logging, the backtrace file path and line number is set:

/path/to/file.php : 23


Actual results:

In the console, the path and colon appears, but not the line number:

/path/to/file.php : 

Also, the line and column numbers should be red, but they are not.


Expected results:

I should see the path and line number:

/path/to/file.php : 23

Comment 1

[iamsentme]

<?php

/**
To EASILY TEST WITH PHP, USE THIS:
*/

// This displays "/path/to/example_url.php :"
$backtrace_message1 = '/path/to/example_url.php : 777';

// This displays "/path/to/example_url.php : 777 :" 
$backtrace_message2 = '/path/to/example_url.php : 777 : 0';

// This displays "(unknown)"
$backtrace_message3 = '/path/to/example_url.php : 777 :';

header( 'X-ChromeLogger-Data: ' . base64_encode( utf8_encode( json_encode( [
	'version' => '0.0.1',
	'columns' => [
		'log', 
		'backtrace', 
		'type'
	],
	'request_uri' => 'example_url.php',
	'rows' => [
		[
			['epoch: ' . time()],
			$backtrace_message1,
			''
		],
		[
			['epoch: ' . time()],
			$backtrace_message2,
			''
		],
		[
			['epoch: ' . time()],
			$backtrace_message3,
			''
		]
	]
] ) ) ) );

Comment 2

[Loic]

Could you provide a live example (or an example without php), it will help a lot.

Comment 3

[iamsentme]

(In reply to Loic from comment #2)
> Could you provide a live example (or an example without php), it will help a
> lot.

Live example:
https://brianswebdesign.com/noline.php

Comment 4

[Loic]

Duplicate of bug 1321957?

Comment 5

[iamsentme]

(In reply to Loic from comment #4)
> Duplicate of bug 1321957?

No, this is not the same issue at all. The other bug is related to opening the source of files in the debugger, but this bug is for the line numbers not displaying according to the technical specs.

The technical specs are here:
https://craig.is/writing/chrome-logger/techspecs

Comment 6

[Krzysiek Grzembski]

It actually cuts off everything after last colon, so:

some/fake/page/address (90):(90)
results in 
some/fake/page/address (90):

or 

some/fake/page/address (90):(90):0
results in
some/fake/page/address (90):(90):

or 

some/fake/page/address (90):(90):0:98:80
results
some/fake/page/address (90):(90):0:98:

Comment 7

[iamsentme]

(In reply to Krzysiek Grzembski from comment #6)
> It actually cuts off everything after last colon, so:
> 
> some/fake/page/address (90):(90)
> results in 
> some/fake/page/address (90):
> 
> or 
> 
> some/fake/page/address (90):(90):0
> results in
> some/fake/page/address (90):(90):
> 
> or 
> 
> some/fake/page/address (90):(90):0:98:80
> results
> some/fake/page/address (90):(90):0:98:

This is exactly what I was trying to convey when reporting the bug.

Comment 8

[Nicolas Chevobbe [:nchevobbe]]

The console does not support server logs natively now. Bug reports should be made in chrome-logger extension.

Comment 9

[iamsentme]

chrome-logger extension, along with almost all useful FF extensions, no longer works with FF57. At some point, when the damage is done, maybe somebody can make it good again.

Comment 10

[Nicolas Chevobbe [:nchevobbe]]

Are you talking about this extension https://addons.mozilla.org/en-US/firefox/addon/chromelogger/ ? A new version was pushed yesterday, and everything should be fine.


Also, if you are missing extensions, you can nicely ask in http://discourse.mozilla.org/ if there are any alternative/plans to have them migrated to webextension.