Places Feature Cut From Firefox 2

segphault writes "Apparently, the new bookmark and history system (called 'Places') scheduled for inclusion in Firefox 2 has been removed from the roadmap and disabled in the builds. An article at Ars Technica discusses some of the implications: 'Since Firefox 2 (and all alpha builds from here on out) will use the conventional bookmark system, those of you that have been using Firefox 2 alphas (the Gecko 1.8 branch) will have to export your bookmarks to HTML in order to preserve them. As a Firefox user and a software developer, I am personally very disappointed with the removal of this innovative feature.'" Update: 05/01 01:16 GMT by Z : Ars link updated.

Comments

Re:Firefox has the wrong focus

[Xelrach]

Doesn't the fact that "Places" was delayed show that they _are_ focused on polish?

Let me start by quoting...

[Biomechanical]

...My earlier comment on Digg when this story showed up there.

Personally I couldn't give two shits about _any_ browser getting "new and exciting!!!!" features right at the moment, and my reason is very simple,

They all fail at what they are supposed to do, first and foremost. Some fail utterly, and other fail a little bit, but they all _fail_.

There is not a single browser available for download at the moment that _fully_ supports the web standards laid down by the W3C, http://w3.org/ and developers who are working on Safari, Konqueror, Mozilla Firefox and Seamonkey, IE, Opera, Camino, and so on, all need to take a step back from their computers and say,

"Hey, how come we're adding new features to a program that isn't even standards-compliant?"

The continual lack of support for even the full subset of CSS 1 and 2.1 makes designing pages based on XHTML and CSS a frickin' pain in the arse.

If there was one browser, even just one, that was cross-platform and fully supported even just HTML, XHTML, CSS 1 and 2.1 (maybe even parts of 3), and was extensible to support such things as SVG and XVRML, then I would be using it in a damn shot, and then I'd _know_ that when a page failed to render properly, _I_ screwed up, not a bug in the browser.

Stop adding features guys, just follow the damn standards.

All I want, and I'm betting so do a great deal of other people who work with the web, is a browser that follows the standards for HTML, XHTML, CSS 1 & 2 (maybe even 3), Javascript, and DOM.

Extra features are nice, yes, but the top priority should be putting out a browser that follows the standards, first and foremost.

What good are extensions and themes and fancy bookmarking tools if the core program for seeing information on the web cannot render pages which have been correctly created?

MOD PARENT UP

[Trogre]

Putting close buttons in individual tabs is nothing but evil, wrong and stupid.

One mis-click on a tab (which is very common when managing a dozen or so tabs) and you've just closed an important page with no confirmation dialog.

See http://bugzilla.gnome.org/show_bug.cgi?id=335453 for the current gnome-terminal fiasco.

Just don't do it.

Re:Bad URL

[mabinogi]

if I have to stare at a blank page while my status bar says "waiting for google-analytics.com" then either I'm going to block google-analytics.com, or I'm just going to get fed up and stop visiting your site.

It really bugs me just how often I have to sit and wait for my browser to contact 5 different ad and stat sites when viewing some web sites - slashdot being one of the big offenders.

I have no problem with you providing (tasteful and discreet) ads, I have no problem with you collecting stats. I do have a problem with having to wait for that to happen, when I could be reading your site.