Closed
Bug 762833
Opened 13 years ago
Closed 9 years ago
Web apps don't work when Firefox is a XULRunner application
Categories
(Firefox Graveyard :: Webapp Runtime, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: glandium, Assigned: glandium)
References
Details
Attachments
(2 files, 2 obsolete files)
Webapps record the firefox path in webapp.ini, and then tries to load xpcom from there, but in FF-on-XR setups, xpcom is in $firefox_path/xulrunner/.
Changing the path recorded in webapp.ini to point to $firefox_path/xulrunner fails too because the runtime tries to open application.ini there.
It looks like the recorded path should be $firefox_path/xulrunner/, and the runtime should check platform.ini instead of application.ini.
Assignee | ||
Comment 1•13 years ago
|
||
As a side note, the runtimes would really benefit from using some common init code...
Assignee | ||
Updated•13 years ago
|
Blocks: metro-build
Assignee | ||
Comment 2•13 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #1)
> Created attachment 631321 [details] [diff] [review]
> Make webapp runtime use platform.ini from the GRE directory
>
> As a side note, the runtimes would really benefit from using some common
> init code...
This doesn't work properly, though.
Assignee | ||
Comment 3•13 years ago
|
||
I'm wondering if it wouldn't make sense to ship the webapprt in xulrunner...
Assignee | ||
Updated•13 years ago
|
Component: Web Apps → Webapp Runtime
QA Contact: webapps → webapp-runtime
Assignee | ||
Updated•13 years ago
|
status-firefox14:
--- → affected
status-firefox15:
--- → affected
Comment 4•13 years ago
|
||
Should only be FF 15 or later affected, as we have disabled web apps support on FF 14.
status-firefox14:
affected → ---
Updated•13 years ago
|
Priority: -- → P3
Assignee | ||
Comment 5•13 years ago
|
||
This fixes my problems on FF-on-XR and should help with not breaking things after bug 755724 and I think it's the sensible thing to do. It only addresses the issue on linux, though. It would surely benefit from bug 763071 and bug 658847.
<none>
Assignee | ||
Updated•13 years ago
|
Attachment #631321 -
Attachment is obsolete: true
Updated•13 years ago
|
QA Contact: jsmith
Updated•13 years ago
|
status-firefox15:
affected → ---
status-firefox16:
--- → wontfix
Assignee | ||
Comment 6•12 years ago
|
||
A more lightweight approach.
Assignee | ||
Updated•12 years ago
|
Attachment #631623 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → mh+mozilla
Assignee | ||
Updated•12 years ago
|
No longer blocks: metro-build
Comment 7•12 years ago
|
||
We hit this problem in Fedora, is it a problem to add webapprt also to xulrunner (like done in attached patch)?
Assignee | ||
Comment 8•12 years ago
|
||
(In reply to jhorak from comment #7)
> Created attachment 716443 [details] [diff] [review]
> Workaround to build webapprt also in xulrunner
>
> We hit this problem in Fedora, is it a problem to add webapprt also to
> xulrunner (like done in attached patch)?
webapprt is built as part of browser/ and that should be fine. If that doesn't work (and I heard it doesn't in recent releases in debian, but it used to work), that's a bug.
Assignee | ||
Comment 9•12 years ago
|
||
Oh, the webapp installer stuff moved to toolkit...
Assignee | ||
Comment 10•12 years ago
|
||
So, the logical solution here would be to build the webapp runtime as part of the platform. But this would need the webapp runtime localization to move where it should be. I'll file a bug about that.
Comment 11•12 years ago
|
||
I've checked the dependent bugs and they seems to be fixed, can we also fix this bug?
Comment 13•11 years ago
|
||
The problem still persists in Fedora 19. Here's a workaround:
ln -s /usr/lib64/firefox/webapprt-stub /usr/lib64/firefox/xulrunner/
ln -s /usr/lib64/firefox/webapprt /usr/lib64/firefox/xulrunner/
ln -s /usr/lib64/firefox/application.ini /usr/lib64/firefox/xulrunner/
And I can confirm that after doing that, evertything seems to be working ok.
Updated•11 years ago
|
Flags: needinfo?(mh+mozilla)
Comment 14•11 years ago
|
||
Mike, is it now ok to build the webapp runtime also for XULRunner?
Assignee | ||
Comment 15•11 years ago
|
||
I'd rather put it in the platform as mentioned in comment 10. Either way, the branding problem from i don't remember which bug remains.
Flags: needinfo?(mh+mozilla)
Comment 16•11 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #15)
> I'd rather put it in the platform as mentioned in comment 10. Either way,
> the branding problem from i don't remember which bug remains.
Yes, the branding problem is a separate issue.
Assignee | ||
Comment 17•11 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #16)
> (In reply to Mike Hommey [:glandium] from comment #15)
> > I'd rather put it in the platform as mentioned in comment 10. Either way,
> > the branding problem from i don't remember which bug remains.
>
> Yes, the branding problem is a separate issue.
It's not separate, it's entangled.
Comment 18•11 years ago
|
||
Some reference on Debian and Red Hat
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699294
https://bugzilla.redhat.com/show_bug.cgi?id=912398
Comment 19•11 years ago
|
||
Any news about this bug?
This create some problems on the linux world for promote the open web apps :-(
Comment 20•9 years ago
|
||
Per bug 1238079, we're going to disable the desktop web runtime and remove it from the codebase, so we won't fix these bugs in it.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•9 years ago
|
Product: Firefox → Firefox Graveyard
Updated•7 years ago
|
status-firefox16:
wontfix → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•