Summary: | [GTK] XDG extended attributes spec support | ||
---|---|---|---|
Product: | WebKit | Reporter: | Avid Seeker <avidseeker7> |
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | ap, bugs-noreply, ie2kl43y, mcatanzaro, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Avid Seeker
2023-08-27 13:32:20 PDT
Moving from https://gitlab.gnome.org/GNOME/epiphany/-/issues/2165, as I mentioned there, the standard has no mention of user.xdg.referrer. It would be of questionable utility anyway: what would you ever want to use that for? We could set user.xdg.origin.url though. I'd like to ensure that at least Firefox or Chrome already does this, though, because users might be very surprised if we add extra metadata to downloaded files that other web browsers do not add. I'm guessing that the point of referrer is probably that it's what the user thinks of as where they've downloaded from. The trust comes from the referring HTML page, not from where the file is served from. There is limited visibility for the user into the actual download URL, especially if there are redirects happening. Discussion thread here, including some negative feedback from the nautilus developers: https://discourse.gnome.org/t/feat-xdg-extended-attribute-spec-support/16892 |