Recommended Posts

If they went by whatever the community said, nothing would ever happen, everybody has the small things they don't like.

Edit: Some people hate DirectWrite, doesn't mean Firefox shouldn't use it. The increased text quality outweighs the few users who don't like it.

But you can easily disable DirectWrite without any addon or whatever (it's an option in the menus). To me it's unlikely that we'll see option for the UI.

I personally don't expect anything to come out of the UI design for Firefox next. Remember all those concepts that came out for Firefox 4 that looks really good? Now compare that to what it actually look for FF4+, it's garbage. It's just a bunch of XUL horribly squashed together. They should just disband the UX team. Hell, if it weren't for BoneyardBrew and SoapyHamHocks, I don't know if I would even be looking at Firefox right now.

For anyone that is using 13.0 Beta 1, did the new download manager make it in? I know smooth scrolling, new home page, and most visted sites upon opening a new tab made it in, so I was curious about that. I assume it might make it into the final version if it hasn't already been implemented.

But you can easily disable DirectWrite without any addon or whatever (it's an option in the menus). To me it's unlikely that we'll see option for the UI.

Sure (Although that option disables all HWA, you can't disable DirectWrite without disabling Direct2D either), but they shouldn't put every single thing behind a UI visible menu item, the amount of work required would be immense.

People complain about how slow the theme progresses, now think about them maintaining 2-3 themes at the same time, just in case a user hates the new tabs, or new button style, or new site identity block, etc.

I personally don't expect anything to come out of the UI design for Firefox next. Remember all those concepts that came out for Firefox 4 that looks really good? Now compare that to what it actually look for FF4+, it's garbage. It's just a bunch of XUL horribly squashed together. They should just disband the UX team. Hell, if it weren't for BoneyardBrew and SoapyHamHocks, I don't know if I would even be looking at Firefox right now.

If you compare it to the Mockups for Firefox 4, it's pretty darn close. The only difference is really the tabs being "square" compared to how they were more rounded on the edges.

New rounded tabs IMO look great! The default ones we have now IMO are way too plain.

Sure (Although that option disables all HWA, you can't disable DirectWrite without disabling Direct2D either), but they shouldn't put every single thing behind a UI visible menu item, the amount of work required would be immense.

People complain about how slow the theme progresses, now think about them maintaining 2-3 themes at the same time, just in case a user hates the new tabs, or new button style, or new site identity block, etc.

Right, hopefully it can be disabled with an about:config entry.

If i've got enough time later, i'll post you my Firefox Screenshot, to show you how i think it should be done :D

For anyone that is using 13.0 Beta 1, did the new download manager make it in? I know smooth scrolling, new home page, and most visted sites upon opening a new tab made it in, so I was curious about that. I assume it might make it into the final version if it hasn't already been implemented.

No, the new download manager did not make it into Firefox 13 beta.

For anyone else, in the latest Nightly, is the tab strip a little glitchy with the mechanisms it uses to handle overflow? For example, past a certain limit, the arrows are appearing then immediately disappearing with every new tab, and some other glitches.

The bug (see Bugzilla entry here) has been resolved in today's nightly.

Does anyone have this problem on the Nightly wherein when the click-to-play is enabled, the Adobe Reader plugin doesn't work? It displays the "click to play" but when clicked, it does not display the PDF. I noticed this since the click-to-play popped up on the nightly but chose to ignore it, well, since it is in the nightly but it's been there for a while now.

Does anyone have this problem on the Nightly wherein when the click-to-play is enabled, the Adobe Reader plugin doesn't work? It displays the "click to play" but when clicked, it does not display the PDF. I noticed this since the click-to-play popped up on the nightly but chose to ignore it, well, since it is in the nightly but it's been there for a while now.

Possibly a bug , file it.

You can add exceptions for click to play from about:permissions :) or from the dialog

PDFJS development build shows new UI which was shown in a mockup few days ago :)

The scrolling etc is also faster. Clearly a competitive alternative to Adobe's.

pdf.png

(I wish i had OSX , Firefox looks so good! Cant even try hackintosh , AMD/ATI :/ )

Download : mozilla.github.com/pdf.js/extensions/firefox/pdf.js.xpi ( NO RESTART REQUIRED :) )

  • Like 1

Does adblock plus not work for anyone else in ff14 (aurora)? The filter subscription does nothing to block ads, I have to block them manually.

I installed Aurora 14 and ABP on another computer and the filter failed to download the first time so that may be your problem. I went into Ad Block Plus options, filter preferences and it said 'failed' next to Easy List so I selected 'actions' -> 'update filters'.

I've had issues when both Adobe PDF Plugin and PDF.js are installed, where it will display a blank page instead of the PDF, so your issue could be related to that.

This is my problem but only when click-to-play is enabled regardless if FX's viewer is enabled/disabled. Is there another way of "disabling" it so we can check it?

I guess I'll just wait for the new update. The new viewer looks promising.

I installed Aurora 14 and ABP on another computer and the filter failed to download the first time so that may be your problem. I went into Ad Block Plus options, filter preferences and it said 'failed' next to Easy List so I selected 'actions' -> 'update filters'.

It was issue related to XHR2 so now development build of ABP is perfectly fine and uses WeakMap.

did the new download manager make it into 14a2 Aurora? I heard it would be in it but disabled by default

if it did make it, how do you enable it

i guess it did not , anyways u can toggle between the two UIs by


browser.download.useToolkitUI
[/CODE]

(use it in about:config)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now