New issue
Advanced search Search tips

Issue 610804 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

data URIs display inconsistent in developer tools, useless really

Reported by pdk...@gmail.com, May 10 2016

Issue description

Chrome Version       : 50.0.2661.94

Right now, the way Developer Tools reports data URIs is rather useless IMO, and inconsistent too.

(1.png)

It displays some characters from the data URI. In a strange way, but the more important question is: why? I challenge anyone to decode base64 manually, and then decode PNG manually. Nobody can edit this. So why not use a more concise format which actually has some useful information, like the remaining string size.

data:image/png;base64,(500)

(2.png)

Google seems to acknowledge this, as you can only edit the not encoded part really, which is covered with the above format. Trying to move the cursor to a further position takes a minute perhaps. (As established, nobody does this anyway.)

(3.png)

In the network tab, not even the encoding is shown. (It's the same in the Resources panel.) When you hover, it shows the full data URI in a single row only, and truncates overflow. (I couldn't capture this.)
 
Components: Platform>DevTools
Labels: Needs-Feedback
pdknsk@Could you please provide detailed reproducible steps with expected behavior screencast for better understanding the issue to triage it further.

Comment 2 Deleted

Comment 3 by pdk...@gmail.com, May 18 2016

I can't.
Project Member

Comment 4 by sheriffbot@chromium.org, May 19 2016

Labels: -Needs-Feedback Needs-Review
Owner: ssamanoori@chromium.org
Thank you for providing more feedback. Adding requester "ssamanoori@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review
Owner: ----
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
Status: WontFix (was: Assigned)
I'm not sure what do you propose instead? Since nobody edits data URIs manually, it's fine to display them as we do now.

Please provide constructive feedback on what you think the right behavior is.

Comment 8 by pdk...@gmail.com, May 24 2016

(I did?)
Status: Unconfirmed (was: WontFix)
One constructive feedback the report mentions is to show -
data:image/png;base64,(500)
Instead of the full URL.
It makes some sense, since rendering the endless stream of characters everywhere does have performance and memory implications.

Still a WontFix?
Status: WontFix (was: Unconfirmed)
We show the trimmed version. Why invent some new notation instead of using ellipses as everybody does?

Comment 11 by pdk...@gmail.com, May 25 2016

It's trimmed very strangely. Show first 100 or so characters. Skip
1000 characters. Show 100 characters. Skip 100 characters. (And a
reason could be that it's useless.)

Sign in to add a comment