Slashdot Mirror

Ben Bucksch of Beonex fame has offered to work on the roaming profile support on a tips-for-code basis. See bug 17048 for the background, and bug 124026 for the funding issues.

Looks very promising -- if you want this feature, consider throwing in a few dollars. If this kind of development model turns out to work well, it could be a revolution for large Open Source / Free Software projects.

Are you talking about obfuscating it in source code (mailto:)? If so tell me how! I always figured that if a browser could read it so could a harvester, but would love to be proved wrong.

Mitch Stoltz does that with his name on http://www.mozilla.org/projects/security/component s/. He wraps the mailto: address in javascript. If you do that, visitors who have disabled javascript won't see or be able to use your mailto: link.

If you read the release notes for Mozilla 0.9.8 you'll see how to get Java applets working by installing Sun's JRE and copying one file. There are some bugs in Java support that could be fixed, but copying that one file has worked fine for me.

If you read the release notes for Mozilla 0.9.8 you'll see how to get Java applets working by installing Sun's JRE and copying one file. There are some bugs in Java support that could be fixed, but copying that one file has worked fine for me.

Mozilla uses the Java Plug-in from Sun. This is an API that allows Mozilla to use the lastest version of Java with out having to wait for Netscape to provide support. Need to create an applet that uses Java 1.4 functionaly? Just install the lastest plugin, copy a few files from your JRE to mozilla's plugin directory and restart!

Currently Mozilla needs work in the area of finding the Java Plugin and setting up the connection between the two. Until then, copy the file 'NPOJI610.DLL' from your JRE's bin directory to the plugin folder for Mozilla and restart Mozilla.

This is documented in the relase notes

Interesting my ass.

Well all browsers have this by default, except its less of a holding motion than a tapping motion. Try tapping your right mouse button moving the mouse, to the right and slighly down, tap again. Bingo you just went back. A bit farther down, you just went up. Try doing this freqently, and you will find its just as fast as opera gestures. -grin- I'm serious.

In Netscape 4, it's even faster: push the right mouse button down, move down and right a little, and lift the right mouse button. For some reason, Mozilla has duplicated this behavior on Linux but not on Windows.

Alright, now how do you switch tabs using the keyboard?

Ctrl+pgup, Ctrl+pgdn.

I would have expected Ctrl-Tab to do it, but it doesn't work...

Ctrl+tab has traditionally been used for "switch between frames and the url bar" by web browsers and "switch tabs" by tabbed dialogs. See bug 114974 and the linked bugs for some heated controversy on the subject of what Ctrl+tab should do in the tabbed browser.

I'm a member of the "that's what windows are for" camp. That is, I think the tabbed-browser feature is an unnecessary duplication of what window managers do, a waste of screen space, and a waste of keyboard shortcuts. Thus, I sided with keeping Ctrl+tab for switching frames. I could see a compromise in which Ctrl+tab does both, since then it would have its old behavior in the case where you only have one tab open.

What I don't want to see is for this to be turned into an argument for full keyboard configurability. I like being able to sit down at my friend's computer without having to worry about them having completely different keybindings than I do, and I don't want that to change.

Alright, now how do you switch tabs using the keyboard?

Ctrl+pgup, Ctrl+pgdn.

I would have expected Ctrl-Tab to do it, but it doesn't work...

Ctrl+tab has traditionally been used for "switch between frames and the url bar" by web browsers and "switch tabs" by tabbed dialogs. See bug 114974 and the linked bugs for some heated controversy on the subject of what Ctrl+tab should do in the tabbed browser.

I'm a member of the "that's what windows are for" camp. That is, I think the tabbed-browser feature is an unnecessary duplication of what window managers do, a waste of screen space, and a waste of keyboard shortcuts. Thus, I sided with keeping Ctrl+tab for switching frames. I could see a compromise in which Ctrl+tab does both, since then it would have its old behavior in the case where you only have one tab open.

What I don't want to see is for this to be turned into an argument for full keyboard configurability. I like being able to sit down at my friend's computer without having to worry about them having completely different keybindings than I do, and I don't want that to change.

It sounds like if Mozilla could send and receive mail through an Exchange server directly without using IMAP, you could use Mozilla mail. Could someone who knows more about this please enter a bug on the MailNews component?

Here's the bug list for text editor bugs.

Here are the buglists so you can vote for the bugs and add useful comments:

Roaming access
LDAP
Composer

I don't know what the similar pages button is or what refrech bookmakes should do.

Here are the buglists so you can vote for the bugs and add useful comments:

Roaming access
LDAP
Composer

I don't know what the similar pages button is or what refrech bookmakes should do.

Here are the buglists so you can vote for the bugs and add useful comments:

Roaming access
LDAP
Composer

I don't know what the similar pages button is or what refrech bookmakes should do.

After reading Bug 18808 (wow! it's long), I found Bug 110535 which relates to providing an implementation.

If anybody else believes in this feature, please vote on it:
Bug 18808
Bug 110535

After reading Bug 18808 (wow! it's long), I found Bug 110535 which relates to providing an implementation.

If anybody else believes in this feature, please vote on it:
Bug 18808
Bug 110535

After reading Bug 18808 (wow! it's long), I found Bug 110535 which relates to providing an implementation.

If anybody else believes in this feature, please vote on it:
Bug 18808
Bug 110535

Window cloning is a great idea. It's covered by Bug 18808.
Better integration with Outlook would be good, but I'd rather use Mozilla instead of Outlook. What features of Outlook would you need?

Window cloning is a great idea. It's covered by Bug 18808.
Better integration with Outlook would be good, but I'd rather use Mozilla instead of Outlook. What features of Outlook would you need?

Is it possible that IE and Netscape are trying to change the standard rahter than using the standard?

It used to be like that (think of horrors like 'frames' and 'font'). These days it is more the other way around; when the spec is thought out and published, there is usually no conforming implementation yet.

This is a Good Thing (TM), because it creates a much cleaner specification. Take a look at the XHTML Strict specification, and you'll see that it has become much cleaner. Some of the old 'cruft' is retained in the Transitional/Frameset DTD's, but the Strict version is nice, clean and simple.

The W3C has done a good job removing the presentational aspects out of the HTML spec and into CSS. Mozilla follows the spec quite closely, in fact so closely that they sometimes get into a heated discussion with web-developers who don't understand the CSS2 spec.(for instance, this 'little' gem http://bugzilla.mozilla.org/show_bug.cgi?id=22274)

43015
Vote away....

Here are the bug numbers:
Bug 43015 for attaching multiple files with the File dialog
Bug 69528 for attaching multiple files with drag-and-drop

Here are the bug numbers:
Bug 43015 for attaching multiple files with the File dialog
Bug 69528 for attaching multiple files with drag-and-drop

Anyway, what I want to do is run linux on my k6-2 333 or heaven forbid my p1-100 and still be able to browse the web.

This is what I like the most about open source software; the diversity that is a natural consequence of the open-source model has resulted in a number of browsers:

• Mozilla
• Galeon
• Konqueror
• SkipStone

There are also some proprietary browsers:

• Netscape. All of the browsers can be freely downloaded, and Netscape Communicator will work fine on the Pentium 100 machine.
• Opera

- Sam

My one compliant is [begin rant] that underlining of bold text still doesn't work correctly. There are so many obvious test cases for this, including Slashdot and Mozilla's BugZilla itself.

This bug has seemingly been ignored for the past two and a half years, with no plans of fixing it anytime soon (or before 1.0). Please, please, vote for bug 1777---or better yet, fix it if you know how!

Shouldn't an open source web browser be able to display Slashdot correctly? [end rant]

My one compliant is [begin rant] that underlining of bold text still doesn't work correctly. There are so many obvious test cases for this, including Slashdot and Mozilla's BugZilla itself.

This bug has seemingly been ignored for the past two and a half years, with no plans of fixing it anytime soon (or before 1.0). Please, please, vote for bug 1777---or better yet, fix it if you know how!

Shouldn't an open source web browser be able to display Slashdot correctly? [end rant]

The more I hear " IE is better because MS are cheating" without proof

What IE gains in performance, it loses slightly in conformance. IE bends the rules of HTML by not always properly initializing every iframe page's DOM. Speed-conformance tradeoffs that the user can't set are nothing new in the world of proprietary software; see also the Quack 3 incident.

I switched to Linux as my primary OS a few months ago, and I haven't looked back. I find I don't miss Windows a bit, and I'm happy with my Slackware/AfterStep setup.

I use Mozilla as my primary browser (Nightly builds), and I find that it has gotten much better than it used to be. Bug reports hit Bugzilla, and are usually updated and/or assigned the same day. Their system is really great.

Sure, the browser has a few annoying things. Text boxes STILL don't behave properly, opening a new window in any shape or form (Ctrl+N, or a javascript function) takes *forever*, and other little things. Overall though, Mozilla is a pretty decent browser. Gecko is a great rendering engine, and tabbed browsing is just totally fucking fantastic.

Once the speed issues are addressed and the behaivior kinks are worked out, that's when 1.0 should hit.

Unfortunately, I find that I do miss the incredible speed of IE 5x. Say what you will about IE security, but it's still the best browser out there. Fortunately, I can happily make that trade-off as a Linux desktop user.

XPCOM isn't directly compatible with MSCOM, but it is damn close, and I don't think it is far fetched to see complete interaction between XPCOM and MSCOM.

Care to back this up, say with some examples of projects where large numbers of people swarmed over the code and still couldn't fix the bugs?

Mozilla, anyone?

C-X C-S
Three years. Still buggy, still slow, still no release. But hey, we have themes!

Go download mozilla 9.8 and go to Edit/Preferences/Privacy and Security. it fixes popups, allows for cookie rejection, add blocking, image blocking by site...it's what you need. And it handles lousy HTML pretty well too.

Yes, this is a key area where I think de Icaza has a problem. He's clearly planning on implementing Winforms (I checked on the Mono site) and those are not part of the ECMA C#/CLI/CLR spec. Microsoft will not permit those classes to be cloned - its already dropped strong hints about it.

Hmm... If I was Miguel I would take a different route to avoid this problem - I would create a UIML based tool that would generate code for both Winforms (on Windows based platforms) and Mozilla XUL for everywhere else (and your little Windows too, deary!) Plus UIML is a handy intermediate form for other forms-based UI platforms, such as Java Swing and HTML. Just standardize on Javascript for the local scripting needs...

Personally I think UIML is a damn good stab at creating a standardized common syntax for cross-platform UI design. Given a couple of revisions to add scripting capability and a decent event model it would rule (if enough tools supported it). And I like this kind of general approach a lot more than I like the idea of emulating MS Winforms.

Jack William Bell

Now, we intend to use the name Mozilla as the generic term referring to internet client software developed through our open source project.

So, Mozilla is a set of technologies, but not a specific (in biologic terms, Mozilla is a genus; a particular product is a species).

The original roadmap recorded the momentous decision in October 1998 to reset the Mozilla project around the new layout engine (now called Gecko), a cross-platform front end (XPFE), now several XP Apps built on an XP Toolkit), and a scriptable components architecture (XPCOM and XPConnect).

Now, we intend to use the name Mozilla as the generic term referring to internet client software developed through our open source project.

So, Mozilla is a set of technologies, but not a specific (in biologic terms, Mozilla is a genus; a particular product is a species).

The original roadmap recorded the momentous decision in October 1998 to reset the Mozilla project around the new layout engine (now called Gecko), a cross-platform front end (XPFE), now several XP Apps built on an XP Toolkit), and a scriptable components architecture (XPCOM and XPConnect).

Now, we intend to use the name Mozilla as the generic term referring to internet client software developed through our open source project.

So, Mozilla is a set of technologies, but not a specific (in biologic terms, Mozilla is a genus; a particular product is a species).

The original roadmap recorded the momentous decision in October 1998 to reset the Mozilla project around the new layout engine (now called Gecko), a cross-platform front end (XPFE), now several XP Apps built on an XP Toolkit), and a scriptable components architecture (XPCOM and XPConnect).

I'd still like to see antialiasing of the quality found in Konqueror though.

Does Moz reload the page when you want to view the source now?

Yes, it still does. See bug 55583 for details.

I’d better answer this one, as I started the discussion. Thanks, afidel, for raising the web standards issue.

Actually, I wasn’t referring to how Mozilla renders particular websites. I think web standards are important, and I’m broadly in favour of the Browser Upgrade initiative. The sooner we can banish table layout hacks (and worse) the better. Mozilla is a website developer’s dream from that point of view.

My issue is with the unsatisfactory way that Mozilla renders certain fonts and certain glyphs. I refer in particular to bug number 86563, which is about the incorrect rendering of ’, ” and „. I had this problem on my system (MDK 8.1). In this context, “properly” means displaying the correct glyph— fairly fundamental really. There was a great deal of discussion of the problem on bugzilla, which finally cumulated in it being closed as “WORKSFORME”. Except that it doesn’t. You really need to read the full discussion.

(I take back my earlier remark about Helvetica being substituted for certain truetype fonts. It appears that it may only affect symbol-type fonts, which are not really within the web standards.)

I’d still like to see antialiasing of the quality found in Konqueror though.

P.S. My own workaround was to completely remove support for iso8859-13 character sets from my system by editing some of the FreeX86 configuration files. Ok for me, as I don’t need the Baltic Rim characters set. But it is not the kind of thing you can expect Joe User to know how to do. It took me several days to figure it out.

file a RRE.

If more people contributed an improvement instead of complaining, there would be less money flowing into the stockpiles of corps like MS and more money spent hiring people to solve NEW problems instead of paying a for a proprietary solution OVER and OVER and OVER...

From the bug 112564:

According to RFC 2616, "Pragma: no-cache" and "Cache-Control: no-cache" SHOULD NOT affect the back/forward buttons.

Gahhh this is the crap that really turns me off from Mozilla. It seems like the project is dead set on reinventing everything.

The crap that really turns me off about Mozilla is the arm chair quarterbacks who mouth off without a clue. You obviously didn't even read the freaking bug report.

You might be particularly interested in the attachment to comment 23 which is an email from the author of Aspell/Pspell which gives a gap analysis of the various open source spell checkers.

In fact, it appears that Mozilla and Abiword have some alignment in goals for making a library based spell checker, so far from the picture of "reinventing everything" that you paint, this is actually an example of synergy between diverse projects that exemplifies open source development code sharing.

Gahhh this is the crap that really turns me off from Mozilla. It seems like the project is dead set on reinventing everything.

The crap that really turns me off about Mozilla is the arm chair quarterbacks who mouth off without a clue. You obviously didn't even read the freaking bug report.

You might be particularly interested in the attachment to comment 23 which is an email from the author of Aspell/Pspell which gives a gap analysis of the various open source spell checkers.

In fact, it appears that Mozilla and Abiword have some alignment in goals for making a library based spell checker, so far from the picture of "reinventing everything" that you paint, this is actually an example of synergy between diverse projects that exemplifies open source development code sharing.

The ability to put newsgroups into folders is requested as part of bug 60764. If you want that feature in Mozilla, go vote for it.

Mozilla has been my primary browser ever since the anti-popup feature became a standard preference. There's only one bug left before I can declare it to be the "best" browser for OS X -- blocking images on a site-by-site basis gets hung up by Amazon ad banners.

Also, note that "native-looking" widgets are not the same as true native widgets. Mozilla's jellybeans are less responsive than real ones, and they don't "gray out" when you background the window. On the bright side, you can vote for it to be fixed.

Macromedia plug-ins are cool, they still don't seem as fast

That's because Macromedia's plugins aren't as fast on Mac as they are on Win. It gets discussed all the time on the forums.macromedia.com NNTP server. Macromedia doesn't bother to optimize their Mac code, and probably won't unless the cost/benefit ratio (for them, not for us) is good enough.

Mozilla has been my primary browser ever since the anti-popup feature became a standard preference. There's only one bug left before I can declare it to be the "best" browser for OS X -- blocking images on a site-by-site basis gets hung up by Amazon ad banners.

Also, note that "native-looking" widgets are not the same as true native widgets. Mozilla's jellybeans are less responsive than real ones, and they don't "gray out" when you background the window. On the bright side, you can vote for it to be fixed.

Macromedia plug-ins are cool, they still don't seem as fast

That's because Macromedia's plugins aren't as fast on Mac as they are on Win. It gets discussed all the time on the forums.macromedia.com NNTP server. Macromedia doesn't bother to optimize their Mac code, and probably won't unless the cost/benefit ratio (for them, not for us) is good enough.

If you have opinions about what features should be added and what the priority of Mozilla developers should be, I suggest that you use Bugzilla to communicate directly to Mozilla developers. You can enter requests for enhancement, bug reports, and vote for the issues that you think should have priority. I'm sure doing that will be far more effective than posting your opinions here!

several very old linux printing bugs were re-targeted for 1.1 or 1.2

Mozilla is slow with a large Slashdot page probably because it's a large table, and Mozilla is slow on large tables. See bugs 74888 and 54542.

Mozilla is slow with a large Slashdot page probably because it's a large table, and Mozilla is slow on large tables. See bugs 74888 and 54542.

That is reported as bug 105619, and it's being worked on right now. It's planned to be fixed for 0.9.9.