Closed Bug 968862 Opened 12 years ago Closed 8 years ago

Customization process for packaged apps sets unexpected origin

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Harald, Unassigned)

Details

https://wiki.mozilla.org/B2G/MarketCustomizations#packaged_webapp "origin: the origin will be 'app://<app name>' ex: 'app://poppit'" https://developer.mozilla.org/en-US/Apps/Developing/Manifest#origin "The domain name you use should be a domain that you control. The app probably will not be approved for the Firefox Marketplace if it is a domain like app://facebook.com and you are not Facebook." We break that documented rule when preloading. Can somebody explain why the preload process has to set an origin?
Because we preload the registry and gecko doesn't create origins at this stage? But you could use uuid instead of nice looking domains if you want.
> But you could use uuid instead of nice looking domains if you want. Might be more accepted and closer to how normal installed apps behave. Would that break anything?
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.