Closed Bug 464602 Opened 16 years ago Closed 1 year ago

URL drags from the location bar produce escaped UTF-8 urls

Categories

(Camino Graveyard :: Drag & Drop, defect, P3)

All
macOS
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: alqahira, Assigned: chris)

References

()

Details

STR: 1. Visit http://hi.wikipedia.org/wiki/मुखपृष्ठ or another site with a UTF-8 URL fragment 2. Drag the site icon in the location bar to an application that only accepts text drags (e.g. TextWrangler) AR: Pretty UTF-8 URL is all escaped ER: Pretty UTF-8 URL When Safari does this, it puts the unescaped UTF-8 URL in 'url '/public.url, but it continues to place the escaped version in other flavors (WebURLsWithTitlesPboardType, Apple URL pasteboard type, public.utf8-plain-text, NSStringPboardType) In a perfect world, we could fix this in a way that bookmark drags (post-bug 464501) could pick up this fix automatically.
And just for posterity's sake, this is the third (and final, for now, and as far as we know) followup to bug 387312.
Hardware: Macintosh → All
Summary: URL drags form the location bar produce escaped UTF-8 urls → URL drags from the location bar produce escaped UTF-8 urls
Safari exhibits this bug as well. Do we want to do what Safari does when Copy Link Location is used? In that case, everything except 'Apple URL pasteboard type' is unescaped. Or do we just want to unescape everything?
We chatted about this on irc, but for the record, we probably want to keep at least one common type escaped to deal with clients that aren't so Unicode-friendly.
Assignee: nobody → trendyhendy2000
There's not a bug about it (like we do for Copy Link Location, bug 464496), but we should make sure that "Copy Source URL" in the downloads manager is also handled correctly; I can file that if we need it.
Blocks: 491448
These are P3 on the 2.1 list, but I think they're at the very bottom of hendy's to-do list.
Priority: -- → P3
Target Milestone: --- → Camino2.1
Pushing all the UTF-8 stuff out, since it's somewhat risky for this stage in the process.
Target Milestone: Camino2.1 → ---
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.