Meet Firefox 4.0.1


Recommended Posts

Is there a gmail notifier that works for this yet, im using the windows system tray one and its crap.

I got Gmail Notifier to work on beta by installing it on the 3.6.4 (I have both versions installed) with the install.rdf file modified (max version 4.1) and is now working just fine on FF4.0b1.

Link to comment
Share on other sites

I took the patch from here:

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

and extracted the css, and got this:

bts.png

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

 #appmenu-button {
   border: 2px solid !important;
   border-top: none !important;
   -moz-border-left-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-border-bottom-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-border-right-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
                    0 0 2px 1px rgba(255,255,255,.25) inset !important;
 }

 #appmenu-button {
   -moz-appearance: none !important;
   background-image: -moz-linear-gradient(rgb(247,182,82), rgb(215,98,10) 95%) !important;
   background-clip: padding-box !important;
   -moz-border-radius: 0 0 4px 4px !important;
   border: 1px solid rgba(83,42,6,.9) !important;
   border-top: none !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
                    0 0 0 1px rgba(255,255,255,.25) inset !important;
   color: white !important;
   font-weight: bold !important;
   text-shadow: 0 0 1px rgba(0,0,0,.7),
                0 1px 2px rgba(0,0,0,.5) !important;
   padding: .1em 1.5em .15em 1.5em !important;
   margin: 0 !important;
 }

 #appmenu-button:-moz-window-inactive {
   background: transparent !important;
   background-clip: padding-box !important;
   border-color: rgba(0,0,0,.4) !important;
 }

 #appmenu-button:hover:not(:active):not([open]),
 #appmenu-button:hover:-moz-window-inactive:not(:active):not([open]) {
   background-image: -moz-radial-gradient(center bottom, farthest-side, rgba(252,240,89,.5) 10%, rgba(252,240,89,0) 70%),
                     -moz-radial-gradient(center bottom, farthest-side, rgb(236,133,0), rgba(255,229,172,0)),
                     -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
   border-color: rgba(83,42,6,.9) !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.1) inset,
                    0 0 2px 1px rgba(250,234,169,.7) inset,
                    0 -1px 0 rgba(250,234,169,.5) inset !important;
 }

 #appmenu-button:hover:active,
 #appmenu-button[open] {
   background-image: -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
   -moz-border-radius: 0 !important;
   -moz-box-shadow: 0 2px 4px rgba(0,0,0,.4) inset,
                    0 1px 1px rgba(0,0,0,.2) inset !important;
 }

Anyway i can't get rid of the damn 1px space above the button :s

Link to comment
Share on other sites

Try this:

#main-window {
  margin-top: 1px !important;
}

thanks a lot! :)

Link to comment
Share on other sites

Guys , is it just me who thinks Firefox 3.6.6 is more responsive than 3.7 or even 4 beta ? and playing very nice with flash and java more than 3.7 & 4b ?

Link to comment
Share on other sites

Guys , is it just me who thinks Firefox 3.6.6 is more responsive than 3.7 or even 4 beta ?
Yes.
and playing very nice with flash and java more than 3.7 & 4b ?
Can't respond to that. I have neither installed.
Link to comment
Share on other sites

Yeah, I noticed that.

Well, retained layers do make a huge difference though.

Even at this stage, webpage rendering is snappy and scrolling performance is excellent.

Hopefully that D2D bug will be fixed before Beta 2.

Link to comment
Share on other sites

D2D/DW seem to actually slow down normal browsing. I don't think that D2D/DW are worth the trouble unless you primarily surf on html5 graphics demo sites. Especially since some of the more annoying text rendering issues require Microsoft to update Windows itself (e.g. light text on dark background).

Link to comment
Share on other sites

The Direct2D stuff shouldn't take that long to get fixed, a lot of graphics work has been done since it first started that's changed how the window is rendered about 3 times I think.

It should be the easiest to fix now, the invalidation/scrolling no longer relies on the OS, it's now handled entirely by Firefox.

Edit: And titlebars on OS X don't render correctly now, since it's smarter at repainting so it doesn't trigger the titlebar to update.

Link to comment
Share on other sites

Edit: And titlebars on OS X don't render correctly now, since it's smarter at repainting so it doesn't trigger the titlebar to update.

i don't think that will matter, if i remember correctly, tabs on top for mac will eventually put the tabs in the titlebar removing that problem anyway

correct me if I'm wrong though, i'm just going off of memory

Link to comment
Share on other sites

It's the same functionality, it's just theme stuff hasn't landed (and there's still going to be a titlebar, people didn't like it when Safari did it)

The OS X build got it months ago, long before the Windows build. It's just used for light weight themes at the moment.

Link to comment
Share on other sites

It breaks the webpage up into different parts based on their position and how they move, and render each part into a separate part of memory.

For example, a fixed background image would get it's own layer, and the text content on top would have it's own layer. When the browser scrolls, all it now has to do is copy the text layer over the background layer in a different position, vs. re-drawing the text layer from scratch.

In effect, it reduces the need for the engine to repaint parts of the page, meaning all it ever really has to do is blend images together (which is also what graphics cards are very good at, which is they they eventually want to use OpenGL and Direct3D for all rendering).

Link to comment
Share on other sites

It breaks the webpage up into different parts based on their position and how they move, and render each part into a separate part of memory.

For example, a fixed background image would get it's own layer, and the text content on top would have it's own layer. When the browser scrolls, all it now has to do is copy the text layer over the background layer in a different position, vs. re-drawing the text layer from scratch.

In effect, it reduces the need for the engine to repaint parts of the page, meaning all it ever really has to do is blend images together (which is also what graphics cards are very good at, which is they they eventually want to use OpenGL and Direct3D for all rendering).

Sounds good. Firefox's scrolling is very disappointing compared to opera's, especially on fixed image pages. (well at least its nor as horrible as chrome's)

Link to comment
Share on other sites

Yeah, it's similar to what other browsers do, but smarter.

Layers will also allow for 3D transforms, and hardware accelerated SVG filters (implement them as shaders, attach them to the layer for the object with the filter applied, let the GPU do the rest)

Edit: Eventually of course, probably not in 4.0 final. It'll make stuff like TabCandy pretty damn fast though.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.