Evaluate delivery/caching model of client code

RESOLVED INVALID

Status

RESOLVED INVALID
5 years ago
4 years ago

People

(Reporter: abr, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Reporter)

Updated

5 years ago
Blocks: 972004
(Reporter)

Updated

5 years ago
No longer blocks: 972004
(Reporter)

Updated

5 years ago
Blocks: 971986
Adam, can you expand on what this is about? Was this when we were thinking about using social and remote code, but then having some sort of caching?
Flags: needinfo?(adam)
(Reporter)

Comment 2

4 years ago
(In reply to Mark Banner (:standard8) from comment #1)
> Adam, can you expand on what this is about? Was this when we were thinking
> about using social and remote code, but then having some sort of caching?

The best I can reconstruct from my notes is that, yes, this predates our understanding of the risks of using non-bundled-in code for the project. At this point, since we're bundling everything into the browser, I'm going to close this as invalid.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(adam)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.