Closed Bug 108619 Opened 23 years ago Closed 23 years ago

investigate the cost of security icon

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cathleennscp, Assigned: law)

References

Details

please provide a patch to remove security icon to the bug for further analysis.
Blocks: 7251
Here's performance test results comparing a standard Navigator to one with the
overlay for securityOverlay.xul commented out:

----- base/modern -----
00008.188: ...main1
00008.078: ...main1
00008.343: ...main1
----- noSecurityOverlay/modern -----
00008.156: ...main1
00008.078: ...main1
00008.297: ...main1
avg1=8.203000 avg2=8.177000 diff=0.026000 (0.316957%)
----- base/modern -----
00008.171: ...main1
00008.328: ...main1
00008.203: ...main1
----- noSecurityOverlay/modern -----
00008.172: ...main1
00008.109: ...main1
00008.031: ...main1
avg1=8.234000 avg2=8.104000 diff=0.130000 (1.578820%)
----- base/modern -----
00008.125: ...main1
00008.219: ...main1
00008.063: ...main1
----- noSecurityOverlay/modern -----
00008.157: ...main1
00008.125: ...main1
00008.093: ...main1
avg1=8.135667 avg2=8.125000 diff=0.010667 (0.131110%)

The savings varied widely, from negligible to 1.58%).

Needs further analysis to determine the actual savings.  To realize this gain,
we'd have to defer loading this overlay till we hit a secure page.  That could
likely be done with some JS and .xbl/.css magic.

On hold pending further measurement and decision as to whether to pursue some
sort of overlay-free chrome packaging scheme.
done
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.