Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Firefox Deer Park Alpha Available

Zonk posted more than 9 years ago | from the break-out-the-salt-licks dept.

Mozilla 330

The Mozilla folks have made available the newest release of the Firefox web browser. This release is for testers and developers only, and should not be used if you have no interest in trying out the latest build. The release notes cover the recent changes. From the what's new document: "Fast back (and forward) - This very experimental feature allows much faster session history navigation. The feature is off by default but can be enabled for testing purposes by setting the browser.sessionhistory.max_viewers preference to a nonzero number."

Sorry! There are no comments related to the filter you selected.

burning edge says: (4, Informative)

professorhojo (686761) | more than 9 years ago | (#12692748)

According to Burning Edge, there are numerous usability regressions since 1.0 on the trunk builds.

I think they need a lot of time to iron things out and this is one of those things they've decided to prolong the process!

Since Fx is a hugely successful project that is still unusual in its open-source nature, the fact that more alphas and betas and in-betweens are being released may be a good thing.

Re:burning edge says: (-1, Troll)

Anonymous Coward | more than 9 years ago | (#12692845)

They managed to make FF even more slow and bloated. Good job, assholes!

Re:burning edge says: (0)

Anonymous Coward | more than 9 years ago | (#12693010)

For crying out load, it'a an ALPHA build. And it's almost 1 year younger than the previous release (Firefox1.0 used a branch of the main development tree).

fp (-1, Offtopic)

Anonymous Coward | more than 9 years ago | (#12692749)

Nothing for you to see here. Please move along.

whatever

Re:fp (3, Funny)

miasmic (669645) | more than 9 years ago | (#12692757)

I hope it lets you fast forward to some better posts than this one!

Changes (4, Informative)

Hank Chinaski (257573) | more than 9 years ago | (#12692751)

Notable bug fixes

* Web page rendering and interaction
o 217527 - Left column on Slashdot is sometimes too narrow or too wide for its contents.
o 238493 - Ads on Gamespot flicker into other parts of the page during page load.
o 95227 - Make it possible to set different default font type (serif vs sans serif) for different languages.
o 47350 - Current scroll position not retained, reloading or going back to multipart/x-mixed-replace (e.g. Bugzilla bug lists).
o 56314 - Reverse selection colors when page background is similar to default selection background.
o 274553 - Blocking iframes either via an extension or userchrome.css breaks find toolbar search.
o 103638 - Targets with same name in different windows open in wrong window with javascript.
o 62384 - Text Zoom doesn't change dropdown height (without reload).
o 97283 - Mouse wheel scrolling does not work for elements such as div using overflow - auto or scroll.
o 251986 - Keyboard scrolling does not work for elements such as div using overflow - auto or scroll.
o 209020 - Meta HTTP-EQUIV="refresh" broken if midas was ever used in that browser window.
o 198155 - Midas html editing mode persists after leaving the page that enabled it.
o 21616 - Space after ::first-letter pseudo-element line is larger than between other lines (improvement in first-letter drop-caps appearance?).
o 273785 - Plugins not scanned/detected on startup (empty plug-ins dialog in downloads, open-with dialog for PDFs).
o 76197 - Scrollbars should look disabled when there's nowhere to scroll (not yet fixed on Mac).
o 151375 - Focus outline should be drawn outside of element.
o 133165 - Focus outline should include larger descendants of inline elements.
o 65917 - :active neither hierarchical nor picky about what can be activated.
o 20022 - :hover state not set until mouse move.
o 278531 - Generic request prioritization (loadgroup prioritization) (e.g. for each HTTP host, load images with lower priority than pages).
* Improved error pages. To enable error pages, go to about:config and set browser.xul.error_pages.enabled to true.
o 157004 - Error pages should be stored in history and show the original URL in the address bar.
o 237244 - "Try Again" on XUL error pages does not repost form data.
* Downloads
o 239006 - Download manager doesn't account for filesize when presenting combined percentages.
o 245829 - Download manager progress and title do not update correctly, wrong number of files and percentage after finishing or cancelling a download.
o 249677 - Cancel does not delete temporary file in helper app dialog, if default action is save.
* Accessibility
o 175893 - Make XUL 's focusable.
o 162081 - Wrong letter is underlined as accesskey / mnemonic when widget direction is RTL.
o Many keyboard accessibility fixes.
o Many screen-reader accessibility fixes.
* Speed and memory-use improvements
o 227361 - Don't reflow documents in background tabs until window resizing is complete.
o 131456 - Memory use does not go down after closing tabs.
o Many other speed and memory-use improvements.
* Windows-specific bugs
o 16940 - [Windows] IME is now disabled for password fields.
o 255123 - [Windows] Opening URL from another app focuses an existing window before opening a new window.
o 171349 - [Win98] Firefox icon is Win98's standard icon (taskbar & upper lefthand corner of app).
o 284716 - [Win2k/WinXP] Create DDBs in nsImageWin::Optimize. (Fixes several performance bugs with large images, such as slow scrolling on exactaudiocopy.de.)
o 231300 - [Windows] Clearing cache is slow (nsLocalFile::MoveTo is slow to move directories).
* Mac-specific bugs
o 222364 - [Mac] Don't use sheet for the about box.
o 273217 - [Mac] Lots of menu items are enabled that shouldn't be when no windows are open, and many menu items that are correctly enabled do not work.
o 187508 - [Mac] Follow "full keyboard access" setting in System Preferences for tabbing navigation.
o 151249 - [Mac] Middle click on link does nothing on Mac OS X (should open link in new tab).
o 220589 - Cmd-Enter and Cmd-Shift-Enter should work like win/lin builds.
o 239218 - Menus are nonfunctional when 'tools' have focus (Downloads / Extensions / Theme Managers, JavaScript Console and Page Info window).
* Linux-specific bugs
o 241245 - [Linux] Auto download to 'Desktop' downloads to home directory on Linux.
o 238854 - [GTK2] Changing GNOME2 theme doesn't apply until restarting Mozilla.
* 57724 - View Source corrects for parser errors and shows slightly different source than what was sent by the server.
* 269259 - When upgrading an extension, its metadata is not updated from the new install.rdf.
* 69114 - Opening Internet Shortcuts (.url files) doesn't work (using File | Open or file protocol)
* 245163 - Right-click context menu is cut off/disappearing/offscreen when it contains too many items (items added by extensions).
* 275430 - Change default for "open links from other applications" to be "a new tab in the most recent window" instead of "the most recent tab/window". (?)
* 253950 - Less confusing UI when default profile is locked on startup.

Re:Changes (1)

80 85 83 83 89 33 (819873) | more than 9 years ago | (#12692853)

on most web pages i often increase the font size using Ctrl+ and the main text area usually gets squished by collums on the sides. i would like the article content (the stuff that matters) of pages to widen when the text gets bigger, and not be confined by a certain width no matter what.

Re:Changes (4, Informative)

Issue9mm (97360) | more than 9 years ago | (#12692911)

That's not necessarily something that should be fixed at the browser level. From a coding perspective, I've gotten into the habit of specifying horizontal margins and padding in ems, which is a relative unit of measure (horizontal) based on font size. Because of that, a simple document can scale perfectly regardless of text size.

If I specify a column's boundary at 150px, it isn't the browser's job to correct for it, other than to wrap the text when it gets too big.

Long story short, your complaint is with web designers, not with Firefox.

-9mm-

Re:Changes (-1, Troll)

Anonymous Coward | more than 9 years ago | (#12692935)

Spoken like a true ass-to-mouth Mozilla-zealot.

Do you have a blog, fuck-bunny?

Re:Changes (1)

80 85 83 83 89 33 (819873) | more than 9 years ago | (#12692975)

i had the feeling that web page designers were not making their pages flexible enough to work with FF's text enlarging. (i must be getting old; need the large font to read comfortably, damn!). though it would be nice to somehow be able to force margins wider....

Re:Changes (4, Informative)

n0-0p (325773) | more than 9 years ago | (#12693018)

Opera style "page zoom" should be possible in 1.5, so you may eventually get your wish anyway. It's just not really practical with the current rendering engine.

good to see (1)

teh_mykel (756567) | more than 9 years ago | (#12692754)

keep the progress up :) its good to see mozilla are open to change, and are willing to impliment useful features as asked. its nice to have a company respond to the individuals for once.

Opera (1, Flamebait)

Digital Warfare (746982) | more than 9 years ago | (#12692755)

Its seems to me as though Firefox are taking Opera as their lead example.

Yay! (0, Flamebait)

Silverlancer (786390) | more than 9 years ago | (#12692769)

Bug Fixes
...
o 217527 - Left column on Slashdot is sometimes too narrow or too wide for its contents.


FINALLY! Slashdot renders correctly. But doesn't this mean we can't make any jokes about Firefox and Slashdot anymore?

Re:Yay! (0)

Anonymous Coward | more than 9 years ago | (#12692786)

Just wait for the next version of IE when Microsoft trys to reinvent the wheel

Re:Yay! (1)

millwall (622730) | more than 9 years ago | (#12692805)

Bug Fixes
...
o 217527 - Left column on Slashdot is sometimes too narrow or too wide for its contents.


I thought this wasn't considered to be a bug, and that the problem was with Slashcode's HTML?

Re:Yay! (4, Informative)

linuxci (3530) | more than 9 years ago | (#12692828)

I thought this wasn't considered to be a bug, and that the problem was with Slashcode's HTML?

Although Slashdot's HTML is old and bloated by modern standards this was actually a bug in the Firefox renderer. Although I'd like to see Slashdot clean up their HTML in the future this time it wasn't their fault.

This bug was actually fixed before Firefox 1.0 was relased but they pulled the fix from 1.0 as it caused some regressions, lucky that they got ironed out.

Re:Yay! (1)

Speare (84249) | more than 9 years ago | (#12692980)

I haven't yet tried it-- is the fix just a reload/re-layout after the page is done loading? Or is it more of an actual fix?

I noticed that phpBB forum sites often have the same issue for their right column. A real fix should notice the problem during layout and rework the layout assumptions that are proven false as it goes.

Re:Yay! (1)

linuxci (3530) | more than 9 years ago | (#12693036)

I think the fix addresses the root of the problem, check with these forum sites and see if they now display correctly too. If they don't then it's a good opportunity to try out the new reporter tool in Firefox.

It's in the Help menu under Report Broken Website

Re:Yay! (1)

petermgreen (876956) | more than 9 years ago | (#12692847)

whilst slashcodes html is pretty damn horrid this was definately a bug in firefox.

iirc firefox could render the page fine if it did so all at once but sometimes fucked it up when rendering incrementally.

Re:Yay! (1, Informative)

Anonymous Coward | more than 9 years ago | (#12692909)

I thought this wasn't considered to be a bug, and that the problem was with Slashcode's HTML?

Are you fucking kidding me? EVERY TIME Firefox gets mentioned on Slashdot this comes up. And EVERY TIME, a FUCKING MORON like you says this.

It's a bug in Firefox.

What, the valid HTML testcase attached to the Bugzilla entry isn't enough? The FIREFOX DEVELOPERS saying it's a bug in Firefox isn't enough? The fact that the next version of Firefox will fix it isn't enough?

What will it take for you fucking fanboys to realise that YES, YOUR PRECIOUS FIREFOX HAS A BUG?!?

I started pointing this out in a reasonable manner last year. I get slightly louder and more aggressive each time I post this. I don't tolerate idiot fanboys. Nobody should.

Re:Yay! (0)

Anonymous Coward | more than 9 years ago | (#12692931)

A previous rant of mine [slashdot.org] . It's not sinking in, is it?

What is it going to take to convince people that it's a bug in Firefox?

Obviously, nothing will convince some idiots. Idiocy is very persistent.

Re:Yay! (0)

Anonymous Coward | more than 9 years ago | (#12692959)

Easy, cowboy!

Re:Yay! (0)

Anonymous Coward | more than 9 years ago | (#12693143)

That was a good post, to which I am replying as a means of demonstrating my approval

Slashdot (-1, Redundant)

Paska (801395) | more than 9 years ago | (#12692771)

Renders Slashdot correctly, yay! :)

Firefox 1.1 (1)

bcmm (768152) | more than 9 years ago | (#12692777)

For the record, Deer Park is not the next minor point release (1.05 is guess), but the line that will be officially released as Firefox 1.1

Re:Firefox 1.1 (1)

jesterzog (189797) | more than 9 years ago | (#12692850)

Deer Park is not the next minor point release (1.05 is guess), but the line that will be officially released as Firefox 1.1

Does this then mean that Deer Park should also have the binary diff update feature? (Though presumably not supported with actual updates.)

Re:Firefox 1.1 (2, Informative)

linuxci (3530) | more than 9 years ago | (#12692884)

Not sure that is fully implemented yet (as there's no easy way to test) but this feature will be in for 1.1 so making updates a lot smaller and easier (not that the full download updates were that big anyway)

Re:Firefox 1.1 (2, Interesting)

mdew (651926) | more than 9 years ago | (#12693089)

I was thinking how they would implement such a feature, considering theres numerious "optimised" compiled binaries, so each firefox binary will be different (apart from the official mozilla.org release).. how would you make a binary diff against the unofficial packages? is it possible?

Re:Firefox 1.1 (1, Insightful)

Anonymous Coward | more than 9 years ago | (#12693184)

Well there's only one official build for each platform. All they have to do is query the server with a checksum of the binary currently in use, and if it doesn't match the official build, they can send the whole thing down the line or redirect or something.

Re:Firefox 1.1 (1)

bsharitt (580506) | more than 9 years ago | (#12693000)

Was 1.1 going to fix the Mac version so it actually looks and behaves like a Mac application, or is that going to have to wait until 2.0?

Re:Firefox 1.1 (0)

Anonymous Coward | more than 9 years ago | (#12693241)

Actually I think it does that. On windows the preference dialog box looks like a mac preference dialog box. Icons along the top instead of the side. So they may be doing that work still.

Extensions (5, Interesting)

johansalk (818687) | more than 9 years ago | (#12692780)

I'm often late on adopting firefox new releases and the reason is simply that extensions often need time to be updated by their authors. I wish the Mozilla foundation would somehow remedy this problem in the future, so updating the browser need not break extensions.

Re:Extensions (2, Informative)

Hank Chinaski (257573) | more than 9 years ago | (#12692801)

this is a alpha released. it is targeted at extension and theme developers so that end users have all their favorites available ones the final product is published.

Many work (5, Informative)

glrotate (300695) | more than 9 years ago | (#12692842)

Working:

Adblock
Launchy
Bugmenot
Spellbound
Stumbleu pon

Broke:

Forecastfox
Dictionarysearch

Re:Extensions (5, Funny)

MynockGuano (164259) | more than 9 years ago | (#12692879)

Perhaps they should put out a sort of "alpha release". This release would be basically a semi-official in-development build for "testing purposes only" on which extension authors and developers can "test" their code to see if there are any problems. This way, they will have time to prepare their extensions before the next release. Furthermore, to avoid confusion and prevent everyone from jumping on an unstable product and generating negative publicity, it would probably be best not to brand it with the Firefox name; maybe they could just use whatever the current code-name happens to be (like, for example, "Deer Park", a random name that I just happened to come up with).

Re:Extensions (1)

Timesprout (579035) | more than 9 years ago | (#12692989)

Mock away but a lot of people find it more that a little stupid that just about every new Firefox release, however minor breaks existing extensions. Its really not a very clever way to treat an extension interface.

Re:Extensions (1)

I confirm I'm not a (720413) | more than 9 years ago | (#12693097)

a lot of people find it more that a little stupid that just about every new Firefox release, however minor breaks existing extensions

I've not really noticed this since the change to (I think) 1.0. Same with themes (thank $DEITY). Which extensions have you had problems with?

Re:Extensions (1)

MynockGuano (164259) | more than 9 years ago | (#12693128)

I was just teasing; no offense intended to the original poster. I was just pointing out that this is exactly the situation that this release is meant to address in a way that I hoped would make an impression. I apologize for any offense taken.

Re:Extensions (1)

n0-0p (325773) | more than 9 years ago | (#12693151)

The issue is that the interfaces aren't completely solidified. For instance, plugging some of the Javascript security issues in 1.0.2 required breaking several extensions that relied on those interfaces. The devs have said that the extension versioning will become less of an issue once the existing interfaces have been locked. Unfortuneately there's still quite a bit of active development in that area.

It's either this approach, or the backwards compatability at all costs mantra that made Microsoft a target for years. One must accept some compromises. Though I thought the sarcasm was a bit heavy too.

Re:Extensions (1)

spectre_240sx (720999) | more than 9 years ago | (#12693245)

A lot of the people that have that annoyance have been using the browser before it was 1.0. Before that time, expect things to change. What's so hard about that concept?

Re:Extensions (1)

bmongar (230600) | more than 9 years ago | (#12692994)

I think Deer Park is an awful name. Mostly because is reminds me of a town/filling station half way between Jefferson City, Mo, and Columbia Mo. That filling station had a 'deliverance' feel to it for sure.

"Filling station"? (0)

Anonymous Coward | more than 9 years ago | (#12693277)

Oh, you must mean gas station. Foreigner. Also, capitalize both letters of a state's postal abbreviation.

Will copying work *all* the time now? (1, Insightful)

Anonymous Coward | more than 9 years ago | (#12692791)

Any chance the god damned clipboard bug is fixed yet?

New browser features (4, Informative)

darteaga (806257) | more than 9 years ago | (#12692795)

Re:New browser features (2, Informative)

toadnine (525325) | more than 9 years ago | (#12692999)

Not bad. 3 out of 6 new features are copied from Opera. "Sanitize" vs. "Delete private data" "Fast back (and Forward)" vs. "Rewind" and "Fast Forward" "Report a broken website wizard" vs. "Help -> Report a site problem"

Re:New browser features (2, Interesting)

linuxci (3530) | more than 9 years ago | (#12693156)

Not bad. 3 out of 6 new features are copied from Opera

So what? Some people prefer the Opera UI and will use that as their default browser, others prefer the way Firefox is designed. What's wrong with copying the best features off other browsers? There's not one browser fits all.

I think Firefox is better designed for users that want a relatively simple interface whereas Opera comes packed with just about everything but the kitchen sink (it'll be in version 9.0).

So to me Firefox and Opera appeal to different people. They both support standards and provide competition to the browser world so I like to see both grow.

Re:New browser features (2, Funny)

MynockGuano (164259) | more than 9 years ago | (#12693169)

Unregrettably, Opera's ad-spam feature wasn't quite able to make it for this release.

Re:New browser features (4, Interesting)

Lussarn (105276) | more than 9 years ago | (#12693321)

It's a god damn mystery why opera has close to zero marketshare and Firefox has 5% when according to some opera fanbois all features of every browser is copied from opera. So where is opera lacking? Why isn't marketshare larger? Maybe you should ask yourself that question instead of picking on successfull browsers such as Firefox.

maxviewers or maxentries? (0)

Anonymous Coward | more than 9 years ago | (#12692799)

I see browser.sessionhistory.max_entries set at 50. Is this what the article meant instead of max_viewers?

Re:maxviewers or maxentries? (0)

Anonymous Coward | more than 9 years ago | (#12692873)

No, max_viewers needs to be added and set non-zero to enable the new functionality. Well worth doing, because it makes it very snappy.

Graphical History (3, Interesting)

Anonymous Coward | more than 9 years ago | (#12692804)

When will Firefox implement a graphical representation of the history for the user?

Thumbnails of where the user has been, linked in an easy to follow graphical manner. It would make finding sites of interest (where one has forgotten where they found them) so much easier.

Re:Graphical History (0, Flamebait)

millwall (622730) | more than 9 years ago | (#12692824)

When will Firefox implement a graphical representation of the history for the user?

Obligatory answer: When you create it. Stop whining.

Re:Graphical History (2, Insightful)

Hank Chinaski (257573) | more than 9 years ago | (#12692837)

never. this is ideal stuff for an extension. there is already one called "how did i get here".

Re:Graphical History, how to start (3, Interesting)

kbrosnan (880121) | more than 9 years ago | (#12693019)

When someone writes some writes some code to implememt an API that Robert O'Callahan wrote for the upcoming release. The API renders web pages to images [mozillazine.org] .

Right now Mozilla/Firefox use a rather crusty history file format, Mork [mozilla.org] . There are plans to replace this history file with sqlite (Bug 245745, not until Gecko 1.9) which would make an extension writer's job a bit easier.

Re:Graphical History (0)

Anonymous Coward | more than 9 years ago | (#12692844)

If you're on Linux, try Kazehakase. It has rudimentary expression of the history as thumbnails, and a full-text history search. Neither are perfect, but nonetheless usable.

Re:Graphical History (0)

Anonymous Coward | more than 9 years ago | (#12693038)

>When will Firefox implement a graphical representation of the history for the user?

What browser are you using that currently supports this? When one does, let us know so we can copy it! Open source software does not INNOVATE!! ;-)

Seriously:
* Learn to ASK for a feature, instead of asking when it will arrive. I am a browser junkie and I have never seen this feature. Maybe you didn't mean it as such, but your question came across as "Are we there yet????" (whine).
* learn to post your FEATURE REQUESTS in the correct forum (ie Bugzilla). Here on Slashdot, the MSIE-using masses will just laugh at you.

Re:Graphical History (1)

bursa (452329) | more than 9 years ago | (#12693136)

NetSurf implements a graphical history:

http://netsurf.sourceforge.net/screenshots/ [sourceforge.net] (last screenshot)

We're looking for developers to work on the GTK port, which currently doesn't implement this.

Two things to look out for (3, Informative)

linuxci (3530) | more than 9 years ago | (#12692807)

1. Talkback [mozilla.org] (aka Quality Feedback Agent) in Windows builds is only enabled by default for a random selection of users on the Windows platform. This feature was built into the installer so that the talkback server on Firefox release builds wouldn't get bogged down.

As this is an alpha release and is a good idea to send in as much crash data as possible you may want to do a custom install on Windows and make sure it's selected.

2. This release comes with a tool you can use to report broken websites. This can be found in the help menu.

This data is stored in a serpate database to bugzilla so that you can report any broken sites without having to worry about clogging up bugzilla with duplicates.

Nothing really new. (1)

Rirath.com (807148) | more than 9 years ago | (#12692815)

It's not like all these changes just spring up overnight. Use nightly (or hourly) trunk builds and you'll be up to date long before these releases or preview releases. I fully understand there's a reason for these sorts of dev previews, but the real testers and developers have been using these features and fixes for quite a long time now.

Trunk builds are quite nice for even the regular user, so long as you're willing to put up with a few issues from time to time. The tradeoff for bug fixes and new features is well worth it, if you know what you're doing. If a really big bug comes along, just use an older build for a week or so. You extensions will usually be A-OK from build to build, but if something breaks them odds are you would have had to version-bump or reinstall them anyway on the next release. Give it a shot. It was fun using livemarks and find as you type before the release, and it's fun using things like fast back and the improved rendering before every else.

http://www.squarefree.com/burningedge/ [squarefree.com] - Not updated much anymore, but still a decent resource.

http://ftp.mozilla.org/pub/mozilla.org/firefox/nig htly/ [mozilla.org] - Nightly builds

http://bonsaibugs.org/pyblosxom.cgi/firefox/latest [bonsaibugs.org] - Latest bug fixes

Re:Nothing really new. (1)

linuxci (3530) | more than 9 years ago | (#12692863)

Speaking of fastback, that is a feature that makes back/forward a lot faster, similar to the performance of Opera.

This feature is switched off by default at the moment until the known regressions are ironed out, but I've enabled it and it works well for me. So if you want to give it a go the instructions are here [mozillazine.org]

In brief:
Type about:config in the URL bar
Right click and select "New > Integer"
Enter pref name (w/o quotes) "browser.sessionhistory.max_viewers" and click ok
Enter a value (number of pages to cache, the post I linked to suggests 5, if you've got a lot of memory maybe try 15 or 20) and click OK
Restart Firefox

Remember if reporting bugs on it please check that they're not already known about, the reason this is not enabled by default yet is there's a lot of regressions already known and they don't want bugzilla filled with dupes.

Fast back (1)

Scrameustache (459504) | more than 9 years ago | (#12692859)

Finally an imitation of Safari's SnapBack!

I love that thing, I've been missing it when using Firefox.
It lets you go back to the last adress you specified to the browser (by typing it in or using a bookmark), quite usefull when you let yourself wander semi-randomly through clicking links.

Re:Fast back (0)

Anonymous Coward | more than 9 years ago | (#12692878)

Finally an imitation of an insightful post!

Re:Fast back (2, Interesting)

Overzeetop (214511) | more than 9 years ago | (#12692899)

Darned, I was hoping they were implementing the Opera back/forward action, where the page is simply redrawn, for lack of the proper term, as the page you saw, rather than re-executed or re-downloaded. In Opera, the page redraws were so fast as to be unnoticable, and there were no data-post limitations. It was a snapshot rather than a reload. Of course, if you wanted to, you could just reload the page manually to re-invoke the post (or whatever actually happened on the page)

Re:Fast back (3, Informative)

linuxci (3530) | more than 9 years ago | (#12692925)

They are, it's the parent post that got it wrong.

Feature off by default as it's got some bugs at the moment, see my earlier comments [slashdot.org] on how to enable it.

Not sure if they plan to implement the feature the parent mentioned in safari

I think you mean Opera's Rewind button! (0)

Anonymous Coward | more than 9 years ago | (#12692918)

Safari's SnapBack?

Oh that would be Apple's copy of Opera's Rewind button. It seems like every major browser innovation in recent years has been copied from Opera.

1.1 Extensions (3, Informative)

mdew (651926) | more than 9 years ago | (#12692882)

http://www.projects1.com/firefox/exthacks/FFnightl yextensions.html [projects1.com]

something to help with the coversion to 1.0->1.1, also best to try a new profile too.

Re:1.1 Extensions (1)

Grey Ninja (739021) | more than 9 years ago | (#12692957)

Thanks for the info. Got my adblock and ForecastFox working again. :) Now the only thing missing is Linkification and gcache, and I can easily live without those. (And if I REALLY wanted them, I could just modify the extensions myself)

sex w1t4 a homo (-1, Offtopic)

Anonymous Coward | more than 9 years ago | (#12692889)

Since then. More fatal .mistakes,

But I Thought (1)

CastrTroy (595695) | more than 9 years ago | (#12692924)

But I thought they outlawed internet hunting?

Keychain on OS X? (1)

pschmied (5648) | more than 9 years ago | (#12692930)

Does anybody know the status of keychain integration on Mac OS X?

I know that Camino exists, but I really like the nifty Firefox extensions. Unfortunately, keychain integration is really a killer feature for me.

Anyone else wish there were keychain integration? Maybe somebody has already started working on this?

-Peter

Re:Keychain on OS X? (2, Insightful)

chrisblore (866716) | more than 9 years ago | (#12692979)

It's coming, but not until Firefox 1.5 (http://wiki.mozilla.org/Firefox:1.1_Mac_Migrators [mozilla.org] ).

"The Safari migrator will not be importing passwords for 1.1. For 1.5 we will utilize the Keychain for password storage and provide a simple migration solution."

Re:Keychain on OS X? (1)

argent (18001) | more than 9 years ago | (#12693037)

Camino Keychain Integration isn't all that hot, because Camino doesn't support multiple passwords per site, so you end up with separate Keychain entries for Camino and Webkit browsers.

Tabs (1)

Mr_Silver (213637) | more than 9 years ago | (#12692941)

I'm still looking forward to the day when you can ctrl-click a link and have the tab open immediately to the right of the currently active one and not at the far end of a line of tabs.

So far, the only way I've found of solving this is to download the miniT extension and then modify a text file. This is 2005, not 1995.

Product Placement? (1)

kevin_conaway (585204) | more than 9 years ago | (#12692951)

So did Deer Park water pay them for the naming rights to this release or what? Or is it just a coincidence? That could actually be pretty funny, if there was product placement in open source release names.

Memory leak (0)

Anonymous Coward | more than 9 years ago | (#12692964)

Does anyone know whether or not the monstrosity that is the notorious memory leak issue has been taken care of? It does happen quite often and it is a bane to have to close a Firefox session ripe with numerous tabs.

Re:Memory leak (1)

ssj_195 (827847) | more than 9 years ago | (#12693081)

It's actually memory leaks; there's a whole bunch of the buggers. Lots of leaks have been found and fixed, so I'm betting it won't be as bad as it used to be, but I doubt they've got them all, alas.

Re:Memory leak (1)

ssj_195 (827847) | more than 9 years ago | (#12693115)

Forgot to add - check out the Session Saver extension. Makes closing and re-opening a tab-heavy session pretty much painless.

Re:Memory leak (0)

Anonymous Coward | more than 9 years ago | (#12693139)

Thanks for the tip! Your adviec is very much appreciated.

Just me, or... (0)

Anonymous Coward | more than 9 years ago | (#12692968)

DUDE, IT'S FAAAAST!

[OT] crashing (0)

Anonymous Coward | more than 9 years ago | (#12693013)

Does anyone know of an extension that will automatically copy into clipboard whatever it is you happen to be writing at the time in a [textarea] of a form?

I've had browsers (including firefox) crash on me after writing a lengthy text to a forum or whatever, just a second before hitting reply. I always feel like pulling my hair out, so an extension that always keeps a working copy of what is being written would be a godsend. Is there such a thing?

Re:[OT] crashing (0)

Anonymous Coward | more than 9 years ago | (#12693100)

The best I could find for you is Auto Copy Lite [mozdev.org] , an extension which boasts automatically copying to the clipboard the text you select within Firefox. It is a shame there is no apparent better option and I understand your frustration -- more from losing data on busy websites than with crashing browsers -- but why not use this extension and just select all the text you have written (Control + A on Windows) every time you, say, finish a paragraph?

Sorry for not being more helpful.

[OT] crashing (0, Redundant)

FJR1300 Rider (888176) | more than 9 years ago | (#12693031)

Does anyone know of an extension that will automatically copy into clipboard whatever it is you happen to be writing at the time in a [textarea] of a form?

I've had browsers (including firefox) crash on me after writing a lengthy text to a forum or whatever, just a second before hitting reply. I always feel like pulling my hair out, so an extension that always keeps a working copy of what is being written would be a godsend. Is there such a thing?

Extension Installation (1)

MynockGuano (164259) | more than 9 years ago | (#12693041)

Something I haven't seen mentioned that has quietly slipped in is the new extension-installation support. You can place .xpi files directly in the 'extensions' directory of either the program or your profile, and the next time you start it, Deer Park will automatically recognize and install the new one. This would seem especially noteworthy at this point in time, since many "broken" extensions can be hand-updated by bumping the version numbers in the extension's install.rdf and re-zipping the .xpi. You can just stick a manually-bumped .xpi directly in one of the above-mentioned 'extensions' directories and restart the program. You no longer need to use a web installer, make a dummy webpage, or drag-and-drop the file to the Extension Manager (something that I've found--at least under Linux--to be reliably unreliable most of the time).

Re:Extension Installation (0)

Anonymous Coward | more than 9 years ago | (#12693223)

You no longer need to use a web installer, make a dummy webpage, or drag-and-drop the file to the Extension Manager

Huh? Just type /home/user/ into the address bar and click on the XPI.

bug fixes (1)

UlfGabe (846629) | more than 9 years ago | (#12693087)

# 217527 - Left column on Slashdot is sometimes too narrow or too wide for its contents.

I believe that some applause is nessisary.

Re:bug fixes (0)

Anonymous Coward | more than 9 years ago | (#12693243)

"I believe that some applause is nessisary"

As is some spellchecking :)

Aside from the faster history (1)

beforewisdom (729725) | more than 9 years ago | (#12693106)

Is there anything else in end-user land worth checking out?

Re:Aside from the faster history (0)

Anonymous Coward | more than 9 years ago | (#12693239)

I'm personally looking forward to using site-specific CSS. Granted, Greasemonkey works well for this, though..

not working for me (0)

Anonymous Coward | more than 9 years ago | (#12693141)

bookmark folder not showing
nav buttons disabled (dead)
some (important) plugin not compatible
cant even find "browser.sessionhistory.max_viewers" on about:config

reverting to old 1.04
worst waste of 30 minutes

Re:not working for me (2, Funny)

MynockGuano (164259) | more than 9 years ago | (#12693282)

cant even find "browser.sessionhistory.max_viewers" on about:config

I found it by right-clicking, selecting "New->Integer" and typing in "browser.sessionhistory.max_viewers" in about:config.

Re:not working for me (1)

mdew (651926) | more than 9 years ago | (#12693284)

tried a new profile?

How about... (1)

jbarr (2233) | more than 9 years ago | (#12693155)

...providing a toolbar button for the new Sanitize feature? Several features surprisingly lack toolbar icons (like Print Preview, Sanitize, etc.)

Also, be aware that many extensions do NOT recognize the latest Deer Park build.

As an Alpha, it looks pretty good. My only fear is that the likes of Microsoft use these Alpha builds as templates for their new releases...

Re:How about... (1)

Shaper_pmp (825142) | more than 9 years ago | (#12693271)

What, you mean in five years' time they'll release a "new" version of IE with all these current features in?

Keeping it trim (1)

TintinX (569362) | more than 9 years ago | (#12693212)

I've gotta say that I'm a little skeptical about the need for some of the 'fixes' in this build.
The attraction of FF is that it's sleek and lightweight. I don't want it to start making all kinds of allowances for bad formatting and adding 'features' like the Sanitize option. This is what optional extensions are for.
Let's focus on keeping FF slender. I don't like to think of a senario in, say, a couple of year's time when FF3.0 has become bloated.
Am I alone?

Just installed it, first impressions... (2, Informative)

NoMoreNicksLeft (516230) | more than 9 years ago | (#12693225)

Pro:

* An old xml text webpage of mine, first I clicked on, showed an xlink image. Inline images were the one thing I knew of preventing 100% XML webpages.

* SVG. When I finally converted from seamonkey for all the gorgeous features I didn't realize firefox had, the lack of SVG hurt, hurt badly.

Con:

* Alot of extensions seem to be broken. Waiting for updates will be hard.

* Greasemonkey. Yes, I know it's just another extension, but at work, this one is a lifesaver. Going without it means using IE for our stupid webapps.

* The GrayModern theme is broken. The realization that this theme existed convinced me to switch from seamonkey. God I hate the default theme. (Are there any compatible themes at this point? I'd take anything other than the default!)

Strange:

* Even though it disabled the FavIcon Picker extension, alot of my links still have the icons I set for them. Wondering if a single click on them will undo the handywork.

The Canvas (1)

notfancy (113542) | more than 9 years ago | (#12693317)

The <canvas> [mozilla.org] is cool. Safari compatibility or not, this could be the LOGO of the noughties. JavaScript is a fun language when you're not trying to be cross-compatible with every browser under the sun.

However, the last paragraph reads:

If fallback content is desired, some CSS tricks must be employed to mask the fallback content from Safari (which should render just the canvas), and also to mask the CSS tricks themselves from IE (which should render the fallback content). Todo: get hixie to put the CSS bits in

(emphasis in the original). While I commend Ian's commitment to standards, I can't imagine he will be very pleased with this tasks (for those who don't know him, he's victriolic against violations of the standards. He's a first-rate purist). I predicts the flames will be very pretty to look at.

Load More Comments
Slashdot Login

Need an Account?

Forgot your password?