Closed Bug 295554 Opened 20 years ago Closed 20 years ago

Running 1.0+ nightly from .dmg results in launch without any chrome CSS

Categories

(Toolkit :: Startup and Profile System, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: vlad, Unassigned)

References

()

Details

Downloading the latest Deer Park nightly for OSX and launching the app directly
from the dmg results in the app coming up, but not having any CSS -- the
toolbars and whatnot appear as just smooshed text.  (See URL)

This is different than the 0.9 branch failure, which resulted in an infinite
loop on startup.
Flags: blocking-aviary1.1?
We need to find out when this regressed. Is it possible that it's related to
recent build machine swaps we've made? Sarah or Marcia, can you guys help us
find a regression window?
Flags: blocking-aviary1.1? → blocking-aviary1.1+
In short, this is another form of the issue we had in 1.0 (infinite loop when
launching from disk image). The easiest way to 'fix' it is to make the dmg
writable, also see bug 286421.
Depends on: 286421
Hardware: PC → Macintosh
(In reply to comment #2)
> In short, this is another form of the issue we had in 1.0 (infinite loop when
> launching from disk image). The easiest way to 'fix' it is to make the dmg
> writable, also see bug 286421.

I think that's a pretty bad fix; people will run from the dmg, and then take
that dmg to another computer to install.. and it will no longer be the pristine
mozilla-distributed dmg.  There's potential for who knows what to happen to that
file... I don't think any other app installer dmgs are writable.

If anything, Firefox should just refuse to launch from the dmg, check app path
at launch pop up a dialog saying "please don't launch this from the dmg".
That is sub-optimal, users are used to run apps from disk images, for testing
purpose.
I think the correct solution is to fix bug 286421 (marked as blocking this bug).
Wouldn't we also have a problem launching straight from RO media like a CD? We
definitely want that to work, no? Seems, to my ignorant eye, like this is just
the same issue but with a different file system type.
Fixed by bug 286421
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.