Slashdot Mirror


Mozilla 1.2 Beta Released

nberardi writes "Mozilla 1.2 Beta is out. Typeahead now works on Mac and Java now works on Jaguar. On Linux, the classic theme now picks up GTK native theme. See the release notes for more info."

109 of 448 comments (clear)

  1. If only... by sl3xd · · Score: 4, Interesting

    If only there was a theme that used the OS native widgets, without the ugly 'classic' icons...

    --
    -- Sometimes you have to turn the lights off in order to see.
    1. Re:If only... by Anonymous Coward · · Score: 5, Informative

      Help yourself. Unpack the classic theme (classic.jar is a zip archive) and replace the icons with your own.

    2. Re:If only... by unixmaster · · Score: 5, Informative

      It does actually , uses GTK on Linux and native widgets on Mac/Windows when classic theme is selected.

      --
      Never learn by your mistakes, if you do you may never dare to try again
    3. Re:If only... by evbergen · · Score: 5, Interesting

      Sadly, there isn't even any such thing as OS native widgets on Unix. Every toolkit has its own, and every application gets to choose its own toolkit.

      We need an X protocol that works at widget level instead of pixel level. It'd be great if we could design /that/, together with a good widget definition language, and to stop reinventing the OS in huge toolkits that even provide timers and I/O and mistreat X as a dumb framebuffer backend.

      Client-side rendering, high-level application frameworks, *yuck*. Provide your high-level GUI stuff through an IPC channel and get out of the way. Let me have my own main loop back. Thank you.

      --
      All generalizations are false, including this one. (Mark Twain)
    4. Re:If only... by ichimunki · · Score: 5, Informative

      Personally, I'm anxious for the day it uses gtk-2.0 instead of gtk-1.4. I tried it with gtk2 and couldn't do any cutting/pasting (known bug, already in Bugzilla, I believe). Other than that it was great-- they're very close. Even better: once it is stable on gtk2, then Galeon 2 is ready to go. Either way, hats off to all Mozilla coders, Mozilla is a great browser and gets better all the time.

      --
      I do not have a signature
    5. Re:If only... by ncc74656 · · Score: 3, Informative
      If only there was a theme that used the OS native widgets, without the ugly 'classic' icons...

      Phoenix looks like it's going that way. I would be using it right now instead of the new Mozilla beta, but Phoenix doesn't let you disable third-party cookies (you can't check the checkbox that controls third-party cookies, at least not under Win2K). Once they get that fixed, though, I'll more than likely switch over to Phoenix. All I really want is a browser. I use Mutt on my home Linux server for mail, so I don't need a mail client, and I use text editors (such as JOE or Notepad) for editing HTML and CSS.

      The thing that bugs me right now about Mozilla 1.2b is that the Pinball theme doesn't work (it didn't work in Phoenix, either, and for the same reason...it hasn't been updated). Classic is ghey (as you noted), and Modern isn't much better. Pinball ought to be the default. :-)

      --
      20 January 2017: the End of an Error.
    6. Re:If only... by uhoreg · · Score: 4, Informative

      It only uses GTK/etc. to *draw* the widgets. It doesn't use actual GTK/etc. widgets.

      --

      To get something done, a committee should consist of no more than three persons, two of them absent.

  2. pinstripe theme by Anonymous+Cowrad · · Score: 5, Informative

    Note that if you're using the pinstripe theme, you've got to use the one made for nightlies.

    I don't know why.

    First thing I noticed.

    --

    --
    pants ahoy
    1. Re:pinstripe theme by Anonymous+Cowrad · · Score: 3, Funny

      The funniest part is that I am a homosexual Macintosh user.

      I don't know why.

      First thing I noticed was that I really liked men. Then I noticed that I really liked Macintoshes.

      --

      --
      pants ahoy
  3. Link prefetching by Rhubarb+Crumble · · Score: 5, Interesting
    check this out: Link prefetching

    seems to mean that if you're reading page 1 of a multi-page article, page 2 will be loaded in the background. nice!

    1. Re:Link prefetching by Anonymous Coward · · Score: 5, Funny

      And if your reading a page with links you dont want to click, lets say to a picture of a man stretching his balloon knot open, then they'll be cached for you and swallow up more and more system resources. nice!

    2. Re:Link prefetching by PEdelman · · Score: 3, Insightful

      This sounds cool, but it looks like the page author has to specify what has to be pre-fetched. Due to the relatively small marker-share of mozilla, there will probably be few sites which implement this feature. Too bad, because it looks like a nice feature to me.

      --
      Like science? Comics? Wicked...
      Funny By Nature
    3. Re:Link prefetching by Jugalator · · Score: 5, Informative

      ... provided the page is written for link prefetching explicitly. It doesn't mean you can go to a site like Google News and it will start loading the various articles in the background.

      Perhaps that's good, although I'd like to see an option where you can choose to apply the feature to all links leading to HTML pages. This combined with a customizable maximum bandwidth restriction for the prefetching would be nice.

      --
      Beware: In C++, your friends can see your privates!
    4. Re:Link prefetching by Rhubarb+Crumble · · Score: 5, Interesting
      And if your reading a page with links you dont want to click, lets say to a picture of a man stretching his balloon knot open, then they'll be cached for you and swallow up more and more system resources. nice!

      That's a fair point - there is potential for abusem since the web page decides which "hints" to issue. Hopefully it'll eventually have an "enable prefetching for these sites"-type access control, similarly to the way it's done with cookies. Or a limit on the amount of data to prefetch.

    5. Re:Link prefetching by Steveftoth · · Score: 3, Interesting

      What about a button to manually prefetch links on pages that you like? Not all pages should have their pages prefetched. For the advanced users, for the normal people it should be auto -on - or off.

    6. Re:Link prefetching by pubjames · · Score: 4, Funny

      Perhaps that's good, although I'd like to see an option where you can choose to apply the feature to all links leading to HTML pages.

      What would be great is if it could recognise if a page is of thumbnail images, and then automatically download the linked images. It would make browsing porn much quicker.

    7. Re:Link prefetching by trollercoaster · · Score: 5, Funny

      Cool, this could lead to preslashdoting.

      --

      Slashdot, come for the goatse, stay for the trolls.

    8. Re:Link prefetching by GeorgePBurdell · · Score: 3, Insightful

      Seems like there's a lot of potential for abuse with this, especially given that right now you have to manually edit the prefs file to turn it off. What's to stop a page from tagging a really huge file, hosted on someone *else's* server as a "prefetch" item. Everyone who goes to page A starts "prefetching" from page B in the background - enough people do this and you've got a DOS going on.

      Even if that scenario is not likely, I think it's still an odd choice for Mozilla - the philosophy behind the idea seems to be "the browser knows best and will think for you behind the scenes." On the one hand that sounds great: the browser will anticipate my next move. On the other, that doesn't sound so great... My cable modem starts blinking when I think I'm not grabbing anything and I get suspicious.

    9. Re:Link prefetching by JanneM · · Score: 5, Informative

      http://leech.mozdev.org/

      --
      Trust the Computer. The Computer is your friend.
    10. Re:Link prefetching by Eimi+Metamorphoumai · · Score: 5, Interesting

      How is this worse than just embedding the image into the webpage, possibly with height=0 width=0? When you go to a webpage you already pretty much give it carte blanche to download what it likes; this doesn't seem very different.

      --

      Visit me on #weirdness on the Galaxynet.

    11. Re:Link prefetching by Iamthefallen · · Score: 5, Funny

      I still cherish the days with modem when I could see the goatse.cx pic load before my eyes and go away before it was done, now with DSL it's instant, and you think this is good?!


      :)
      --
      Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
    12. Re:Link prefetching by roca · · Score: 3, Informative

      > What's to stop a page from tagging a really huge
      > file, hosted on someone *else's* server as a
      > "prefetch" item.

      You can already do this by loading someone else's page into a hidden IFRAME.

      Nothing new here. Move along.

    13. Re:Link prefetching by ObligatoryUserName · · Score: 3, Insightful

      How about limiting the prefetching to pages in the same domain as the page doing the prefetching. Perhaps you could explicitly allow addtional domains for prefetching in the head of the document.

    14. Re:Link prefetching by Ed+Avis · · Score: 5, Interesting

      The style of web browsing I use is to load all the links I want to read in new windows by clicking on them with the middle button. Then they can be loading in the background while I read the first part of the article. It forms a kind of queue of pages to read, so when I've finished reading the first page I just close that window and go on to the next (which is ready instantly). The result is up to a hundred browser windows open at once - but I know that I'm not the only person who browses like this. Of course, it helps to have a browser which can open lots of windows without thrashing and slowing the machine to a crawl (like Dillo) or one that has tabbed browsing.

      This style of following links can also work well with offline browsing and a proxy server designed for offline use like WWWOFFLE. If you go online briefly and click on all the links you want to load, the proxy remembers to download them. Then a few minutes later you can go online again and all the pages will be loaded ASAP. Once they've loaded you can disconnect again and continue browsing. This makes the most sense for people whose internet access is metered (hmm, I wonder if something like this could work for palmtops).

      But what I'd really like to see in a browser is an explicit 'to read' queue. When you click on a link with the middle button, it doesn't immediately open in a new window or tab but instead is added to the queue and starts downloading in the background. On the browser's toolbar there is a 'next page' button which goes to the next URL you have marked for reading.

      Automatic prefetching of all links from a page, la wget -r, would be crazy for many heavily-linked sites. But you could have heuristics for it or specify particular sites where the link following should be more aggressive.

      --
      -- Ed Avis ed@membled.com
    15. Re:Link prefetching by j7953 · · Score: 5, Insightful
      Perhaps that's good, although I'd like to see an option where you can choose to apply the feature to all links leading to HTML pages.

      No, that would be a very bad idea. Just right now in the navigation menu of the Slashdot page I'm viewing ("Post Comment"), there are 17 navigation links, plus the category links, etc. You cannot tell me that you'll be following all of those 17 links. Web sites (and probably ISPs as well) would not like such a feature due to the increased bandwidth costs they'd have to account for.

      Also note that e.g. this page has a "log out" link that I really do not want to be automatically prefetched for obvious reasons. Granted, it contains a query-string so Mozilla would not prefetch it anyway, but I imagine there will also be web sites that have log out links without query strings in the URL. And there are lots of other actions that might be associated with following a link (think prefetched one-click-shopping).

      The HTTP standard (RFC2616) states that "In particular, the convention has been established that the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered 'safe'", and if there are side effects, "the user did not request the side-effects, so therefore cannot be held accountable for them", but I wouldn't trust on web site administrators knowing this.

      --
      Sig (appended to the end of comments I post, 54 chars)
    16. Re:Link prefetching by HiThere · · Score: 3, Informative

      Right. And so you go to /., open an article, and...

      I see a use for a "load in background" click option. That could sometimes be very good. But "load all links"? No. Not even "load all links when selected". There's too much problem with hidden links already.

      (Mind you, as long is Mozilla is the browser of a small minority this wouldn't be too bad. But once people start designing web pages to take advantage of this ... unh unh.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    17. Re:Link prefetching by mpsmps · · Score: 5, Informative

      Embedding an invisible image has a variety of problems.

      1. Relying on obscure side-effects leads to bad code. For example, one could imagine a highly-optimized browser-rendering engine may choose not to read the bits of the image because they won't be visible. It's much better to have an XHTML tag that explicitly expresses the desired semantics and leave it to the presentation tool to properly figure out how to present.

      2. Languages, standards, and practices evolve. For example, if my webages are XML interpreted by XSL stylesheets, do I really want to start embedding browser hints in my XML pages (or have my XSL stylesheet assume a browser is the client)?

      3. How does the browser know not to start prefetching the image before it has loaded the main page? The prefetching FAQ says that prefetching uses an idle test to avoid doing harm. Embedded images can't readily be optimized by an idle test.

    18. Re:Link prefetching by SethJohnson · · Score: 5, Insightful


      Ed,

      If you're using Mozilla, or the recently-released Phoenix (highly recommended), you can also accomplish your browsing style by right-clicking the links and selecting "open in new tab". The other page will open a new tab within your existing window. When you're done reading the current page, you can click on the tab for the other page without having to juggle windows.

      What's nice about Phoenix in this respect is the default behavior is to have the new tab open in the background. I complimented the design team for this on their discussion board and some guy came back and said you can also set this up in Mozilla via the prefreences. It's supposed to be controlled by the checkbox 'Load links in the background'. You can also set middle or right-click to open these tabs in the preferences.

      Seth

    19. Re:Link prefetching by aftk2 · · Score: 3, Informative
      Interesting idea, although it's too bad that, according to the FAQ:
      URLs with a query string are not prefetched.
      This really limits how useful this feature might be. I can imagine reading a multiple page article, and on page one of that article, the link tag prefetches page two while I'm reading page one, for quick access to the next page. Unfortunately, the URLs to most articles on the web contain query strings (a query string is the question mark (?) that preceeds a bunch of variables in a URL.)

      Interesting idea, at least.
      --
      concrete5: a cms made for marketing, but strong enough for geeks.
    20. Re:Link prefetching by zmooc · · Score: 4, Insightful
      Perhaps that's good, although I'd like to see an option where you can choose to apply the feature to all links leading to HTML pages. This combined with a customizable maximum bandwidth restriction for the prefetching would be nice.

      And that, my friend, would be the end of the Internet. How many of the links on a website do you generally click? On slashdot, I think, it would at most be something like 5%. Let's say 5% of the users would enable this feature. Now their browsers start pre-fetching. Since they normally only click at most 5% of the links, preloading all would multiply their bandwith-usage by 20 times. So. Our 5% of the users uses 20 times as much bandwidth as they would without preloading. So the average bandwidth-usage for web-browsing would about double and that's with only 5% of the users having this feature enabled. Bye bye Internet. There's a reason this really simple to implement feature isn't there yet.

      But.... combined with a reasonably large distributed network of caching proxy-servers, pre-fetching might be worth a try.

      --
      0x or or snor perron?!
    21. Re:Link prefetching by Jorrit · · Score: 3, Insightful

      I would turn this off immediatelly even if it works correctly. I have limited bandwidth every month. I only want to load what I need. Not what the server thinks that I need.

      Greetings,

      --
      Project Manager of Crystal Space (http://www.crystalspace3d.org). Support CS at http://tinyurl.com/cb3x4
    22. Re:Link prefetching by Erik+Fish · · Score: 4, Interesting

      Well if there's an enable/disable for prefetching it's sure to be accessable via the best Mozilla plug-in ever!

    23. Re:Link prefetching by arkanes · · Score: 3, Informative

      Off topic but relevent: When you open a new window from within an explorer window, with open link in new window or by hitting ctrl-n, then it's a child window of the original, and dies when the parent does. A totally new IE window, opened by invoking iexplore.exe, is a seperate process. As for why it works exactly like this - I don't know.

  4. GTK.... by GreyWolf3000 · · Score: 4, Informative

    Mozilla's binaries still depend on gtk 1.x, however when compiling from source you can tell it to use gtk2. I don't know how stable that is, though...

    --
    Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
    1. Re:GTK.... by cyco/mico · · Score: 3, Informative

      As it seems, they are not there yet. But there's a patch from the galeon guys, who seem to be working on that too. You can find the respective hints here (galeon2 installation instructions).

  5. Type ahead find is great by fault0 · · Score: 5, Interesting

    Type ahead find is great. Been using it since Moz 1.2 alpha. The neat thing is that you can type a search phrase, and you can search again with ctrl-G. My only suggestion would be to have type ahead and find searches appear in a history combobox in the find window.

  6. Mime Types by nagora · · Score: 4, Insightful
    Have they done anything about adding large numbers of mime types (ie, made it not be a pain in the arse) yet?

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  7. And Blizzard Represents.... by unixmaster · · Score: 5, Informative

    XFT support on Linux! Now we can get cool anti-aliased fonts on Linux!

    You must compile from source with --enable-xft and need fontconfig & xft2 package from www.fontconfig.org and of course freetype2 from www.freetype.org

    Great thnx to Chris Blizzard for this!

    Oh btw now HTML for controls & scrollbars use your native GTK theme widgets when classic theme is chosen.

    --
    Never learn by your mistakes, if you do you may never dare to try again
    1. Re:And Blizzard Represents.... by tempest303 · · Score: 3, Informative

      If you have Red Hat 8, you already have Xft2 and fontconfig installed and working, and Mozilla 1.2-final will ship with Xft2 enabled and (it looks like) GTK2 widgets, too!

      So ideally, with a RH8 rig anyhow, there's really no effort at all. Just wait for the Moz 1.2-final RPMS to come out, install them, and voila! Beautiful font rendering, with no hassle. :-)

  8. Probably a little redundant... by MacOS_Rules · · Score: 5, Informative

    Moz 1.2 works like a champ on my iMac under Jaguar. 1.1 was a little sluggish, but 1.2 seems to have corrected that and then some. Startup times are now nearly as fast as IE 5.2.2, and Moz is and hopefully will continue to be much less crash prone than IE. This is in and of itself amazing, considering it is 1.2 BETA.

    Great job to all who work on this effort. It is much appreciated by many in the computing field.
    Cheers!

    --
    If a man's character is to be abused there's nobody like a relative to do the business. -Thackeray, William
  9. Fast releases by koh · · Score: 4, Informative

    moz development has been considered sluggish by many a few months ago... now that they have the infrastructure right, they do release early and often. Nice :)

    Too bad I'm still stuck to 1.0.1-r1 on my gentoo distro... ;)

    --
    Karma cannot be described by words alone.
    1. Re:Fast releases by rizzo · · Score: 5, Informative

      Why are you stuck to 1.0.1-r1? Just unmask 1.1 and you'll get 1.1. You can copy the 1.1 ebuild and make a 1.2a ebuild. As soon as 1.2b source is released I'll be submitting a 1.2b ebuild.

      You just need to unmask it by commenting out any mozilla lines in /usr/portage/profiles/package.mask. The gentoo people mask apps to create an aura of stability.

      --

      "More organs means more human." - Zim

  10. Type-ahead Find by RPoet · · Score: 5, Informative

    1.2 is really worth installing just for the Type-Ahead Find feature. It's one of those "how did I ever manage without it" features, and a punch in the stomach of anyone who says free software isn't innovating. This feature almost obsoletes the use of a mouse while surfing (well, almost). You see a link you want to follow, called "Click here". So you type "cl", and that link is marked. Now press enter to follow it. So simple, yet so efficient.

    --
    "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
    1. Re:Type-ahead Find by Anonymous+Cowrad · · Score: 3, Interesting

      Typeahead rocks my socks, but the Mozilla team didn't invent it. Internet Explorer for the Mac has had this for quite some time.

      A trivial point, maybe, and I certainly agree that Mozilla is innovative, but they weren't first in this case.

      --

      --
      pants ahoy
    2. Re:Type-ahead Find by Loligo · · Score: 3, Informative

      >Typeahead rocks my socks, but the Mozilla team
      >didn't invent it. Internet Explorer for the Mac
      >has had this for quite some time.

      IE has had "fill in the box" type-ahead completion for years, but it sounds like what he's describing is different.

      As an example, say you wanted to reply to this article. Instead of clicking on "Reply to This", you'd type enough of "reply" to jump the highlight to the link in the active window.

      Not exactly the same thing. Not even remotely the same thing, even.

      -l

    3. Re:Type-ahead Find by Corvaith · · Score: 4, Insightful

      It sounds good, sure. But, I can't be the only person out there for whom it's more of an irritant than a feature. On long pages, if you accidentally type something without focusing on, say, the form box... then it'll scroll you right down to the link it thinks you want.

      I'm therefore waiting expectantly for the feature that lets you turn this *off*. I'm sure it's nice for some people, but if you don't want it, being forced to have it is a pain. If there /is/ a place to disable it... it's definitely not anywhere visible.

    4. Re:Type-ahead Find by BZ · · Score: 3, Informative

      IE/Mac and IE/Windows have nothing to do with each other. IE/Mac has typeahead find and has for a long time (and is generally a much better browser than IE/Windows).

  11. Great News by MercuryWings · · Score: 3, Insightful
    I've been using Mozilla since the 0.6 beta days and count my blessings on a regular basis. It's nice to see they've added the GTK support - now it'll not only be a linux app, but will have the look and feel that is consistent with other GTK-based apps. That part tended to be irritating - didn't feel like GTK, didn't feel like KDE, felt like one of those 'let's design the entire interface to our own personal tastes' programs that one finds far too often on that 'other' OS.

    One question I have though - does it support GTK 1.2, or 2.0 (including the anti-aliasing fonts feature)?

    --
    Karma: Shagadelic (mostly affected by those tight knickers - yeah baby, yeah!)
  12. Beware of GTK themes by Psiren · · Score: 4, Informative

    Some of the themes I tried with GTK and Mozilla this morning crashed Mozilla on startup. Others were okay. I guess there are still a few bugs to work out there.

    1. Re:Beware of GTK themes by l0ungeb0y · · Score: 4, Insightful

      Well of course, that's why I"just say NO" to themes. OS themes, browser themes, any theme at all besides the defaults they come with.

      Not because I don't like themes, but they are version specific for each release... and having to drop/change themes with each new release seems like more of a pain in the ass than it's worth.

      Maybe someday in the not so distant future, they will build a theme utility that will adjust theme graphics to match the current GUI... but I doubt it.

  13. Link Pre-fetching is a baaad idea... by Bonker · · Score: 5, Insightful

    Remember all those offline browsers and 'modem accelerators' that sucked up your modem bandwidth by downloading contantly, spidering every link on every page you visited?

    While the Mozilla project is an incredible piece of work, I have to question this feature. It appears that they've designed it so that a page designer or webmaster decides what is appropriate for prefetching or not. Still, if used inappropriately, this feature could lead to more information being transmitted across the internet that is either discarded or unwanted. In a worst-case scenario, an inexperienced web designer might routinely run into his bandwidth cap or unintentionally force users who have bandwidth caps to exhaust their allowance.

    If you can only download 3GB per month over your cable modem, do you really want the designer of a page deciding that your browser needs to spend time downloading ads or useless images?

    For some people, this could be really useful. For others, it could be a real pain. Team-Moz, if you have any consideration at all, please adjust the default configuration of Mozilla so that this feature is turned OFF.

    --
    The next Slashdot story will be ready soon, but subscribers can beat the rush and slashdot the links early!
    1. Re:Link Pre-fetching is a baaad idea... by Anonymous Coward · · Score: 3, Insightful

      It requires the web-"designer" to hint, what pages to prefetch.
      Since, the employer of named designer pays for the bandwith, it surely will be used only at adequate places (Cost/Benefit).

    2. Re:Link Pre-fetching is a baaad idea... by Tack · · Score: 3, Insightful
      So far as I can tell from the prefetching FAQ, there's nothing built into this to keep it from, say, prefetching banner ads, which are very typically hosted on a different server than 'real' web content. Thus, the designer of a web page can force your browser to download ads for his benefit and without any cost to him.

      This isn't an inherent problem with prefetching. You can do this with regular HTML now. Consider:

      • <img src="bigbaduglybanner.gif" width=0 height=0>

      Or, you might use CSS and set display:none (although I'm not sure if the browser will fetch the image in that case, but some might). Or, if you want to cause the client to load an html, use an iframe also with 0x0 dimensions. You can see there are ways to do exactly what you're worried about right now, in all browsers, without prefetching.

      Jason.

    3. Re:Link Pre-fetching is a baaad idea... by srmalloy · · Score: 4, Informative
      Read the specs, please. It doesn't prefetch ALL links, only those explicitly set as such in the web page. Which, as far as I know, accounts for exactly zero web pages in existence today.

      However, it only takes a minimal amount of underhandedness to start screwing people over. Banner ads are everywhere, and a large percentage of them are implemented by having a site drop in a block of code that references a CGI script on a server run by the company managing the distribution of banner ads. If the company running the banner distribution server decides that having their advertising clients' linked pages load faster is a valuable feature, all they would have to do is add the prefetch code to the output of their CGI script -- both Mozilla and IE will happily process a META tag in the body of an HTML document, even though by the specification, a META tag should occur only inside the HEAD tag block. So the user's network connection bandwidth would get usurped to prefetch the advertiser's web page, even if the user has no intention of clicking on the banner ad.
    4. Re:Link Pre-fetching is a baaad idea... by roca · · Score: 3, Informative

      This point has been made elsewhere but it needs to be reiterated:

      A Web page can already force you to download arbitrary files. For example, it can include a hidden IFRAME linked to some URL. This prefetching feature does not allow Web sites to do anything nefarious that they couldn't do before.

      In fact, this prefetching feature is strictly better for users than hidden IFRAMEs or similar, mainly because prefetches are given bottom priority so they never interfere with your other Mozilla network activity.

  14. Mac OS X Users should ignore Mozilla by toupsie · · Score: 4, Interesting
    Of course, lets heap praise on the Mozilla developers for their hard work. Without it, we would not have the best browser for Mac OS X, Chimera. Mozilla is a full of bloat that Mac OS X users don't need. We already have iChat, Address Book, Mail and iSync built into our beloved UNIX operating system. So a lot of Mozilla's functionality is not needed -- newsgroups are nice but we have better alternatives. Chimera is what Mac OS X users really need. Its blazingly fast, supports standards and gives Microsoft Internet Explorer something to aspire too. Poor Omniweb never knew what hit them.

    Get the latest nightly build here!

    --
    Strange women lying in ponds distributing swords is no basis for a system of government.
    1. Re:Mac OS X Users should ignore Mozilla by analog_line · · Score: 4, Funny

      The next time I read someone in all seriousness using the term "blazingly fast" the baby seal gets it.

      Chimera's great, I use it, but it has zero speed advantage over OmniWeb. Nil. Goosegg. And in my opinion, OmniWeb looks better.

  15. Moz versus IE by 0x0d0a · · Score: 5, Interesting

    With the two rapid releases of Phoenix and Mozilla, with Netscape (the browser) being pushed by AOL, and with Chimera popular on the Mac, IE may have more users, but aside from being more stable and configurable, Moz is now steadily heading for a 1-1 user:browser ratio. Hopefully, this will result in an extremely customized browsing experience.

    1. Re:Moz versus IE by azzy · · Score: 3, Funny

      Moz has gone beyond 1-1 user ratio. I have several versions of Mozilla installed.. it's about 1-3 user:browser ratio :)

  16. Question about typeaheadfind by Mr_Silver · · Score: 5, Insightful
    Type Ahead Find is currently part of the default install. To turn it off, use:

    user_pref ("accessibility.typeaheadfind", false);

    Or, to remove it completely, find all files in your installation subdirectories that match *typeaheadfind*, and delete those files.

    Whilst it's great that stuff like this is being implemented, is anyone actually working on making a point and click interface to active/deactivate functionality rather than having to get users to resort to deleting or editing files?

    If it's already there, for gods sake, why on earth do they insist on giving you these contrived instructions on how to deactivate it?

    If the aim of Mozilla is to get a sizeable userbase and encourage developers to avoid writing for IE only then the first thing they should do is make it easy for the common computer user to do this sort of stuff without having to resort to editing text files.

    Once they have to do that, then you lose and IE will continue to reign.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
    1. Re:Question about typeaheadfind by Kidbro · · Score: 4, Insightful

      If the aim of Mozilla is to get a sizeable userbase and encourage developers to avoid writing for IE only then the first thing they should do is make it easy for the common computer user to do this sort of stuff without having to resort to editing text files.

      Good point, but remember that this is the first time we see this feature. I wouldn't expect it to be finished yet (and if you can't live with non finished stuff - don't run betas). I can't speak for the Mozilla team of course, but being a GUI Application developer, I can tell that sometimes you choose between implementing a feature and providing a rough interface to it, or not implementing it at all - as providing a nice "user friendly" (whatever that means) interface would take twice, three or a hundred times longer.
      I would expect there to be a nice point and click interface by the time this leaves beta...

      Moral of the story: Patience :)

    2. Re:Question about typeaheadfind by pmz · · Score: 3, Informative

      ...is anyone actually working on making a point and click interface to active/deactivate functionality... ...why on earth do they insist on giving you these contrived instructions on how to deactivate it?

      Well, why don't you type "about:config" in your Mozilla location bar. By your argument, there should be pointy-clicky stuff for all 1100+ configurable parameters in Mozilla. Implement that, and Mozilla turns into something like Microsoft Word or the Windows Control Panel (shit everywhere piled under menu upon menu).

      Trust me, it is a good thing that Mozilla doesn't put everything in the GUI. Be thankful that the configuration is in a plain text file and not some binary GUI database or, worse, the Registry.

  17. Re:Hooray! by Lussarn · · Score: 4, Informative

    I saw the link prefetching feature and thought oh no, there goes our server bandwith. But after reading the FAQ it seems that it's the author of the page that selects what's prefetched and whats not.

    Nice feature.

  18. GTK on Phoenix by distributed.karma · · Score: 3, Informative

    Since Phoenix (my default browser, as Mozilla is a hog) is built from the Mozilla tree, its latest nightly also has the GTK look. Time to rpm -e galeon.

    --

    --
    If you moderate this, then your children will be next.

  19. Link prefetching abuse? by billybob · · Score: 4, Insightful

    So what happens when the greedy web master decides to add "rel=prefetch" to his tags for banners?

    --
    Joseph?
    1. Re:Link prefetching abuse? by sporty · · Score: 4, Interesting

      It's something mozilla is missing, blocking based off of filters. It'd be nice if I can say, fine, take everything on this server except .swf files.

      --

      -
      ping -f 255.255.255.255 # if only

    2. Re:Link prefetching abuse? by roca · · Score: 4, Informative

      The greedy web master doesn't get a cent, because Mozilla doesn't send a referrer for prefetches.

      BTW your greedy web master can already just include a hidden IFRAME with SRC pointing to the click-through, which WILL send a referrer, so Mozilla's prefetching adds no new danger here.

  20. And Emacs had it forever by Per+Abrahamsen · · Score: 5, Informative

    In fact, the bugzilla item which typeahead find sprang from was named "implement typeahead find (like Emacs isearch)".

  21. It only prefetches _one_ item... by Per+Abrahamsen · · Score: 5, Informative

    and only if explicitly specified, and if nothing else is going on (i.e. if you have an active download, prefetch is disbabled).

  22. Re:Xt by roukounas · · Score: 3, Informative
    XT??? HELLO???

    everyone forgot about Xt which works beautifully, and decided to make their own widget sets. this is really annoying when trying to embed Xt stuff into applications that use gtk or qt.

    Xt was (is) just a toolkit framework on top of X, it does not change or modify the X protocol. Not only that, but Xt is a mediocre attempt at a toolkit, compared to modern standards: programming with Xt is not easy or intuitive and the on-screen widgets are not up to it.

    Xt is not the answer, but a unified toolkit would be nice. I don't think it will happen though, not in this lifetime.

  23. UI Not needed by tweakt · · Score: 4, Informative
    Whilst it's great that stuff like this is being implemented, is anyone actually working on making a point and click interface to active/deactivate functionality rather than having to get users to resort to deleting or editing files?
    1. This is a BETA release. (remember Mozilla is not intended for end users)
    2. It's nothing you'd ever need to turn off unless it was causing major problems (ie: crashes).
  24. Re:Xt by dollargonzo · · Score: 3, Interesting

    no one is asking you to use the Xt widgets. you can make them as pretty or as ugly as you want. but embedding other Xt stuff is much easier. there is no reason why gtk widgets can't be built on top of Xt, besides the fact that they use gdk.

    --
    BSD is for people who love UNIX. Linux is for those who hate Microsoft.
  25. You could do this before and without too much work by GoofyBoy · · Score: 4, Informative



    Here are the instructions

    I have it working with Mandrake 9 and Mozilla 1.0.

    --
    The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
  26. NO NEED TO RECOMPILE by Lendrick · · Score: 5, Informative

    The binary of Mozilla that you have supports antialiasing right now.

    Go here and follow the instructions near the top of the page. Provided you have a recent version of FreeType2 on your system and some TrueType fonts for it to find (you have to uncomment a line or two in your unix.js file and tell it where to look), you'll be using antialiased fonts in no time. It looks great, and I wish they'd do it by default. One other thing--you may want to set unhinted to "false", as fonts appear to render better that way. Experiment with your system, though.

    I've gotten this to work with the latest Mozilla and an otherwise fresh install of Redhat 8, plus a few .ttf's in the directory "~/.fonts".

    1. Re:NO NEED TO RECOMPILE by Dirtside · · Score: 3, Interesting

      I followed those instructions and got it to work -- looks great.

      However, my question is, why does this have to be in the unix.js file? Every time I install a new version of Mozilla, it's going to get overwritten. Isn't there some way to set these prefs in my ~/.mozilla dir so that they don't get overwritten when I install new versions? I tried putting a unix.js file in there, but it didn't help.

      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  27. Wow - what a bummer by baptiste · · Score: 3, Informative
    I've used Mozilla as my primary browser/email for a LONG time. Been happy with it. But I made a clean install of 1.2b (after uninstallin 1.2a) on my Win2K/SP3 laptop, and it won't even go past the splash screen. I guess something in my prefs file is hosing it - sure would like to know what.

    Still digging, but it won't even start? Sheesh.

  28. Disabling it by RPoet · · Score: 3, Informative

    Alright alright, if you really want to disable it, the way to do it is described here. Requires some prefs.js entry though.

    --
    "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
  29. Mozilla's feature flood by Jugalator · · Score: 5, Interesting

    I really have to say that I find the recent development of Mozilla very inspiring as it brings completely new, unique features to the users. First came integrated popup and advertisement blocking. A simple but effective feature. Then came Type Ahead. Then came link prefetching. Now, in what time span?

    I don't know about you, but at least my opinion is that the browser software has suffered from some serious stagnation during the past years. Since Internet Explorer 4.0 and its CSS and "DHTML" (mostly Javascript+CSS) support, I haven't seen much development in the browsers at all. Opera was innovative with mouse gestures, but I think the browser that truly turns this stagnation of browser features that's often limited to things like "slightly better CSS support", etc is Mozilla. I'm not even sure how it's possible for the team to bring so many new features in such a short time. Is it a side effect from being open source with browser enthusiasts working on it day and night? Is it "just" because a very flexible and well written code base? An efficient organization of the mozilla developers? A combination?

    IMHO, the changes in Mozilla from a late version such as 1.0 are surely larger (at least more useful) than the changes since Internet Explorer 4.0. Each new version is right now bringing lots of new features. Perhaps that will change in the future, but I'll enjoy it while it lasts for sure. :-)

    --
    Beware: In C++, your friends can see your privates!
    1. Re:Mozilla's feature flood by IamTheRealMike · · Score: 3, Interesting
      I'm not even sure how it's possible for the team to bring so many new features in such a short time. Is it a side effect from being open source with browser enthusiasts working on it day and night? Is it "just" because a very flexible and well written code base? An efficient organization of the mozilla developers? A combination?

      All of those things. I think type ahead find was written by an open source contributor (of course the module owners helped out, as with most Moz features). Mozilla is very very easy to hack on, as it's very componentized and large parts of it are just text files (xml/js/css). And finally they've been doing stuff like code review, super review, commit for a while so they are pretty slick about it.

    2. Re:Mozilla's feature flood by goon+america · · Score: 3, Informative

      FYI Type Ahead is not a new, unique feature. IE 5.* for the Mac has had it for the past 3 years. I should know, I've been using it since that time.

  30. Re:Xt by Redline · · Score: 3, Insightful

    programming with Xt is not easy or intuitive and the on-screen widgets are not up to it.

    No joke. To program directly with Xt is to hate your life. But I think you miss the point. Toolkits written *on top of* Xt, like Athena, OLIT, and Motif, are able to interoperate much better than say Qt and Gtk+. You can embed Athena widgets in a Motif app, or vice versa. It is not so easy with non-Xt toolkits. It helps if you think of Xt more like GDK than GTK+, like a sub-toolkit. Nobody writes apps completely with GDK, but *lots* of apps use it indirectly.

  31. Security danger by Henry+V+.009 · · Score: 5, Insightful

    I noticed pre-caching when I read the release notes last night. In my opinion it is a major security danger.

    A lot of police investigations go by the browser cache to see where you have browsed. Now you are giving control over to the cache to someone else.

    It would be simple to put a link in the page source to some kiddie porn or other illegal information. You would never see the link on the page and would have no way of knowing what had been inserted in your browser cache until the police inform you of how long you are going to be in jail. Sure, it is possible that the police won't use the browser cache as proof of guilt (don't bet on it), but that requires a lot of trust. And if they want to be technical about it, it is technically illegal to possess that information, no matter how it was acquired.

    And the gain isn't at all proportional to the risk. No pre-caching is done except on sites specifically engineered for it. That means next to none.

    1. Re:Security danger by AvitarX · · Score: 3, Insightful

      A lot of innocent until proven guilty hinges on the fact that if there is a reasonable doubt that you did not do something then you are innocent, because proof cannot exist with reasonable doubt. So the fact that you are using Mozilla, and Mozilla has the option for totally innocent looking pages to sneak kiddy porn into you cache would be a valid defense. also there would probably be html files cached that employed that tactic in you cache as a very strong defense.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  32. Some problems by macdaddy · · Score: 4, Interesting
    I've got to admit, I am have some problems with Mozilla 1.1 (final release). Recently the problems have led to instability. I was trying to buy a generator on eBay the other day. I had a search going and I opened windows to tabs as I found auctions that interested me. Mozilla kept dumping me. My box is a G4/500MP with 512 RAM running OS X 10.2.1. I've had window focus problems where I click in a Mozilla window text box but my focus is still on another window. I have to switch apps and back to regain control. The javascript driven menus on my PacketShaper 4545 web GUI still don't work. This one is really annoying. And the web GUI to the PacketShaper renders very slowly. Overall I'm pleased with Mozilla. It just needs some honing to fix some of the current problems.

    Maybe delaying a release and all new features for a short time to fix existing bugs would be worth it. My $.02.

  33. Re:1.2 beta still has bugs that was meant for 1.0. by Jugalator · · Score: 3, Funny

    > > Sorry, links to Bugzilla from Slashdot are disabled.
    > WTF?


    The war Bugzilla vs Slashdot sadly had this unfortunate outcome. We will have to live with it. But I'm sure you'll find a way to circumvent the problem. But then again, you're circumventing Bugzilla's access protection and you'll surely be a DMCA case.

    --
    Beware: In C++, your friends can see your privates!
  34. Some Tricks To Make Upgrading Easier by Milican · · Score: 5, Informative

    You can share bookmarks amoung all your installs of Mozilla, Phoenix, and probably other Gecko browsers (untested). All you do is add the following command to your prefs.js file:

    user_pref("browser.bookmarks.file", "C:\\Documents and Settings\\userdude\\Application Data\\Mozilla\\Profiles\\default\\wx4vqyna.slt\\bo okmarks.html");

    In addition, you can share plugins by adding the following line to your environment. Her is an example of what I did on my Windows box:

    MOZ_PLUGIN_PATH = "C:\Program Files\mozilla.org\Share\Plugin" (in Environment Variables on Win2k)

    Really helps so you don't have to redo plugins all the time and you can share one bookmark file for all!

    JOhn

  35. Doesn't work with Windows Proxy servers by oliverthered · · Score: 3, Interesting

    Well, this is almost true,
    please vote for this bug (99 votes so-far, lets make it 100)

    so that me and anyone else who uses microsoft proxy server 2 or any NTLM authenticating proxy can use mozilla. (this is probably a few million people, and a lot of corporations)

    This bug has been there since 2000-01-11, and won't make 1.2, hopefully it'll make 1.3 alpha 1!!!

    --
    thank God the internet isn't a human right.
    1. Re:Doesn't work with Windows Proxy servers by cant_get_a_good_nick · · Score: 3, Interesting

      Now why would they bother doing this?
      Because every time someone posts any Mozilla related story to Slashdot they get, well, slashdotted. Considering it's a DB driven site, it doens't take all that much to drive the server to it's knees and make it unusable. So for a day or so, they can't use a basic productivity tool. Yeah, you can just copy n paste, but this minor increase in effort probably eliminates all the casual clickthroughs.

  36. Not a good idea by spitzak · · Score: 4, Interesting
    This is a very very bad idea. You seriously underestimate the enormous complexity of the communication to a "toolkit". Also there is a little thing called "innovation" where people invent new methods of GUI interaction. This would be stopped by such a design, or would force people to write a parallel toolkit anyway (as many (most?) Windows applications are forced to).

    If you don't believe GUI innovation happens, imagine if X had an enforced toolkit. It would be Athena, in black and white, with this 1-bit color so written into it that it would be impossible to remove, and everybody would marvel at the fact that you could set it to inverse video and all applications would agree. And defenders would claim that the fact that only the middle mouse button makes the scrollbars move was a *feature*. And any intelligent people would be laughing X off the planet!

    Meanwhile, despite it's problems and pretty stupid design even for when it was invented, X is able to replicate interfaces designed 15 or more years after it was invented. This is because of the one intelligent decision they made, which was to keep the GUI widgets out of it!

    Now X has problems. There really should be high-level graphics, at least similar to PostScript. Though also complex, it is far less complex than toolkit interfaces, and perhaps more importantly the set of graphics calls needed has been pretty stable for about 20 years. It may even make sense to add calls to "draw a nice raised box" or "clear this to the flat background color" which would do about 99% of what people want "themes" to do.

    Also there is a bit of "toolkit" inside X: the "window manager" (even though a seperate process, but the communication protocols are there, and I know for a fact that it takes more code to communicate with the window manager than it would take to draw the window borders and handle moving and raising the windows myself). This also needs to be removed.

    But I am serious that putting any kind of "toolkit" interface into the system in a very very bad idea.

    1. Re:Not a good idea by evbergen · · Score: 3, Insightful

      It's nice that you mention window managers. Although generally not running on the X server side, they are an integral part of the X window system. Even though window managers are specified as an entity separate from the client application, we've seen lots of innovation in window managers.

      If the X server would not mandate certain widgets, just as it does not mandate any specific window manager, but would simply allow a 'widget server', then client applications could still be relieved of the burden of managing their own widgets, just as clients are already relieved from the burden of drawing their own window decorations and moving windows around.

      It would be great if applications wouldn't have to worry about drawing a check mark in check boxes when clicked, not even at the protocol level, and that a widget server would handle that.

      We'd change themes (widget servers) as easy as we change window managers now, and have a well-defined protocol between client application, display server and widget server, just as we have for window managers.

      I'm serious. We need a better X protocol. And it's not HTML/XML over HTTP, sorry. The ultimate test there is to get self hosting I guess, i.e. can you implement a web browser as a web application.

      But until someone implements gecko in javascript, I'm sceptical ;-).

      --
      All generalizations are false, including this one. (Mark Twain)
  37. Re:How much memory will it use with my MAC OSX by veddermatic · · Score: 3, Informative

    I'm running most recent OS X (10.2.1) and this version of Mozilla is taking up 8% RAM (of 512 MB)

    --
    Department of Homeland Security: Removing the rights real patriots fought and died for since 2001
  38. Another major unfixed bug by Animats · · Score: 3, Informative
    The bug that causes crashes and profile corruption if you have both Netscape and Mozilla installed still hasnt't been fixed.

    That's been outstanding for most of a year now, which is inexcusable for a major bug that causes data loss and crashes. The Mozilla team still has way too many "don't do that" items in the release notes.

    Unless this thing gets cleaned up, it's never going to get market share. Adding additional features of very marginal utility won't help. Could AOL use Mozilla as their standard browser? No way. It's got to just work.

  39. Yeah, I stopped using that by Gorimek · · Score: 3, Insightful

    It sounds good in theory, but once you use you realize that pages have far more links than you thought. A typical page can have 20 or 50 links, only 2-4 of which you would be interested in prefetching. Just look around on this page for a good example. It ends up furiously downloading pages, movies etc for as much as your connection can bear, and it's not good for anyone.

    The Mozilla approach could actually work. If any designers ever decide to use it.

  40. Prefetching & Standards Complience by Thenomain · · Score: 4, Insightful

    Maybe I'm missing the standard for it (I'm not on the bleeding edge of things), but I was looking at the HTML 4.01 link rel types and can't find "preload". Fortunately, according to the FAQ, "next" will do just fine.

    This is a not nit-pick, but with all the touting of how 100% standards compliant Mozilla is, I'm wondering what the philosophy is on extending the standard, if "preload" isn't in some later HTML standard that I don't yet know about us.

    --
    This now concludes our broadcast day.
    1. Re:Prefetching & Standards Complience by FooBarWidget · · Score: 3, Informative

      Complying to W3C standards doesn't mean not allowed to invent your own standards.
      The effect of preload-"tags" is mostly transparent; users of alternate browsers won't be left in the dark just because those browsers don't support that feature.

    2. Re:Prefetching & Standards Complience by asa · · Score: 3, Interesting

      100% standards compliance means not doing anything forbidden by the standards body specifications and supporting the recommendations of the standards body. If an extension doesn't violate the specification then it is in compliance. The LINK element was specifically designed with room for clients to extend and interpret.

      --Asa

    3. Re:Prefetching & Standards Complience by darinf · · Score: 3, Informative

      rel=prefetch is something we hope to turn into a standard eventually. it is better than overloading the meaning of rel=next.

  41. It'd be nice if they DOCUMNENTED it... by Lendrick · · Score: 3, Interesting

    Last I heard, the general Mozilla project attitutde about documenting the preferences was that if you don't know what they are, you shouldn't mess with them. As a highly techincal user, I myself would beg to differ. Failing to document all of these options in one place is a cop-out, and their excuse is pure arrogance.

    If I'm wrong about this, and there is complete documentation on all the prefs files, I'd love to know about it.

  42. There's no "right" app for OS X users. by kitzilla · · Score: 4, Informative

    I agree that Chimera ("Navigator," officially) is a terrific Mozilla browser for OS X, but we have a lot of choices these days.

    Chimera is still pretty sparse on features. I use the nightlies, and run into a fair number of buggy builds. But it's quick, and sure looks like an OS X app. I use it far more than anything else.

    KevinG, the guy who did the Pinstripe skin for Mozilla, was nice enough to compile Phoenix 0.3 for OS X. It's just an experiment, not part of the regular project. But damn if it doesn't work, and it has some very cool features. Even *more* OS X choices:

    http://www.kmgerich.com/misc.html

    This OS X build introduced me to Phoenix, which is now running on my Linux box. Kevin's page says his OS X build requires Jaguar, but I'm using it with 10.1.5 just fine.

    Mozilla 1.2b feels very stable on OS X. It's not as fast as Chimera, nor is it as consistent with the Mac human interface standards. But it doesn't suck, and some users like working from within a suite. I know plenty of OS X guys who are more comfortable with Mozilla's mail than Mail.app. It's a matter of preference.

    To me, Netscape 7.0 is heavy and gaudy. It has a spellcheck app, however, and isn't a bad choice for those who rely on the Netscape/Mozilla suite for email.

    As for Omniweb, it's a great browser. A few more features than Chimera in its current state of development, though don't think it renders as well. Speed is a toss-up.

    Every OS X user's needs are different. It's a great time to explore the platform, however. There's a browser for everyone. Run whatever you prefer, and support the community which surrounds it.

    Thanks to all the developers who make my online experience more enjoyable. Your work isn't taken for granted.

    --
    This is my post. There are many others like it. If you don't like what you read here, go try one of the others.
  43. Leech by fialar · · Score: 3, Informative

    Leech seems to install properly only if you run it as root. (It wanted my to have write access to /usr/local/mozilla/chrome dir.)

    It doesn't work as a user. Weird.

  44. Re:Cautionary e-mail tale by Lendrick · · Score: 3, Informative

    Sounds like a really old bug. When Moz-Mail crashed, it used to corrupt its mail index files. The trick to getting at your mail again was just deleting the corrupt index. It would reindex them the next time it started. Nowadays, when it sees a corrupt index file, it rebuilds the index automatically.

    How long ago did you have this problem? To my knowledge, it's been fine for over a year.

  45. Re:New standard? by asa · · Score: 3, Informative

    http://www.w3.org/TR/REC-html40/struct/links.html# edef-LINK

    The link tag has been around for some time. It is used to describe releationships between documents. It was desinged by the w3c with extensibility in mind. The w3c leaves it up to the user agent to determine how to handle link data.

    --Asa

  46. viewing selection source... by esarjeant · · Score: 3, Informative

    There also appears to be a View Selection Source option now. So I can highlight a section of a document and view just that HTML source -- very handy for development.

    --

    Eric Sarjeant
    eric[@]sarjeant.com

  47. Chimera vs. Mozilla by EricWright · · Score: 3, Informative

    Is there any way to import Chimera bookmarks (XML) into Mozilla (HTML)? I did the obvious (Import bookmarks from mozilla and selected my bookmarks.xml file from the Chimera path) but that didn't work...

    TIA
    Eric

  48. Use / to find non-linked text by mbrubeck · · Score: 4, Informative

    If you just start typing "moz...", typeahead will only find text that's part of a link. If you type "/moz..." instead, it will find any text. (Apologies if you already knew this.)

  49. How do I save installed XUL stuff? by Dirtside · · Score: 4, Interesting

    I installed XUL Planet's Preferences Toolbar on Mozilla, but the next time I installed a new version, it was gone and I had to reinstall it. I know that you can install plugins into your ~/.mozilla directory so that upgrading the browser doesn't require reinstalling the plugins, but is it possible to do this for chrome-like things (like the aforementioned Preferences Toolbar)? I've highly customized the toolbar, as well, and I don't even know where that configuration gets saved. Thanks.

    --
    "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  50. Re:CSS is still messed up :-( by asa · · Score: 4, Interesting

    they still stubbornly refuse to use CSS stylesheets that aren't served with a mime type of text/css ... I still can't see the information on a vast number of web sites out there

    You visit sites that include the "information" in stylesheets? That's completely lame. The whole purpose of CSS is to separate the information from the style. If they're including the content in their style sheets then they're doing a lot more wrong than just serving the incorrect mime type.

    --Asa

  51. Re:Link Pre-fetching is a baaad idea...(indeed) by *xpenguin* · · Score: 4, Funny

    Oct 17, 2002:

    First goatse.cx link modded informative.

  52. Re:CSS is still messed up :-( by Anonymous+Brave+Guy · · Score: 3, Informative
    The whole purpose of CSS is to separate the information from the style. If they're including the content in their style sheets then they're doing a lot more wrong than just serving the incorrect mime type.

    I was referring to the styling information, not the words on the page. Unfortunately, if a page makes heavy use of CSS for formatting and layout, it can still be very hard to read without it. You could just read the plain text by scrolling around the window lots, but then you could just read the HTML source if you wanted. That's not really the point. IE gets it right: it shows me what I want to see. Moz doesn't. That's an indisputable point to IE, I'm afraid. There is simply no good reason for Moz to be anal about whether it renders using a stylesheet or not, at least not without giving the user an opportunity to override it.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.