Closed
Bug 40642
Opened 24 years ago
Closed 24 years ago
Sounds will fail when resources are packaged into jars
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: selmer, Assigned: pavlov)
References
Details
(Whiteboard: [nsbeta2-])
I don't know what component this falls under. Please correct it if I got it wrong. Hyatt has looked at some of the code that would break if we jarred all our resources. One thing he found was that we convert URIs into pathnames to open sound files through the GTK. This will fail after jarring because the jar isn't the sound file. It needs to be fixed to use streaming. Further details from Hyatt.
Reporter | ||
Comment 1•24 years ago
|
||
Adding skins keyword because jarring is mainly for skins.
Keywords: skins
Assignee | ||
Comment 2•24 years ago
|
||
are sounds in for beta2? if so, this needs to be fixed.
Nominating for nsbeta2. We need to decide in PDT if sound support is required for nsbeta2. JARs are not really a skin issue, JAR support is a issue having to do with the number of files installed with Netscape 6 and disk footprint. If we decide to turn on JAR support we will need to fix GTK sounds because they use code that goes to the sound file with a file path rather than a chrome path and a stream. My feeling is that if we decide to activate JARs for nsbeta2 then we should fix the sound code for nsbeta2.
Assignee | ||
Comment 4•24 years ago
|
||
this isn't just GTK, changing summary
OS: Linux → All
Summary: GTK sounds will fail when resources are packaged into jars → Sounds will fail when resources are packaged into jars
Putting on [nsbeta2-] radar. Not critical to beta2. But adding perf and nsbeta3 keyword to get done for PR3.
Keywords: nsbeta3
Whiteboard: [nsbeta2-]
Assignee | ||
Comment 6•24 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•