New issue
Advanced search Search tips

Issue 670883 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: relative links are not linkified in console errors

Project Member Reported by l...@chromium.org, Dec 2 2016

Issue description

Links inside of the red text in an error are not always linkified correctly.  See screenshot for example.

Another example:
console.error('Error\nat (../script.js:1:0)')

Similar to  crbug.com/535463 
 
badlyLinkifiedLinks.png
152 KB View Download

Comment 1 by l...@chromium.org, Dec 2 2016

Cc: paulir...@chromium.org

Comment 2 by l...@chromium.org, Dec 3 2016

Currently we aren't doing any relative path resolution, so linkifying them to script locations in Sources isn't possible without a new relative path resolution feature.

What we can do is make these relative paths at lease linkify as external links.  tryFormatAsError() tries to extract links, but gives up completely on candidates that it cannot parse as a ParsedURL.  It should be possible to make it more lenient for this case.

Comment 3 by l...@chromium.org, Dec 5 2016

For reference, there was a similar bug that ended up as WontFix:  crbug.com/535463 .  Let's make sure to test that URLs with valid URLs inside them don't trigger long regex execution time.

Comment 4 by l...@chromium.org, Dec 14 2017

Status: Fixed (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Dec 14 2017

Sign in to add a comment