I don't think anyone has any objection to DOMUIifying those pages, and I don't think it would be a large amount of work. The only reason they're not is that there hasn't been a reason to do so.
On Tue, Jan 5, 2010 at 1:04 PM, Pierre-Antoine LaFayette <[email protected]> wrote: > Apparently Google Groups doesn't add the [chromium-dev] in the subject line > when you post from the web app... > > 2010/1/1 plafayette <[email protected]> >> >> http://crbug.com/24421 and http://crbug.com/27772 seem to hint that >> these directory listing pages would benefit from being handled at a >> higher level than the WebKit Glue Layer (or the net module in the case >> of file:///), namely as a DOM ui page. Is there any reason why >> ChromiumOS' chrome://filebrowse DOM ui page couldn't be generalized to >> be used for these other directory listing pages? I haven't looked too >> deeply into what amount of work this would require. Is this a >> reasonable solution for these issues? >> >> Thanks, >> Pierre. > > > -- > Pierre. > > -- > Chromium Developers mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev >
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
