STEPS: Win2k system, w/ AOL 6 already installed. Load any Mozilla/Netscape product that has WinNT/RAS auto-dial enabled. Initiate network activity w/o dialing. OBSERVED BEHAVIOR: An AOL configured dialer comes up, but does not dial successfully when you say connect. EXPECTED BEHAVIOR: I don't think AOL allows you to dial outside the client. I think we should detect this an not fire the auto-dialer if we know it is not going to work.
If there is no way to determine that the dial config will not work, we need to pref this behavior so people can turn it off.
Hi, Steve: Could the autodial feature be turned off totally after it had been triggered? Thx!
Tao: Shouldn't Netscape and AOL products should place nice on the same system together) I don't know much about AOL client and it's system configs (hence my general orientation to not having software that modifies system files unless we know in advance we have a lot of expertise in that area). My impression is that AOL client configures it's dialup profile via the normal system interfaces, but that the dialer cannot be used by anyone besides the AOL client itself. Can you find someone who is more familiar with AOL client to look at this bug?
Seems that the AOL client is not a well-behaved dialer. When you dial it via the RAS system calls, it should return after it connects like the other dialers do. AOL client doesn't return until it exits. Mozilla will remain hung until the RAS system call returns. Theres not much we can do about it, except many dont dial if the dialer is AOL. Not sure how to tell except by name, which may have been changed by the user.
helpwanted is not for bug submissions anymore.
clean-report: ready for assignment What's the next action here? Shouldn't this be assigned and/or get AOL to explain how they configure the dialers?
over to steve to take a look at this. steve, i think we should try to resolve this for the mozilla 1.3 milestone.
marking invalid based on comment#4