Firefox 4 Feature Directory

[patrickjdempsey]

OOooh vector IMAGE support! Nice! That's actually a pretty nice complement to the VIDEO tag.

[sabret00the]

The MSI package will not make 4.0 and it isn't blocking 4.0 either.

[Omega X]

I'm going to wait a bit before removing it. Some features are being pulled from blocking because they can't get a solid block milestone opportunity even thought they are very wanted.

[sciguyryan]

I think JetPack should also be on there somewhere too

[sabret00the]

I have a feeling App Tabs will be completely re-written/re-implemented for 4.1

[sciguyryan]

You've also got the -moz-font-feature-opentype feature (see bug 511339) which should get a mention I think

Edit: Also, this: https://bugzilla.mozilla.org/show_bug.cgi?id=569520

[Bluefang]

FYI TabCandy is now known as TabView, and it's (in part) landing on trunk today.

[Omega X]

They changed the name again...

[patrickjdempsey]

Edit: Also, this: https://bugzilla.mozilla.org/show_bug.cgi?id=569520

Is this for use with traditional PNG and GIF animations? That bug reads like Vogon poetry.

[patrickjdempsey]

They changed the name again...

And what's the *current* name for Personas?

[sciguyryan]

Edit: Also, this: https://bugzilla.mozilla.org/show_bug.cgi?id=569520

Is this for use with traditional PNG and GIF animations? That bug reads like Vogon poetry.

I _believe_ it is for synchronizing event executions with animations, like SMIL and the like - though I'm not going to put a firm bet on anything until the developer documentations are up-and-running.

[patrickjdempsey]

Looks like you are missing Replace Statusbar with Addons bar:
https://bugzilla.mozilla.org/show_bug.cgi?id=574688

[sciguyryan]

Another item that should probably get a mention is bug 506826 which is about to land soon - seems like it could be really useful in a lot of things.

[patrickjdempsey]

And bug 520124: "Allow applying a persona on top of any custom theme"

https://bugzilla.mozilla.org/show_bug.cgi?id=520124

For many of us, this will have been a long time coming.

[michaell522]

Edit: Also, this: https://bugzilla.mozilla.org/show_bug.cgi?id=569520

Is this for use with traditional PNG and GIF animations? That bug reads like Vogon poetry.

For any kind of animation using script (so not a plugin, and not PNG/GIF animation). The post linked at the beginning of the bug is maybe clearer:

We need a way to give the browser control over animation frame rates and
the timing of when animations actually draw. Having everyone doing their
own setTimeout()-based animation is terribly inefficient; basically if
there are 5 independent animations each wanting repainting 50 times a
second, then we'll try to repaint 5*50=250 times a second. We should
only repaint 20 times a second. Actually, we should repaint N times a
second where N is chosen by the browser to be no higher than the user's
screen refresh rate.

Rather than people writing javascript animations having updating on their own timers without regard to what is actually getting displayed, they will be able to ask the browser when the next display update is, and then tell the browser to draw something in that next update, which makes it all much more efficient. Does that help to explain?

However, getting back to the topic, I'm not sure this, and some of the other stuff mentioned recently, really belongs in a "feature directory" as a separate item - otherwise the result will be more of a changelog than a feature directory.