Closed
Bug 762743
Opened 12 years ago
Closed 9 years ago
Multiple silverlight objects fails to load when Application Library Caching is turned on and they share the same splashScreenSource parameter
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 722034
People
(Reporter: rowenmcd, Unassigned)
References
Details
Attachments
(1 file)
1.53 MB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.52 Safari/536.5 Steps to reproduce: Create a web page with three different silverlight applications embedded. The silverlight apps have Application Library Caching turned on. They all share the same silverlight splashScreenSource parameter (coming from clientBin folder on one of the silverlight apps). Please find sample attached. Actual results: On first render everything works fine. However once files are cached in browser, with subsequent page renders, only the first silverlight object on the page loads successfully. The others silently fail to load. Expected results: All three silverlight objects should load each time page is rendered. In order to resolve, I can a) turn off Application Library Caching on the silverlight projects... or b) specify a unique path for the splashScreenSource parameter for each of the silverlight objects.
Comment 1•12 years ago
|
||
It works in Nightly16.0a1 and Aurora15.0a2 but not Beta14.0 Fixed range: Bad: http://hg.mozilla.org/mozilla-central/rev/306365557d64 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/15.0 Firefox/15.0a1 ID:20120531145004 Fixed: http://hg.mozilla.org/mozilla-central/rev/73783bf75c4c Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/15.0 Firefox/15.0a1 ID:20120601030520 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=306365557d64&tochange=73783bf75c4c I guess this was fixed by Bug 746018
Component: Untriaged → Networking
Depends on: 746018
Product: Firefox → Core
QA Contact: untriaged → networking
Updated•12 years ago
|
tracking-firefox14:
--- → ?
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•12 years ago
|
||
This problem existed since Firefox4. This is not a recent regression.
tracking-firefox14:
? → ---
Comment 3•12 years ago
|
||
Sorry, This was fixed by Bug 722034
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•