[Webkit-unassigned] [Bug 29000] Implement HTML5's fakepath

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=29000





--- Comment #11 from Maciej Stachowiak <mjs at apple.com>  2009-09-13 14:46:15 PDT ---
Yes, this behavior is lame. But it seems to be the best available choice given
the compatibility, platform-independence and privacy constraints. In
particular:

1) Exposing the real path is a privacy/security risk.
2) Exposing Unix-style paths breaks some content, including router Web
interfaces and apparently Orkut
3) Exposing bare filenames has some of the same issues as #1.

Web developers still have the ability to get the real filename without regexp
mangling by using control.fileList[0].fileName. More importantly, from a
compatibility perspective, since other browsers are doing this, Web content
authors *already* have to be prepared to strip the fakepath prefix. So we're
not doing Web developers any favors by omitting it.

And finally, while the lameness of this compatibility hack is very visible,
it's hardly the lamest compatibility hack in the Web platform. Take a look at
WebKit's "quirky em" unites or how parsing works when a <form> is misnested
inside table structure. This hack just seems gross because it is easy to
understand its wrongness without being an expert in the relevant part of the
code.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.