url getter special cases data: URLs

WICG / element-timing

A proposal for an Element Timing specification.

https://wicg.github.io/element-timing/

Other

57 stars 15 forks source link

url getter special cases data: URLs #64

Open annevk opened 2 years ago

annevk commented 2 years ago

Why special case data: URLs? Other URLs can be thousands of code points as well...

npm1 commented 2 years ago

Is that common though? The thinking was to align with Resource Timing on URLs that are fetched (that API does not trim URL names) but to not store the enormous URL for inline images which are in data: URLs.

mmocny commented 2 years ago

If we wanted to consistently truncate all URLs, rather than to rely on a convention which works well most but not all of the time, we discussed some options today:

Truncate all URLs, but increase the number of codepoints to something larger, like 1k-4k
Truncate all URLs to 100 code points-- but then also add a hash of the full URL
Change to only return a hash of the URL