1354073 - Console.log() is capitalizing 'l' characters in a url string

Status: RESOLVED FIXED

(DevTools :: Console, defect, P2)

Description

[Laurent]

Attachment: Firefox52-console-bug.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170323105023

Steps to reproduce:

1) Create a simple html page with a script tag that contains:

    console.log("http://api.openweathermap.org/data/2.5/weather?units=metric&lang=fr&lat=48.853&lon=2.35");

2) Start Firefox in safe mode (to avoid any extension side-effect)

3) Hit F12 (developper tools) or Ctrl+Shift+J (Navigator console) to open Firefox console

4) Drag-and-drop the simple html page in Firefox



Actual results:

The console displays the message:

  "http://api.openweathermap.org/data/2.5/weather?units=metric&Lang=fr&Lat=48.853&Lon=2.35"

  Notice the uppercase "L" to Lang, Lat and Lon instead of lowercase "l".
  
  See screen copy in the attached file.



Expected results:

The console should display the text unchanged.

http://api.openweathermap.org/data/2.5/weather?units=metric&lang=fr&lat=48.853&lon=2.35

Comment 1

[YF (Yang)]

Testcase:
<script>
 console.log("http://llLL");
</script>


It is a display problem due to italics for url.

Comment 2

[Brian Grinstead [:bgrins]]

Attachment: log-message.png

That's really weird.  I'm not seeing the capital L issue in a clean profile on 52 (or in Nightly builds 55).  When loading data:text/html,<script>console.log("http://api.openweathermap.org/data/2.5/weather?units=metric&lang=fr&lat=48.853&lon=2.35");</script> here's what I see

Comment 3

[Brian Grinstead [:bgrins]]

Just tested Firefox 50.0 on Windows 7 and I am seeing the issue

Comment 4

[Brian Grinstead [:bgrins]]

Also seeing this on Windows 10 (Firefox 52 and 54).  This is fixed with the new frontend (currently on by default in nightly builds and work is in progress to enable it in release) so I'm going to block it on Bug 1308219, I'd definitely accept a fix in the meantime.

Comment 5

[Laurent]

Attachment: devtools.webconsole.new-frontend-enabled = true or false

In about:config, set devtools.webconsole.new-frontend-enabled to true solves the issue. See attachement.

Comment 6

[Brian Grinstead [:bgrins]]

Fixed by the new frontend shipping.