Hey, it worked in Moz. How was I supposed to know?:)
Do what every self-respecting web designer does and validate the HTML on pages you generate. Then your pages will have a much greater chance of working correctly in every browser.
There's no need to beat anyone! Just sumbit a Tech Evangelism bug report on Bugzilla for these sites, and Mozilla engineers will cheerfully help the site owner make it work with all browsers.
No amount of complaining on my part is going to change any of these sites. On the other hand, most users (my wife for example) hit one site that doesn't work in Opera and decide to go back to IE forever. My big fear is that cluelessness like thiswill continue to allow IE to dominate the browser market. I think that.NET is only going to make this worse.
Perhaps your complaining won't help. But logging the site in a Tech Evangelism bug report (this link works) will help. Mozilla engineers will contact the site and let the owners know what needs to be done to make the site work in all standards-compliant browsers. As Mozilla-based and other non-IE browsers such as Opera make up more market share, web designers will start to realize that it makes economic sense to support them.
Mozilla doesn't support most IE extensions to the HTML standard. You should report that site in a Tech Evangelism bug to Bugzilla so the site can be fixed.
It's better to file a Tech Evangelism bug in Bugzilla for sites that don't work. That way, the Mozilla team can track these sites and offer technical assistance to make them standards compliant.
With the latest versions of Mozilla, it automatically detects JRE 1.4.0 and uses it. Try the latest nightly and report a bug if it doesn't work.
Re:Mozilla/Netscape usage - Charles Upsdell's site
on
Mozilla RC3 Released
·
· Score: 2, Informative
I've been using Charles Upsdell's Browser News for reliable browser stats. According to that site, Mozilla/Netscape/K-Meleon/etc. browsers currently have a 1.1% share of page hits, IE has about 92%, and Netscape 4 about 4%.
Well, I need netscape anyway because some sites won't let you install a plugin for mozilla but only netscape or explorer.
The Mozilla PluginDoc project was created to help Mozilla users with installing their plugins. Go to that website to get instructions on how to install your favorite plug-in without needing Netscape.
What are the odds of speeding up mozilla's responsiveness in the future?
100%. Mozilla generally gets faster and uses less memory with each milestone. The biggest speed problem is actually RAM usage -- if your computer is low on RAM Mozilla will cause lots of disk swapping. I'd recommend at least 128 MB of physical RAM for decent performance for now.
Redrawing Bug Re: Yes - it can cause Win2K to BSOD
on
Mozilla 1.0 RC2 is out
·
· Score: 1
It's possible that the BSOD bug is related to the bug on the screen redrawing problem in bug 133132. If Mozilla stops redrawing part of its windows or images turn black-and-white before Win 2K crashes, it's probably due to bug 133132.
I expect funding for astronomers who want to spot asteroids and figure out how to deflect those that are headed for Earth won't come until an asteroid actually hits us. We didn't get real airport security until after 9/11, after all...
According to Tech Evangelism bug 89853, this problem hasn't been fixed yet. From reading the bug report, it does look like they're trying to solve the problem. Probably the prospect of AOL using Gecko will motivate them some more!
However, the major hold up is that my bank refuses to allow me to use it - the site became inaccessible to modern Netscape/Mozilla browsers curiously enough at about the same time the whole thing went.asp-based.
You should enter these problems as Tech Evangelism bug reports. After you've done this, a Mozilla evangelist will contact the site maintainer and help them fix the site.
If you find a page that doesn't work well with Mozilla, you can file a Tech Evangelism bug report. The Intel site does have bug 113099 reported against it. If this is the bug you're experiencing you can vote for it, or you can go report your bug.
Slashdot Mirror
You can read PostScript files on Windows, Mac, Linux, OS/2, and VMS with GhostScript.
There's no need to beat anyone! Just sumbit a Tech Evangelism bug report on Bugzilla for these sites, and Mozilla engineers will cheerfully help the site owner make it work with all browsers.
Mozilla doesn't support most IE extensions to the HTML standard. You should report that site in a Tech Evangelism bug to Bugzilla so the site can be fixed.
Why ask how to do something when you already know perfectly well that there are open bugs on the feature? IHBT!
It's better to file a Tech Evangelism bug in Bugzilla for sites that don't work. That way, the Mozilla team can track these sites and offer technical assistance to make them standards compliant.
With the latest versions of Mozilla, it automatically detects JRE 1.4.0 and uses it. Try the latest nightly and report a bug if it doesn't work.
I've been using Charles Upsdell's Browser News for reliable browser stats. According to that site, Mozilla/Netscape/K-Meleon/etc. browsers currently have a 1.1% share of page hits, IE has about 92%, and Netscape 4 about 4%.
Sounds like bug 143602. Needless to say, the vast majority of Mozilla users do not experience this bug!
It's possible that the BSOD bug is related to the bug on the screen redrawing problem in bug 133132. If Mozilla stops redrawing part of its windows or images turn black-and-white before Win 2K crashes, it's probably due to bug 133132.
Bug 132440 has been filed for a UI way to disable the Download Manager.
Just a guess, but you might be experiencing a GDI problem reported in http://bugzilla.mozilla.org/show_bug.cgi?id=133132
It works great for me with the latest nightly trunk build. Try it -- in my experience it's better than the 1.0 branch builds!
I expect funding for astronomers who want to spot asteroids and figure out how to deflect those that are headed for Earth won't come until an asteroid actually hits us. We didn't get real airport security until after 9/11, after all...
According to Tech Evangelism bug 89853, this problem hasn't been fixed yet. From reading the bug report, it does look like they're trying to solve the problem. Probably the prospect of AOL using Gecko will motivate them some more!
If you find a page that doesn't work well with Mozilla, you can file a Tech Evangelism bug report. The Intel site does have bug 113099 reported against it. If this is the bug you're experiencing you can vote for it, or you can go report your bug.