You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see in the _log method that the backtrace message is a concatenation of the file path, a space, a colon, another space, and then the line number. The console drops the line number, resulting in something like this:
/path/to/file.php :
I noticed that if I add another colon and character to the backtrace message that the line then shows up, so a backtrace message that looks like this:
/path/to/file.php : 10 : 0
Will end up showing the console as:
/path/to/file.php : 10 :
So either the console is expecting something different, or the console is broken. If the console is expecting something different, it would be good to fix it. If the console is not expecting something different, then I need help with how to submit a bug to Firefox on this.
The text was updated successfully, but these errors were encountered:
I think this is a bug from firefox console, but it can be fixed by changing the ChromePhp lib, adding 0 at the end of the backtrace instead of : 0 like you did.
I rebased some PR (from @okonomiyaki3000 and @ErikKrause repo). If you use it, you simply have to add this settings to make it works for firefox :
Line numbers are not working for me in Chrome. There is a bug when 'show line numbers' is active. log.js:81 shows 'unknown' in the console before every message.
I see in the _log method that the backtrace message is a concatenation of the file path, a space, a colon, another space, and then the line number. The console drops the line number, resulting in something like this:
I noticed that if I add another colon and character to the backtrace message that the line then shows up, so a backtrace message that looks like this:
Will end up showing the console as:
So either the console is expecting something different, or the console is broken. If the console is expecting something different, it would be good to fix it. If the console is not expecting something different, then I need help with how to submit a bug to Firefox on this.
The text was updated successfully, but these errors were encountered: