Closed Bug 143200 Opened 23 years ago Closed 22 years ago

make RC3 not suck (or "are we having fun yet?" or "last one, really.")

Categories

(Core Graveyard :: Tracking, defect)

Product:
Core Graveyard
Component:
Tracking
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: asa, Assigned: scottputterman)

References

Details

(Keywords: meta) 

This is a tracking bug for bugs that drivers@mozilla.org consider important to
the success of a Mozilla 1.0 Release Candidate 3. Please do not change the
dependencies in this bug unless you are a driver.
Depends on: 70083, 129279
Depends on: 139294
No longer depends on: 139294
Depends on: 128150
Depends on: 139335
Nominating bug 140944 (body.scroll* properties always return 0).
The scrollTop and scrollLeft proporties always return 0. Fixed on trunk.
Nominating bug 135250, "open link in new tab" should be below "open link in new
window" in link context menus.  It would look silly if 1.0 had this bug but 4.x,
0.9.9, and 1.1 didn't.
Depends on: 76431
Depends on: 143503
Added waterson topcrash wallpaper bug 132905.  Jesse, people disagree on the
order of the items.  Without _strong_ consensus, I think we'll be leaving it as
it is.
Depends on: 132905
Keywords: meta
No longer depends on: 132905
Depends on: 132905
No longer depends on: 132905
For RC3 (let's hope 1.0), I would like to nominate :

#120327 : "Sanitize extension-fixup code" ; this bug is driving me crazy :-)

#126782 : "Binary file with unknown type displayed as text/plain rather than
saved" ; I want to see it fixed :-)

#140222 : "Drag and drop of mails do not expand subfolders tree list." ; I
cannot really use mailnews with this one !

#142225 : "Rewrap changes characters" ; very annoying when rewrapping :-(

Hope some on them would be added to the list.
Depends on: 132905
I nominate bug 134535 and bug 137033. Both were nominated by others for RC2 and
are recent regressions. They're also the only bugs I notice on a daily basis.
I'd like to nominate bug 107806, which renders a number of pages unviewable to
people using image permissions.  There's a testcase for it.
I'd like to nominate bug 137223 (PNG background) fixed in trunk.

please, fix the mailto and last visited bugs, their both a major functionality
loss. bug 61893 and bug 119796

I'd like to nominate bug 143250 Imported IE Favorites not resolving
http://bugzilla.mozilla.org/show_bug.cgi?id=76831

Must be fixed, it's driving me nuts :(
Nominating bug 80530, single-pixel rendering error when scrolling document
(120DPI, 125DPI) (with patch); bug 117371, Explanation on Prefs -> Advanced no
longer makes sense (only a change in wording required); bug 123553 (cryptography
regulation compliance); bug 127112, incorrect usage of term "internet" (affects
only help file, with patch); and bug 142590, Add "Do Not Edit" warning to
prefs.js (only a change to the comment in prefs.js, with patch).
I'll join the nomination game:

Bug 127857 - Change Scale Textbox to dropbox (already only needs an a=, plus it
is trunk)

Bug 116394 - Tab Borders Disappear (classic only) (A recent change in
tabbrowser.xml fixed this)
Depends on: 143607
(already only needs an a=, plus it is trunk) - only needs an a=, plus it is in
the trunk. Good lord, that sounded just like JeffK.
I'd like to nominate Bug #129115. This has a fix checked into the TRUNK, and
seems to make a massive differance to the speed of certain functions in Mozilla.

Here is the list of current keywords on this bug : mozilla1.0, nsbeta1, perf,
testcase, top100, topembed-, topperf
nominating following bugs, imho most visible on windows

* bug 133351 (Bookmarks cannot be moved by drag in sidebar)
  also leaves sidebar-bookmarks in a visible inconsitent state 
* seconding Comment #12 
  bug 127857 (Change scale textbox to dropdown (accomodating ``shrink to fit'')
  in print preview toolbar 
   
nominating Bug 143862 - document.write crashes on some pages

This is a reliable crasher on the branch as far as I can tell.
I'd like to nominate the bug 129115 too. It's really serious performance
improvement on pages which heavily use DOM. And I think there is a little window
in time just now on the beginning of the RC3 that we could check it in and look
for the remaining regressions.

I would like to nominate bug 130876, some .gif images don't display. Sometime
since 0.9.8, Mozilla stopped being able to display corrupt gif images such as
this one: http://forum.ngi.it/smiles/insane.gif

It's a small fix and has been fixed on trunk for a few days without problems.
I'd like to nominate some skin/UI "enhancements" which if not in RC3, should 
DEFINITLY be in 1.0.  These are not "BUGS" as people would have you believe, 
rather the way the browser should be and should've been designed from the 
start.

Bug 30579 - "Scrollbar corner" should be skinable (currently always white) 

Bug 123712 - URL drop down should not show arrows for scroll when only one 
match - REGRESSION

Bug 49543 - Separate toolbar from address bar [urlbar] - HAS PATCH(S)

Bug 89350 - Home button should appear on main toolbar - HAS PATCH

The first two bugs don't seem to have much activity, but are pretty annoying 
cosmetic glitches and bug 30579 is a regression anyway, so it should be fixed 
regardless.  The last two bugs have had patches from a long while ago and 
there is no reason for them not to be implemented by 1.0.  I believe many, 
many people would be happier with these checked in for RC3 or 1.0, rather than 
waiting for some toolbar customization that may never happen.  Mozilla is a 
very, very good browser internally, so lets make the outward appearance 
(skins, toolbars) be just as good.  There is a lot of hype about 1.0 - let's 
not give people reason to be disappointed :-)
Tobias: don't wanna spam, so don't answer to that, open a thread in n.p.m.ui if
you want, the discussion doesn't belong in this bug - but:

Bug 49543 - Separate toolbar from address bar [urlbar] - HAS PATCH(S)
Bug 89350 - Home button should appear on main toolbar - HAS PATCH

1) Those are too big change that late in the 1.0 cycle for sure.

2) Not everyone would want that, this is a design decision that we shouldn't do
in such a fast style. I for sure would n't like those personally, and I'd write
some XBL/XUL to get the 'old' way back in my personal builds.
Nominating bug 118846

This is a solaris specific bug in run-mozilla.sh that causes mozilla to hang
hard when loading complex pages (lots of images, etc).

The bug can be fixed by increasing the sized of the shared memort transport from
64k to 512k (which is what sun suggests as a compromise between speed and
resource consumption).
Depends on: 140530
I'd like to nominate bug 120616.
It's very visible and possibly cause crash (bug 137897) ,
and has fixed on trunk.
Depends on: 91795
Depends on: 143912
If I may, I would like to second bug 123712 (URL drop down should not show
arrows for scroll when only one match). It looks very sloppy.
I want to "nominate" bug 144027

Many user have problems (new window doesn't work, Mozilla doesn't start) if
there are old Themes installed but this skin is not active after they upgraded
from RC1 to RC2.
Depends on: 133351
The following 4 unresolved bugs were listed as dependancies for bug 138000 (make
RC2 != suck bug) but they are not listed as dependancies for this bug.  I am not
very familiar with the bugs and I am not sure whether or not they need to be
listed here, but I figured since they were worth listing before, then they might
be worth listing again.

bug 96504
bug 133170
bug 140088
bug 143031

Actually more important to me is that bug 140591 (an OS X regression bug
regarding the "Create Filter from Message" feature) which has been fixed on the
trunk will also be fixed on the 1.0 branch.  Once this bug has been triggerred
it is impossible to exit Mozilla cleanly.  The patch for this bug, which has
been checked into the trunk, also happens to fix bug 112714 as well.

While I am here, I'll go ahead and suggest that bug 133250 be considered for
RC3; this is the bug that keeps leaving "Transferring data from..." on the
status bar even after all data has been transferred,
I nominate the bug 78356 to become RC3 candidate.

I read news via an account on a news server and repeating username and password
over and over again is very annoying.

I don't know if/where there is a bug for that, but I would
say once again that the java section on the release notes
is completely obsolete. for example:

    Mozilla has been tested with all 1.3.0_* versions of the JRE,
    and JRE 1.3.1, and beta versions of JDK 1.4. J2SE releases
    previous to 1.3.0_01 will not work with Mozilla .

JDK 1.4 beta? 1.4 has been released for nearly 6 month now!

    Linux: LiveConnect support now works if you use Mozilla 1.0
    Release Candidate 2 with JRE 1.3.1. Additional LiveConnect
    problems are being addressed in JDK 1.4 as mentioned above. 

Have theses problems been addressed in JDK 1.4 release?
Or should we wait for another JDK release?

Thanks
Cedric

Obviously, this should not just be for Windows -> OS/Platform=ALL

I'd like to nominate:

bug 136345 (To-Field not saved on change), i.e., dataloss making it impossible
to send e-mail

bug 110949 (Edit draft destoys quotes), i.e., saved messages are not usable

bug 59638 (reading news/mail across newsgroups/folders does not load next unread
message), i.e., messages appear to be empty, extremly confusing for the average
user, work-around a PITA

Pro forma all the still open bugs in: bug 138000, bug 134771, and bug 101793.

pi
OS: Windows 2000 → All
Hardware: PC → All
Nominate bug 134745.
Carrying over my nomination from the "RC2 not suck" bug:

bug 30431 - "Intellimouse Explorer Backwards and Forwards button support."
The bug was opened 2000-03-04 11:33, has 35 votes, and has a patch.
[sorry for the SPAM but this looks very serious:]
There are multiple reports
(http://bugzilla.mozilla.org/show_bug.cgi?id=99829#c33 is one of them) that the
JAVA2 plugin support in Mozilla is defunct in the 1.0 branch and none seems to
care about it... ;-(
Release Notes changes can be sent to bug 133795.
I want to nominate bug #135414 about the integration of Mozilla  with
OpenOffice.org. This bug is fixed in the trunk.
Depends on: 136756
No longer depends on: 136756
No longer depends on: 76431
I'd like to nominate :
- bug 135928 (Range.SurroundContent)
- bug 135922 (Range.SplitNode)
- bug 114092 (UninstallPackage)
Because of them, a european project I've made is about to be finished under IE.
:'^(
Please, please, fix them.

I'd like to nominate Bug 144188:  If the sender types <TAB> when composing a
plain-text e-mail, the sender sees what's expected (if you ignore bug 58712) but
the recipient sees either a space or a line break.

A patch already exists.  Tabs are a very basic function (the keyboard should
work!), and it's dataloss (albeit minor) for the sender to see one thing and the
recipient another.  The sender may not even know it happens.
Depends on: 138725
What about nominating bug 133282? Looks like a killer for who uses Mozilla under
win32.
Nominating bug 142515: Printing selection prints all pages on one page.
Depends on: 142113
My nominations:

Bug 103456: javascript window.close should close tab, not complete browser window
Bug 18266: Query IMAP folders other than INBOX for new msgs (has patch w/
review, still waiting for sr)
No longer depends on: 130614
I'd like to nominate: Bug 130174 scrollbars=no ignored for window.open

Its a nasty regression in basic functionality, and it really makes some sites
look bad.
I nominate one of bug 133334 or bug 138826, both of which are about "Can't open
link in email in new window". Why aren't they marked duplicates? This bug is
*very* annoying.

Nominating bug 143764, "Quick Launch enabled but doesn't work", which seems to
be a regression in QuickLaunch between 1.0RC1 and 1.0RC2.
Depends on: 145061
Regarding bug 18266: a fix has now been checked in to trunk and at least wfm.
This is an often requested (has 71 votes) and duped (26) feature.
http://bugzilla.mozilla.org/showdependencytree.cgi?id=128150 pulled.  brendan
needs more time for build foo to get this right.
No longer depends on: 128150
No longer depends on: 140530
don't know how bug 76431 escaped. we need that to get out of the cnet dog house.
Depends on: 76431
No longer depends on: 76431
Depends on: 76431
No longer depends on: 143250
No longer depends on: 70083
I am not having fun while bug 105263 and bug 41502 are alive.
Seconding the nomination for bug 143764. Quick Launch is broken. It doesn't
work. It needs to be either fixed or removed from 1.0.
Seconding the nomination for 134535 and 143250 - the current IE favorites
behavior is not acceptable. If you import a bookmarks.html (say, oh, downloaded
from yahoo), and lose your IE favorites folder, there is no way currently to get
it back.

I'd also like to nominate bug 84272.
Depends on: 145181
olo@altkom.com.pl: Please read the bug before you change something.
Don't change the bug depencys !

BTW: Bug 145181 is only on the trunk AFAIK
No longer depends on: 145181
Nominating bug 137079.  Cookie problems when using "Enable cookies for
originating web site only" preference.
Sorry for spam. My fault :(
Depends on: 135076
Depends on: 139362
adding 142625 for brendan and chofmann.

changing character coding menu in HML ile causes crash. (regression)
Depends on: 142625
adding 133044 for chofmann, brendan.

Single line HTML comments get mangled in textarea
Depends on: 133044
adding 142788 for chofmann, brendan.

Mozilla renders malformed comments incorrectly
Depends on: 142788
Depends on: 133666
Depends on: 142592
How about Bug#143882 ?
The Mozilla doesn't follow RFC822 and it's easy to fix.
Hope it will be fixed in RC3.
Thanks
I'd like to nominate bug 97525 - it's a hang that occurs fairly often for me in
common usage, but I can't work out the pattern. It really sucks!
I'd like to second the nomination for bug 120327, because saving as .rpm.exe,
for example, can be a tad annoying...
Depends on: 133601
I would like to nominate bugs:
http://bugzilla.mozilla.org/show_bug.cgi?id=139843 and (though could be the
same) http://bugzilla.mozilla.org/show_bug.cgi?id=139155
It has not gone, on some previous rc2 nightly builds it hasnt been there .. then
it returned.
No longer depends on: 133601
Depends on: 133601
I would like to nominate bug 132006.
The patch for this bug has been approved by Asa a few weeks ago
(http://bugzilla.mozilla.org/show_bug.cgi?id=132006#c30), but it is still not
check into the branch. It is now waiting for re-approval.

These bugs should also be fixed: bug 116394 , bug 145657 and those print-preview
bugs (there a several bad ones)
What about <a HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=92728">Bug
92728</a>? It's an annoyance for me every day. Because of this Bug I need to use
another Browser for certain tasks as the page doesn't work with mozilla.
putterman, who should this bug go to?
Assignee: asa → putterman
Really, why the bug 129115 is not on the list? I know this one came too late in
the game but to be just 2x slower than IE instead of 10x or so is the big
difference... And also reading that bug and related ones with "this is the only
thing about our horrible DHTML performance we will be able to do for 1.0" all
over the place - what's the point?
This bug tracks the Mozilla stop ship bugs. Not the Netscape beta ones.
It should be assigned to a @mozilla.org staff member and the best indicated
person imho is Asa, since he has done this job carefully til now.
i nominate bug 141023. one of the biggest complaints i've heard from web
designers in the Netscape4 - Netscape6 years is the persistent inability to
distinguish whitespace in content from whitespace in markup when rendering. i
was under the impression that most such bugs had been fixed, but then i
discovered this one. i feel that this bug really ought to make it into a pre-1.0
release since it involves such an elementary browser responsibility.
Matti told me Asa's in Japan (lucky guy!)
I apologize for the spam.
I'd like to nominate bug 73712
This is such a basic UI issue. People need to be able to distinguish between
browser, mail/news and composer on the taskbar with different icons.
I want to nominate Bug 134620 which apparently already has a posted fix
Depends on: 144257
Depends on: 127702
I'd really like to nominate Bug 137223 which is a major regression bug already
fixed in the trunk. This bug breaks the display when PNG images with alpha
transparency are used in DIVs. It would be very sad to have Mozilla 1.0 being
released without support of PNG transparency.
removing 76431, 91795, 127442 which have been fixed on branch
No longer depends on: 76431, 91795, 127442
Bug 144488 needs to be in here - this is the hard-linked themes site you get
when you go View | Apply Theme | Get New Themes . That bug states that we are
already slashdotting xulplanet.com with 0.9.9, 1.0rc1 and 1.0rc2, because eye
candy is popular ... we really can't go live with it still hard-linked and
have the x.themes.org debacle all over again.

That bug contains various solid proposals for new candidates for the hard-linked
themes site. All it awaits is a decision and a patch.
removing following bugs from dependency list which have been fixed on the branch.

129279, 132905, 133351, 135076, 136756, 138725, 139335, 142113, 142592, 142788,
143503, 143607, 143835, 143912
No longer depends on: 129279, 132905, 133351, 135076, 136756, 138725, 139335, 142113, 142592, 142788, 143503, 143607, 143835, 143912
adding 144488 because overloading xulplanet is bad.
Depends on: 144488
I dare to propose bug 116394: disappearing tab borders look unprofessional for a
1.0, the fix (the one for bug 137836 that fixed the bug) is about as long as
this comment and on the trunk already for 4 weeks.
One more bug: the image rights issue. Bug 28028  
I think it should really be solved for Moz 1.0 because it is also legal problem
when shipping Moz 1.0 with questionable images. At least it should be stated
that all the images currently shipped with the Mozilla-releases are MPL/GPL/LPGL.
How about #143882 ?
Mozilla Mail header doesn't follow RFC822...
I think it's easy to fix.
Please don't forget this...
adding 144257 per comment in bug
If there is a chance for bug 129115 to get also on the branch (it has been on 
the trunk doing very fine for quite some time now) that would be a major 
performance boost many would highly appreciate.
Depends on: 143369
nominating bug 92380
its a dataloss bug. ppl will lose their bookmarks
IMHO bug 119317 should be added as a blocker since XBL is an API that people 
will use, so changing it after 1.0 will be not-so-fun/impossible
And the nominations are...:
bug 32157 [RFE] 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
          (what was that subject? - 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.
          (very visible bug - second biggest mozilla blooper)
bug 92380 Context menu in Personal Toolbar incorrect when Sidebar items selected
          (have you accidentally deleted an entire bookmark *folder* lately?)
bug 73712 Need Win32 and Linux/GTK icon files for each window
          (we need icons, man)
bug 22687 [RFE] PGP Plugin
          (e-mail "security", pie-in-the-sky?)
bug 56052 Support PGP in PSM
          (long neglected, but much *voted* for)
I sent an email to Dawn, but got no response. Apologies for the spam.

I'm curious as to why the mass removal of dependancies last night. This is a
tracking bug. I would think that for historical, auditing, and other reasons
that those 17 bug that block this bug but have been fixed on the branch should
remain listed as dependancies.

In my mind this bug should be closed when either all the dependancies are fixed
or RC3 is released. If RC3 is released and bugs listed as dependancies aren't
fixed by RC3 launch that either /they/ are removed from the list as erroneously
there in the first place, or RC3 is deemed "suck". This bug should not be closed
when it magically hits zero dependancies.

This isn't something that has happened to any tracking bug that I've been CC'd
on in the past (including recent "make X not suck" bugs), and I'm a bit
surprised & disturbed to see it happening here.
Nominating bug 86319 - affecting so many sites & portals.

Why remove the dependencies just because they're fixed?
Depends on: 144704
No longer depends on: 145061
fixed bugs are being removed from the dependency list to make it easier
to keep track of which have been fixed on the branch already and which are
still on the radar since a bug's resolution has little or nothing to do with
whether the bug has been fixed on the branch. (and also because brendan asked
me to do it, saying that this is what asa normally does).

If you want to see which bugs have been removed from the list then see the
commends i made when i removed the bug and/or look at the bug activity log
from the "View Bug Activity" link.

removing bug 127702 and bug 139362, which are fixed
No longer depends on: 127702, 139362
adding 145061 to dependency list, per brendan and rjesup.
Depends on: 145061
Depends on: 119317
removing 145061. shouldn't have added in the first place. oops.
No longer depends on: 145061
Depends on: 123123
No longer depends on: 123123
Blocks: 132965
Depends on: 145764
Depends on: 141051
Nomination: bug 136165 - crash with dataloss in Composer. Patch in the bug,
which has r= . This bug gave me four crashes in as many days, those having
been my only 1.0-branch crashes in two weeks ...
Was Bug#132965 fixed ? I don't think so.
Please verify it and see the related bug, #144658...
It's obviuos problem, but it seems no one care about...:-(
Sorry for the spam in advance.
But what is http://bugzilla.mozilla.org/show_bug.cgi?id=143369 ?
I get an Error telling me "You are not authorized to access bug #143369.".
Any reasons?
Are there "not-public" bugs? Critical / Security stuff?
please answer.
Benjamin Schallar: 
This bug is closed because it's a security bug.
It will opened in a few weeks after the bug is fixed.
For such questions ask please in the newsgroups an/or
Irc:/irc.mozilla.org/#mozillazine
fixed bugs dependancies should not be deleted because sometimes they are
reopened and that should be reflected in the tracking bug
http://bugzilla.mozilla.org/show_bug.cgi?id=143200 is closed because of a
security bug?

Then the only way to avoid any security risks is _not_ to use Mozilla. :-(


Answering to Comment #92
AFAIK this security behavior has been discussed long ago. (Does anybody know a
link to a page with a statement about this?).
And IMO it's the right solution to haved closed security bugs that become 
visible(!) after some time. Otherwise Hackers would know about such bugs early
than anybody else.
> (Does anybody know a link to a page with a statement about this?).

http://www.mozilla.org/projects/security/security-bugs-policy.html
Nominating: 
bug 142108 [ Crash when reloading XML+XSLT ]
bug 129115 [ Reflow coalescing within JS called from SetTimeout ]
I'll second bug 142108 - I got it to cause reliable crashes on 1.0 branch
(see bug 146119, a dupe of 142108 with the details). Nasty stuff.
Depends on: 113351, 146333
Nominating bug 130174 (scrollbars=no ignored for window.open) seems essential to
me as it can deeply alter the look & feel of a web application using pop-up
massively.
It can not be consider as a minor bug.
Depends on: 146429
I would like to nominate bug 110112 (Crash after long sequence of image
confirmations) which is causing ask me image permissions to be disabled for the
release.  Many people use this feature to avoid one pixel webbugs in webmail. 
Since this is a privacy feature it would be desirable to have it in 1.0.
I nominate bug 92742 cause not being able to access a SSL site just because you
access the web via a proxy will certainly annoy a lot of company users.

Nominating bug 96877 This one is critical and has dataloss.
I want to nominate bug 128801 'downloading dialog has "-1%" in titlebar'
This one does not reduce functionality, but it gives Mozilla a rather unfinished
look and should be fixed going to V1.0
Nominate: Bug#143882.
It's easy to fix...please...
Since RC3 is now out, I've nominated all the bugs nominated here (and for RC2
and RC1) but not yet fixed for "Make Mozilla 1.0 not suck" (bug 132965).

Should this bug be "resolved fixed" now?
shouldnt this be closed now ?
Fixing as WORKSFORME as the sucking factor is pretty subjective, isn't it? ;-)
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.