Closed
Bug 614723
Opened 14 years ago
Closed 14 years ago
nsSVGFeatures::PassesConditionalProcessingTests doesn't need to get the intl.accept_languages pref on each call
Categories
(Core :: SVG, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla2.0b8
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
1.70 KB,
patch
|
jwatt
:
review+
roc
:
approval2.0+
|
Details | Diff | Splinter Review |
In fact, usually we don't do a language test.
Assignee | ||
Comment 1•14 years ago
|
||
Assignee | ||
Updated•14 years ago
|
Priority: -- → P1
Whiteboard: [need review]
Assignee | ||
Updated•14 years ago
|
Attachment #493155 -
Flags: review?(jwatt)
Updated•14 years ago
|
Attachment #493155 -
Flags: review?(jwatt) → review+
Comment 2•14 years ago
|
||
Probably better to use nsContentUtils::RegisterPrefCallback like we do in nsSVGUtils though.
Assignee | ||
Comment 3•14 years ago
|
||
It's a bit of a pain because we end up having to manage the lifetime of a static string.... I can do it if you want, I guess. But at this point this code only runs if someone is doing filtering on language, right? Which to a first approximation never happens.
Comment 4•14 years ago
|
||
Yeah, never mind that then, I'm sure you have more pressing bugs. ;) I'll file a follow-up.
Comment 5•14 years ago
|
||
Filed bug 614819.
Assignee | ||
Updated•14 years ago
|
Whiteboard: [need review] → [need approval]
Assignee | ||
Comment 6•14 years ago
|
||
Comment on attachment 493155 [details] [diff] [review] Don't get our acceptLangs unless we plan to use it. Requesting approval. Very safe performance improvement that keeps us from doing ridiculous numbers of localized pref gets during SVG frame construction.
Attachment #493155 -
Flags: approval2.0?
Attachment #493155 -
Flags: approval2.0? → approval2.0+
Comment 7•14 years ago
|
||
Pushed http://hg.mozilla.org/mozilla-central/rev/21649e5809fb
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [need approval]
Assignee | ||
Updated•14 years ago
|
Target Milestone: --- → mozilla2.0b8
You need to log in
before you can comment on or make changes to this bug.
Description
•