This is a tracking bug for bugs that drivers@mozilla.org consider important to the success of Mozilla 1.2. Please do not change the dependencies in this bug unless you are a driver.

Nominating: bug 23679 and bug 35159 (NTLM auth bugs) bug 41924 (top100, has a patch and approval) bug 45375 (usability) bug 47475 (has a patch and is often duped) bug 158457 (regression which makes <script> unavailable in XSLT output) bug 161109 (especially for less annoying <marquee> support) bug 173010

Nominating bug 170143: Page Info has no information in Media, Forms, or Links tabs

My nominations: Bug 131456, Bug 171681 and Bug 174760 (probably overlapping or duplicates): memory leaking when closing tabs or windows, or when viewing JPGs In my eyes, this has a serious impact on the user reception of the browser: depending on the content of the opened URLs, I sometimes exhaust almost 200MB of virtual memory within half an hour, and have to close and reopen Mozilla in order to be able to continue. Probably, a lot of the memory footprint complaints are, at least partially, caused by this problem.

Nominate: Bug 117385 Can't delete/rename a folder with name containing 0x5b/0x5d/0x7c This bug is critical for Japanese environment. Mail messages will be lost!

Nominating... Bug 50511 scrolling/app switching under mouse should cause mousemove Bug 51683 Unable to have 2 differently named bookmarks for the same url. Bug 87410 drag in selection in URL bar should start a new selection instead of dragging text Bug 126730 full screen: problem with maximize/fullscreen/restore Bug 146859 File Bookmarks (CTRL+SHIFT+D) default vertical size is too small Bug 166428 "Sending request..." reappearing after "Done" in status bar Bug 167335 Cut, copy and paste of bookmark failed

nominating bug 173703. it's a serious regression which can completely break tabbed browsing. bug 173953 is another serious regression, which looks to have missed the boat on 1.2beta. and while i'm writing... could everyone stop nominating age-old bugs that aren't being worked on and aren't of stop-ship importance? nominations here aren't "i think this bug should be worked on", but "the release needs to be delayed until this bug has been fixed".

I nominate bug 162986 - the JavaScript console does not show many JS errors and warnings. With this bug unfixed, developers can commit buggy JS code without knowing it.

Same bugs i mentioned for 1.2b, cause i really want to sort/use my bookmarks: Bug 139136, [ Set as Personal Toolbar Folder does nothing ] Bug 139396, [ Sorting of Bookmarks doesn't work at all ] Bug 21263, [ Imported Favorites from IE not sorted ] Bug 127479, [ Drag n drop add to bookmark when no other bookmarks present is broken ]

Selected leftovers from Bug 168066 make Mozilla 1.2beta not suck (which is WONTFIX I guess). Some were mentioned above, but for the sake of completeness: bug 11076 *.eml, news://host/article or imap:// should open the article/mail in a new mail window This is a real pain, this bug from the last century, it makes news/nntp URLs almost useless, since the browser window is not able to handle these messages properly, e.g., bug 11076 comment 36. In effect this bug blocks many more other bugs than are listed. There is no hope to support message-ids in news articles as in references without this being fixed. Bug 32571 window.close() can close windows it doesn't own Security issue, very old bug. Bug 41924 Change how layout handles broken images (alt text) Usabilty. Bug 45375 Tooltips should wrap and not disappear off screen. Usability again. Bug 57724 View-source munging pages This bug makes web development a pain. You cannot see where the problem comes from. Simply stated: Mozilla lies about what really is on a web page. Bug 63182 Flash plugin context menu doesn't disappear on click, like other right click menus Very annoying to have the screen overlayed by a menu. Bug 63292 session additions to global history lost on crash has patch and review Bug 70728 Mail Editor adds two blank lines at the end on saving as Draft has test patch Bug 91662 Long strings in mail header cause scroll bars and attachment window to disappear, making message unviewable. The title says it all, makes mails completely unreadable. Bug 93390 "Block images from this server" should identify "this server" It is meaningless to block images if you cannot tell if they come from $goodserver or $badserver. Bug 94118 blocked images are downloaded anyway This makes image blocking almost useless for low bandwidth users. Bug 93426 New news followups/replies are placed last in thread after Get New Messages Actually, a regression Bug 102848 Remove (was: ... in Subject line fix in hand, needs sr=, needs a= Bug 110949 Edit draft destoys quotes This makes the use of the drafts folder useless. Bug 121084 cache: Images requested twice -> "The image cannot be displayed, because it contains errors." message [when "Compare the page in cache ..." set to "every time I view the page"] Very annoying, suggests error which is not there in the image. Bug 131456 Memory use does not go down after closing windows Use many windows and kill yourself. Bug 142196 Cannot get pop email sometimes (if profile is on network drive) Very annoying. Keeps companies away from Mozilla. Bug 143881 No obvious way to prefill form. Having this wonderful feature to prefill forms becomes almost useless if it is so hard to access it. Bug 167047 image blocking dont support image redirection This is heavly used these days and makes image blocking useless. Bug 170116 miscellaneous performance improvements mostly related to image loads This bug just missed it, has patch, r and sr plus target milestone 1.2b. Let me add some long time outstanding features for MailNews: Bug 17483 [FEATURE] implementation of news filters Bug 56301 connect a spellchecker engine for Mozilla Bug 63389 Need options for importing 4.x and Mozilla mails (mbox) Bug 87107 "Get all new messages" in news server context menu Bug 104604 Forward message quoted option missing. Bug 108877 Support <news:msg-id> URLs Bug 140377 Make e-mail address available for attribution line And for the Browser: Bug 62010 Back menu session history should be unbounded Bug 94035 Allow blocking of any media type (flash, plug-in, applet, etc.) by site (like cookies and images) Bug 104142 want infinite Back Bug 140886 Add default system services to prefs.js

I'd like to nominate Bug #174989 : We must have language packs that work. This has a patch all ready to go.

Nominating 171441: Unable to download files - 2002092804 [installer] build for Windows { "...could not be saved, because the source file could not be read."}

nominating: bug 155426 - OS X trunk: download manager never displays downloads bug 154849 - pref for showing single tab is ignored Both are highly noticeable and should have low-impact fixes.

Nominating bug 93426

I'd like to nominate http://bugzilla.mozilla.org/show_bug.cgi?id=76831

I'd like to nominate Bug #171441 which has had 37 dups in the last 7 days according to Bugzilla, so is really high profile. IMHO, this bug is really a regression of Bug #162593 and the infamous COMPREG.DAT problems.

Bug 126592 just looks silly and Mozilla still lies (bug 105292). Both have patches.

I'd like to nominate the following bugs: Bug 149049 - can't send within Excel (big problem for corporate use!) Bug 104237 - Mail windows behind calling application Both of these bugs really impede progress for a corporate user.

Adding [sg:blocker] bugs to dependency list.

Nominating bug 177083 Mozilla does not start on Windows 95 (smoketest blocker)

Nominating bug 176715 - IE Favorites bookmarks are not imported in new profiles.

Nominating bug 176926 - document.image.src= fails (rollovers) - a recent regression that's visible in lots of sites using all sorts of techniques to get images to change (for example when hovered). The bug has a patch with r= and sr= and is just waiting for approval.

Bug 176175 is a regression where IE Favorites are not imported. Mozilla 1.2 would really suck hard if this wouldn't work.

I suck too apparently, I meant bug 176715.

Perhaps this one is rather hard to fix. But it's so much visible by end users that it should be resolved in any final release, imo: Bug 147077 "new message opens with two carets".

I'd like to nominate Bug 177661 -- 2 frame GIFs do not animate I currently have an e-mail to drivers to get approval to back out the patch that caused this regression. This will be a major source of dups if we don't fix it for 1.2.

My nominations are...: bug 32157 Title tips (tooltips) for cropped text (probably the biggest UI *blooper* in mozilla) bug 62586 Need Titletips (or tooltips) for Cropped Text in Message Header Pane (the son of mozilla's biggest blooper) bug 91662 Long strings in mail header cause scroll bars and attachment window to disappear, making message unviewable. (the current patch made it worse! see bug 91662 Comment #218) bug 92380 Context menu in Personal Toolbar incorrect when Sidebar items selected (have you accidentally *deleted an entire bookmark folder* lately?) Bug 56301 connect a spellchecker engine for Mozilla (make testing mail/news on a daily basis emberazing for som uf ous) ;) Bug 169638 front end work for spam / junk mail (Sounds Very cool. I'm drowning in SPAM. See Bug 169638 Comment #121) Bug 72493 support threaded, sorted view (this newsgroups hamperer is ready for a beatin')

I would like to nominate three crypto bugs. They are all regressions. Very annoying regresion: bug 175115 If you use SSL (https, imaps etc.) and connect to a server whose certificate expired, you are repatedly presented the same dialog whether you want to connect anyway. There is no way to connect to the site. You have to cancel to get out of the loop. I tested the patch. (Although bug 175115 is marked fixed, that means only fixed on the trunk of NSS, but the trunk of Mozilla uses a snapshot that does not yet contain the fix). I nominate to include this fix in the snapshot for 1.2. The fix is ready, please read bug 175115 comment 10 to 16. Another very annoying regression: bug 171331 With a lot of existing user profiles, builds from about 1.2 beta interpret the "security trust" stored in the profile incorrectly. As a consequence, - you suddenly can no longer connect to certain sites using SSL, because they are untrusted - signed S/Mime mail messages you receive are displayed as having an invalid signature, although they are valid - you can not send S/Mime messages, because your own security certificate is incorrectly treated as invalid - etc. The fix is ready for checkin and has been tested, please read bug 171331 comment 42 to 61 if you are interested. Annoying regression bug 166655 Some SSL servers do not support communication using the most recent protocol. Those are described as "TLS intolerant". Earlier in the development cycle, the crypto team suggested for security reasons, that we should not blindly retry a connection without using TLS if we expierience a failure on the initial connection attempt. Instead we changed it to a white list of error codes that should trigger an automated retry without using the latest protocol. However, the full list of error codes that should trigger an automatic retry was not yet known. Meanwhile a more complete list of error codes has been posted in the bug. Without taking this patch, connecting to a bunch of SSL sites will simply fail, with no apparent reason. The patch is simple, it only adds more error codes to existing logic. I have not yet sr, but will have it soon. Thanks

In addition I would like to nominate bug 177798 (simple null assignments) that blocks the regression bug 171331.

Nominating bug 56314 :: reverse selection colors when page background is similar to default selection background

I hope this comment is not useless: We will loose many OS X user if we don't fix bug 167663 soon...

Nominating: bug 133534, serious printing issue in RPM builds, patch available

Nominating bug 173072 --- a pretty ugly layout regression (mine) with an easy, albeit band-aid, fix.

Why did you not yet approve bug 175115? Did it confuse you that it is already marked as fixed? The "fixed" state does not apply to Mozilla, but only to main NSS development trunk. Please reconsider bug 175115, better described in bug 171219.

Nominating bug 178401 'Changing screenshots of themes in preferences." which is a simple gif file replacement. Thanks.

Nominating 10872 'Remember last selected message in a folder'. A long standing bug and an absolute pain.

Nominating bug 10872 'Remember last selected message in a folder'.

Nomiate: bug#151084 ==> While saving exporting addressbook, Mozilla forgot extension filename again. bug#150692 ==> Quick Search/Drag-n-Drop card into a list, now duplicate card in PAB bug#151079 ==> AddressBook can not import files with Chinese filename. bug#151732 ==> Reply / Forward Strangly in MozillaMail (1.0 & 1.1Aplha)

Bug 132538 absolutely must be fixed, it's a showstopper for many people.

I would like to nominate bug 90337 "URL bar not responsive to the "Enter/Return" key". This is a real showstopper and makes us look exceedingly stupid.

We might want to consider holding for bug 174197. It seems like the kind of thing that will affect a lot of pages and practically all non-American users (unless it's specific to ISO-8859-1).

> (unless it's specific to ISO-8859-1) .. and also then it will affect quite a lot of people.

I'd really like to see bug 92380 fixed, which causes (among other things) clicking on Delete to delete the completely wrong bookmark, with no feedback that you're doing it. I removed about 5 really important bookmarks this way before noticing the bug. It's got a tested patch sitting there waiting for checkin...

I nominate bug 145141 which is a bad rendering bug not present in 1.1 Final, and will cause news-scroller type scripts (relatively positioned DIV with another DIV inside) to ruin the layout of the surrounding table in a page. I also find bug 104532 an annoyance (status bar doesn't change when switching tabs, even on load completion) but it's not critical for 1.2 Final.

115917 cri Trunk M120B N700 MacOS crash [@ MRJPlugin] 164593 nor DNS: stopping/reloading causes DNS failures? 133770 maj Rendering of IFRAMEs contains framebuffer trash

does anyone care about bug 178152 selecting on a webpage immediately causes core dump if selection includes an image? (all Unix flavors, 8-bit displays) Makes Mozilla 1.2b utterly useless Please at least back out patch RFE/ bug 14835 which causes this havoc

I would like to nominate Bug 32218 (Mozilla needs an updated splash screen). It has fifty votes and would be really easy to fix. Just remove the splash screen by default (as is done for Unix versions) if none of the numerous attached images are usable for copyright or aesthetic reasons.

Nominating bug 179026 (cri, patch, has review, topembed, regression, several dupes) - URL parameter containing non-ASCII characters is not parsed correctly. Patch is one-liner.

Nominating bug 175386 Mozilla 1.2 Final Release Notes Tracking Bug.

Can someone with a recent branch-build check on Bug 179924 ? That would be a blocker.

Bug 95735 was in the dependency list but today it was removed. Is is a security bug (regular users like me are not authorised to see it), is this a good move to remove security bugs to rush the release of 1.2 ? Is not the first security bug who disappear from depenencies, now in list are 7 security bugs (6 solved) and two weeks ago i counted 10.

Nicu Bucule: I have also no access to this bugs but i think this a sercurity busg with a very low impact. (fixed example : You can get the plugin path via JS. about:plugins displays now the plugin without path)

I won't comment on whether it's a good move. The owner says it's minor and plans to work on it for 1.3. I can suggest that you aren't in a position to dictate policy to staff@mozilla.org. If you feel that you are in a position to dictate policy to them, please do so privately by email. If mozilla.org waited for the removed security bugs to be fixed, then it could release 1.2 by about the time when it will probably release 1.3. And if mozilla.org wanted to fix *all* security bugs before mozilla.org made a release, it could probably make a release (call it 1.2 if you like) by say 2020. Maybe 2035 or whenever we have the next overflow problem :-).

If this security bug has really so low impact now, I believe it should be decloaked.

see http://www.mozilla.org/projects/security/security-bugs-policy.html

Matti: As bug 95735 is restricted, we have no means of influencing the unknown reporter and unknown CCed persons who decide the duration of the restricted status in any direct way, except through bugs like this. Sorry for the spam.

If that bug is so low impact, why it was put in the dependency list in the first place ?

I have no access to this bug because I'm not in the mozilla.org security group. I know only that : a) a critical security bug would not be removed b) The bug is old and already in many releases (the next bug is filed on : 2001-08-17) If you want to discuss the mozilla.org security policy do that in the newsgroup or directly with staff@mozilla.org discussions doesn't belong in bugzilla bugs (sorry for the spam -> this is my last comment)

For 1.0 and 1.1, the Debug/QA menus were hidden before the final release (see bug 163246, for example). Those two menu items still appear in the 1.2 nightly builds, even though we're getting very close to a 1.2 release. Also, see related bug 59655.

I'd like to nominate bug 180339. It is a regression, very annoyance if you often send email to people whose name contain offending characters, and have a one-line patch to fix the problem.

nominating bug 180357 (or backing out bug 157669 on the branch). alt-d is interfering with localizations (esp German) this makes it really suck.

Just to clarify comment 60, the "alt-d" accesskey for url bar is hardcoded in the XUL instead of being properly localizable. So localizations that want to use that key for a menu (which the German one does, because that's the access key for the "File" menu in German-language software) get screwed. I doubt that German is the only affected localization.

nominating bug 175324: hang in search (e.g. lxr). this is a regression from 1.1 and has a one-line patch that needs to land.

nominating bug 168516. Until this bug is resolved, Mozilla is very susceptible to 'freezes' in Linux unless you delete the fastload file. There are other 'hang' bugs, such as bug 180469, that will probably be resolved when this bug is fixed.

um.... un-nominating bug 163013 and bug 163018. "Severity: enhancement," need I say more?

I would propose Bug 157062: Filenames with international characters do not show up in Download Manager.

bug 84223 Printing cut off at the right end

I would like to nominate Bug 110655 mac osx: Can't set any Hebrew or Arabic fonts, although appropriate fonts are installed in the system. It is way at the top of Hebrew/Arabic user FAQ list, with a large gap to the next one. And it makes mozilla (and chimera, that has this bug from mozilla) really crippled.

There must be a lot of pressure at the moment, to get Mozilla 1.2 released. I just want to urge you not to give in! It would be a shame if Mozilla 1.2 had a lot of improvements, but the experience was spoiled by a bug that really ought to have been fixed at this stage. It takes time to write good software, but it's also worth waiting for. :-)

I would like to nominate Bug 167152. IMHO it's a good alignment trying to have on all plattforms the same Bugs. Today you can pick multiple files under windows, but not under Linux. It's the most sucking Bug for me.

Shouldn't bug 176715 be a 1.2 blocker? This bug affects all new users to Mozilla. If not fixed this should be in the release notes (to avoid lots of dupes).

I'd like to nominate bug 52821 . It's more than two years old, and now has a fix that noone's complained about in over a month. It's a simple checkin, and would make lots of people happy. Please could you consider it?

I hope bug 52821 gets patched this time. I've had to apply it by hand to every other release.

cancel comment 45 above bug 178152 and bug 124556 (critical, crasher) have been checked into the trunk and the 1.2 branch !

Bug 175939 Where the browser does not display new pages at all, seemingly randomly.

Nominating (FWIW): bug 113536 tooltips don't handle mousedown event because it sucks so much. I trigger the bug every time I try to open a tab using a contextual menu because the tooltip gets drawn over the second menu item in the contextual menu ("Open Link in New Tab"). Apparently I am pre-disposed to left-clicking the menu item after right-clicking for the contextual menu itself. See my 42nd comment in bug 113536 for details (and a workaround). Note that bug 32157 has already been nominated (which bug 113536 blocks). Also nominating for Mozilla 1.0.2 (bug 161807).

1.2 is out and all dependencies are fixed. -> FIXED

Except that patches that were r/sr/approved and checked into MOZILLA_1_2_BRANCH over a week ago (and in the trunk) do not appear in MOZILLA_1_2_RELEASE See bug 124556 for details Any idea?

Bug 182506 deals with the problems that Nicolas mentions in comment 77 (Some checkins to the 1.2 branch seem to have been missed out for the 1.2 release).

Additionally, there are major parser problems due to an incomplete checkout which causes a very big number of bugs, see bug 182500 I suggest to REOPEN this bug and either change the 1.2 release or push out a 1.2.1 in the next 1 or 2 days.

I second comment #79, in that we seem to have code that was checked into 1.2final but isn't in the distributed "version" of 1.2final. Either this bug needs to be reopened, or a new bug needs to be created for 1.2.1. As bug #182506 seems to be the gathering point for code that was missed, maybe it can be used and renamed to "1.2.1 (the real final release)". This needs to be done quickly (and openly) to avoid chaos and the resulting bad press. (NB that last sentence is aimed at AOL/TimeWarner, and not at Mozilla staff and all the volunteers out there).

First step should be to pull Mozilla/1.2 and post some "ON HOLD" announcement on http://www.mozilla.org/ There is no need to let additional people every hour spend time downloading and upgrading to a version that we know is severely broken, only to get them to go through the process again tomorrow to switch to a fixed 1.2.1

The "Stop the Presses" announcement has been posted on http://www.mozilla.org/ Thanks! Transferring the rest of my comments to bug 182506