On Wed, Sep 16, 2009 at 1:06 PM, Erik Kay <[email protected]> wrote: > This is a really good idea. Apparently, I'm not running the URL > through our URLFixerUpper class (I'm not making that name up), which > does a bunch of stuff to fix up URLs that someone may have typed in or > copied and pasted in (not just the http:// example you gave). > > I filed http://code.google.com/p/chromium/issues/detail?id=22038 for > this. In the future, feel free to just go ahead and file the bug > directly.
I would have leaned the other way, that our API should be pedantic and require a correct URL. In some cases, passing an incomplete URL is a bug on the developer's part and they would want to know at development time, rather than storing bad data. - a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
