Closed
Bug 474073
Opened 16 years ago
Closed 16 years ago
Make first run non-xhtml
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: taras.mozilla, Assigned: taras.mozilla)
References
Details
Attachments
(1 file, 1 obsolete file)
3.77 KB,
patch
|
mfinkle
:
review-
|
Details | Diff | Splinter Review |
Taking out the dtd saves 200ms of startup.
Assignee | ||
Comment 1•16 years ago
|
||
Switch to using a js file instead of dtd and to plain html instead of xhtml.
Assignee: nobody → tglek
Attachment #358034 -
Flags: review?(gavin.sharp)
Assignee | ||
Comment 2•16 years ago
|
||
missed firstrun.js in the previous patch
Attachment #358034 -
Attachment is obsolete: true
Attachment #358036 -
Flags: review?(gavin.sharp)
Attachment #358034 -
Flags: review?(gavin.sharp)
Comment 3•16 years ago
|
||
Comment on attachment 358036 [details] [diff] [review]
avoid dtd (with firstrun.js)
I just bitrot this patch pretty good. Rework itand we can get it landed.
Attachment #358036 -
Flags: review?(gavin.sharp) → review-
Comment 4•16 years ago
|
||
We'll have to either figure out a different way to do this, or do some localizer outreach to make sure they understand how to localize the file, but I think this approach can work for now.
Comment 5•16 years ago
|
||
We don't put js files into l10n. That has both security reasons, and l10n policy reasons.
Security as in that we don't trust our localizers to contribute arbitrary js code to our product, and l10n policy in that the number of file formats we expose to localizers is limited.
I don't think that a defines file would work either, that would only fix the policy part, but not the code insertion piece.
We've seen l10n taking other startup hits before, i.e., just having en-US.jar etc seems to have an impact on TP, but I don't see us ripping that out.
IMHO, this should be WONTFIX.
Assignee | ||
Comment 6•16 years ago
|
||
(In reply to comment #5)
> We don't put js files into l10n. That has both security reasons, and l10n
> policy reasons.
Appreciate detailed feedback. I guess our alternatives are to
a) Fix nsFileChannel-related code so it doesnt force a mimetype check on .dtd files
b) stick xhtml11.dtd into a jar
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Comment 7•16 years ago
|
||
did we consider hit difference from .properties? (I expect it to be higher than .dtd, but maybe I'm wrong?)
Also, opeion a) sounds pretty reasonable.
Comment 8•16 years ago
|
||
Gandalf, the perf hit seems to only half-way come from the l10n dtd, but also from the xhtml11.dtd we load from the res:// protocol. Which we do for all xhtml files. Which makes a) a good thing to fix no matter which.
Comment 9•16 years ago
|
||
The JS code here isn't being included in the product, it's only being run in the unprivileged firstun page, for what it's worth.
You need to log in
before you can comment on or make changes to this bug.
Description
•