Recommended Posts

I posted the following on mozilla, but I thought it would be good to post it here too.. thanks for your time.

I did a search and posted in the nightlys area, but I'll ask here too, as in the nightlys it's being ignored.

TO THE POINT: Is the sanities button suppose to remove cookies that are marked as allowed under exceptions?? Another words, if you chose to sanities cookies should it remove them all or just the ones that you don't have marked as allowed under exceptions? Because I tested this and it removes them all..and I would think the ones you have marked under exceptions to be allowed shouldn't be removed when you sanities. Any thoughts on this??

Yeah, I just noticed that this 1.0+ version of FF looks like what 1.1 will be... because I read the new 1.1 features like a month ago I think, and even when I downloaded 1.0+, I did not have the new option menu for example. Anywa, now it's there, just that it's messy and I can't do anything, but I'll just give them some time to make at least a BETA version ;)

Actually... I was using the noia eXtreme skin (the latest) and it probably just doesn't support the latest alpha/beta things in Firefox. The normal skin works great, but I can't wait until they integrate their fade in and out effect (like the Macs) in the Options menu !

585552218[/snapback]

ya only works with the default theme. Also, set 'browser.preferences.animateFadeIn' to true in about:config

I haven't tested it as I'm too lazy.. but it should remove all cookies as removing all but

'exception' cookies function is already in firefox

585552376[/snapback]

I filed a bug for not removing cookies on exception list

ya only works with the default theme. Also, set 'browser.preferences.animateFadeIn' to true in about:config

I filed a bug for not removing cookies on exception list

585553660[/snapback]

Thanks, I think it makes it usesless if it removes cookies you want to keep. btw, can you post a link to that bug so I can vote on it?

PsykX try using this bookmarklet for bugzilla, easy way to copy bug# plus title...makes things a lot easier on everyone.

javascript:(function() { var title = document.title; function htmlEscape(s){return s;}; var OS=document.getElementById(%22op_sys%22).value.substring(0,3);var PR=document.getElementById(%22product%22).value;var comp=document.getElementById(%22component%22).value;if(comp==%22XForms%22||comp==%22SVG%22||comp==%22Editor%22) PR=PR+%22:%22+comp;;document.write(%22<form name=f><textarea name=ta cols=120 rows=5></textarea></form>%22); document.close(); document.f.ta.value = %22[url=%22 + location.href + %22]#%22 + /\d+/(title)[0] + %22 [/url][%22 + PR +%22]-%22+htmlEscape(/-.*/(title)[0].slice(2)) +%22 [%22+OS +%22]%22+ %22%22; document.f.ta.select(); })()

Go to Bookmarks->Manage Bookmarks->New Bookmark, add above code as the address. Open up any bug report on bugzilla and then open the bookmarklet in a new tab and copy the code. :)

Sorry, I should have posted the url and the title.

I didn't know it was a duplicate though, but I really can't wait til it's fixed, some people may think it's because of me but it's not :)

#284537 [Firefox]-the accent in the address bar should become %e9 instead of %C3%A9 [Win]

#284474 [Core]-IRI and parity with IE which has only half-baked IRI support [All]

There's a solution already in about:config, it is to turn off network.standard-url.encode-utf8, but the ones who go to my site don't know about that. Most of them don't know a thing about computers, they just know how to click a link and browser the net ;)

Is this because that option increases the general security of Firefox?

blocking those flash pop-unders with firefox

There's been quite a lot of buzz around the blogs the last couple of weeks with people seeing the return of the pop-ups and pop-unders. It looks to me like the overwhelming majority of these are from plug-ins, mostly flash.

A number of pundits and bloggers have been wondering aloud whether or not we'll be able to keep up with the pop-up spammers now that more of them are focused on us. Well, we shipped 1.0 with the capability to block these pop-ups and pop-unders but we didn't enable it because we were concerned about breaking legitimate uses. If you'd like to turn it on, it's a fairly simple change -- and would be absolutely trivial for us to enable once we determine whether or not lots of websites are depending on the feature.

To block pop-ups from plugins, open your Firefox 1.0 or 1.0.1 browser, type about:config in the address field. Right-click in the resulting config page somewhere and select New -> Interger. Type privacy.popups.disable_from_plugins in the resulting dialog, hit OK, type 2 in the next dialog and you're all set.

This pref can actually take three values:

    * 0: open allowed

    * 1: the opened windows are treated as popups, but they're allowed to open (we limit the number of these types of popups)

    * 2: the window is a popup, block it

you turn this on, please let me know how it works for you so we can make the decision about offering it to users who aren't likely to be hacking in about:config.

  • 2 weeks later...

Update: Haven't updated in a while so most of this news you guys probably already heard.

Mozilla Suite is being discontinued by the Mozilla Foundation and will now be a completly community driven project. Firefox will now be the main developeing core and main browser along with TB as the mail client. Read more...

-----

There will now be no Thunderbird 1.0.1 release and will jump to 1.0.2 and release alongside Firefox 1.0.2 release. Read more...

Test builds are avaiable for both Firefox and Thunderbird

Firefox:

Windows

Linux

Mac

Thunderbird:

Windows

Linux

Mac

-----

I reported earlier this week on neowin about how Yahoo! plans to support Firefox with all of their services. The original story was posted by Yahoo! Australia and later that week Yahoo! US (parent company) clarified the statement and says that most of yahoo! services will work with Firefox but not all of them Read more...

Edited by supernova_00

Update:

1) Source: Ben Goodger's Blog

Extension Manager Changes

I've been making a large number of changes to Firefox's Extension Manager over the past week or so, basically rewriting the way Extensions are installed. These changes when complete will offer a lot of improvements for Extension developers. Here's a quick summary of what I'm doing:

    * Currently you can only install Extensions and Themes into the extensions\ directory under bin\ and profile\, and the assumption that these are the only two Install Locations is made across the Extension Manager. My changes replace this boolean setting with configurable Install Locations. It will be possible to register additional Install Locations with the Category Manager for discovery by the Extension Manager. This means it will be possible to create special kinds of Install Locations that suit the needs of your XULRunner application, e.g. an Install Location object that represents a Windows Registry key with GUID to path mappings instead of the traditional containment relationship.

    * You will be able to install extensions by simply dropping their XPIs into containment relationship Install Locations (e.g. drop foo.xpi into profile\extensions and have it be installed automatically on next start) - this should be a boon for quick setup.

    * You will be able to install and uninstall Extensions by simply adding and removing their GUID folders from the Install Locations - if you add/remove an entry, the Extension system will notice the discrepancy on the next start and configure/remove the item.

    * You will be able to "point" to extensions which you are hosting elsewhere using a cross platform text format which is basically a text file with a GUID name in the extensions directory with a path to the directory where the Extension actually lives (e.g. elsewhere on a NFS home dir)

    * The system will be more robust about upgrades, file removal, etc, and the API a little saner.

At some point it would be nice to abandon the per-type roots in the RDF graph, and the RDF XML text storage format itself, but my patch is already over 300K and I don't want to tempt fate.

2) There will be no longer be zip builds for final builds (ie 1.0.2, 1.1, 1.5 and 2.0) Installers will be the only way to install firefox or TB. I kinda agree with their decision but think they should have come up with a better idea then just abadoning it. Although the nightlys will still have zips you could always search the ftp for the same day nightly only difference is it won't be signed.

3) Firefox 1.0.2 is just about ready for release ;)

Edited by supernova_00

Sorry I haven't updated the graphs lately. I've been really busy!

Updates:

freezing in a week

The Mozilla development trunk will be freezing in one week for Gecko 1.8b2 delivered via Firefox and Thunderbird 1.1 alphas. If you've got anything scary left that needs to land for Gecko 1.8 or Firefox and Thunderbird 1.1, now's the time to do it. We'll be ramping down on risk and focused on cleaning up what we have from then on through the branch and releases.

Source: newsgroup
Mozilla Foundation Pays Out Bug Bounties

The Mozilla Foundation has awarded bug bounties to Michael Krax of Germany. Krax found five security bugs relating to chrome privileges, meaning that he received US$2,500 ($500 for each individual bug). The Mozilla Bug Bounty Program gives cash rewards to those who find critical security bugs in Mozilla code and report them to the Mozilla Foundation. Launched last year, it's based on a similar programme Netscape used to run.

Source: Mozillazine.org

Updates: Finally updated the graphs, sorry for the delay and flatlined for the past week...haven't had time to update.

and also

Firefox 1.0.3 testing candidates

We're working on another Firefox 1.0 update and could use some help in testing these bits.

The first thing that we've fixed that we need your help testing is the Windows "Add or Remove Programs" bug that caused a doubling up of uninstall entries. This new build should behave correctly, in that if you install it on top of an older release, it will replace that older release's entry rather than add a new one.

The second area that we could use your help testing is manual installation of plugins. If you can find sites that offer plugins which we don't support with the Plugin Finder Service, then clicking on the puzzle piece or the "Install missing plugins" button in the information bar should result in a Plugin Finder Service dialog with a "Manual Installation" button which should take you to the web page for manual installation. If you can find cases where that doesn't work, please let me know.

Lin || Mac || Win

Edited by supernova_00

Update:

Trunk Freezes Tonight for Mozilla 1.8 Beta

The main Mozilla development trunk will freeze at midnight tonight (Pacific Daylight Time) in preparation for the release of Mozilla 1.8 Beta, which will be delivered in the form of Mozilla Firefox 1.1 Alpha and Mozilla Thunderbird 1.1 Alpha (names subject to change). The freeze will remain in place until the Gecko 1.8 branch is created. During this time, all checkins will require approval from [email protected]. See our previous article about 1.8 for more details.

After this freeze the branch will once again be the stable, older code. The branch is used to stablaize and finalize builds for release in which this case will be Firefox 1.1 in late summer. The trunk will continue to be the newer code but also chance to be less stable but always newer code and features.

  • 3 weeks later...

Just wanna give some updates. A few days ago a 'Check for Updates' menu entry was added to the Tools menu. Two days ago the extension manager was rewritten, I posted the info on the changes on the first page. Soon the code will be completly checked in for instant back and forward. And also the code for drag-and-drop reordering of tabs will land.

Also check out info for the new rendering engine that will used for all mozilal products in the future. http://www.mozillazine.org/talkback.html?article=6498

Just wanna give some updates. A few days ago a 'Check for Updates' menu entry was added to the Tools menu. Two days ago the extension manager was rewritten, I posted the info on the changes on the first page. Soon the code will be completly checked in for instant back and forward. And also the code for drag-and-drop reordering of tabs will land.

Also check out info for the new rendering engine that will used for all mozilal products in the future. http://www.mozillazine.org/talkback.html?article=6498

585832291[/snapback]

wow, coming along nicely.

Cairo looks sweet :happy:

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

    • No registered users viewing this page.