Closed Bug 46172 Opened 25 years ago Closed 25 years ago

with AtGuard 3.2 ad-blocking enabled, the statusbar displays over 100% complete when loading the above url

Categories

(Core :: Networking, defect, P3)

x86
Windows 95
defect

Tracking

()

VERIFIED DUPLICATE of bug 44126

People

(Reporter: termite, Assigned: gagan)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; m17) Gecko/20000719 BuildID: 2000071910 When AtGuard 3.2 ad-blocking is enabled, the progress bar on the status bar displays percentages over 100%. When AtGuard is disabled, behaviour is normal. Not tested with the successor to AtGuard: Norton Internet Security. Reproducible: Always Steps to Reproduce: 1. Install AtGuard 3.2 2. Enable Ad-Blocking 3. Load www.mozillazine.org in Mozilla 4. Observe progress bar. Actual Results: progress bar displayed percentages over 100% Expected Results: showed normal progress - percentages below 100% I would guess this also occurs with other ad-blocking software. Would be a good idea to test it with NIS, since AtGuard has been discontinued. I have seen this behaviour on other websites as well, when AtGuard prevents a graphic from displaying.
does it block the ads? I heavily doubt this is fixable, and the progress bar is as is not always perfect, which is a known bug
Yes, ads are blocked
over to toolkit.
Assignee: asa → trudelle
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm
possibly just a variation on bug #44126, but this is not xptoolkit (the progressmeter just displays what it is told to display). Moving to necko, but this may ultimately be xpapps (navigator.js code).
Assignee: trudelle → gagan
Component: XP Toolkit/Widgets → Networking
QA Contact: jrgm → tever
Marking Dup *** This bug has been marked as a duplicate of 44126 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verifying as a duplicate of bug 44126 'status bar progress meter craziness'
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.