Status: Assigned Owner: [email protected] CC: [email protected], [email protected], [email protected] Labels: Type-Bug Pri-1 OS-All Area-BrowserBackend Mstone-1.1
New issue 5791 by [email protected]: We should not be re-defining the meaning of the chrome:// URL scheme! http://code.google.com/p/chromium/issues/detail?id=5791 We should not be re-defining the meaning of the chrome:// URL scheme! This means something already as defined by Mozilla. Trying to make it mean something else in the context of Chrome is sure to cause friction and bugs. We originally used the scheme chrome-resource:// instead of chrome:// for this very reason. For the non-standard URL schemes that we invent, we need to prefix them with a vendor'ish namespace. We've been doing so by using "chrome-" Looks like this change happened here: http://codereview.chromium.org/12418 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
