Mozilla 1.3 Alpha Just Around the Corner
Saturday December 7th, 2002
Asa Dotzler has posted a newsgroup message about the forthcoming Mozilla 1.3 Alpha release. It includes details about the number of bugs fixed and explains how to nominate a bug as a 1.3 Alpha blocker.
#1 How to query for all bugs blocking 1.3a?
Saturday December 7th, 2002 3:03 PM
What am I missing - I want to query all bugs that have the blocking1.3a flag set to a specific value, but cannot figure out how?
#2 Re: How to query for all bugs blocking 1.3a?
Saturday December 7th, 2002 3:47 PM
"What am I missing - I want to query all bugs that have the blocking1.3a flag set to a specific value, but cannot figure out how?"
Go to the Bugzilla query page http://bugzilla.mozilla.org/query.cgi and fiddle with the 'Advanced Querying Using Boolean Charts' bit at the bottom. Choose 'Flag' for the first part, 'is equal to' for the second and enter either 'blocking1.3a+' or 'blocking1.3a-' in the text field.
#3 Re: How to query for all bugs blocking 1.3a?
Saturday December 7th, 2002 4:25 PM
a link to the list of blocking bugs http://bugzilla.mozilla.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&remaction=run&namedcmd=All+My+Bugs&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.3a%2B
#4 classic borders
Sunday December 8th, 2002 6:43 AM
I tried a new nightly build today and sometime during the past week (since my last nightly), the borders around lots of things have changed a lot. The statusbar now looks like other Windows apps, which is good, I guess (never really bothered me that much), but at the same time, there are some pretty major other changes in many areas. Mainly, there seems to be a lot thicker borders in many windows, the Address Book for example. Also, the "to/cc/bcc/reply-to" drop down widget in the mail composition window seems a little.. damaged..
How much of this is unintentional and temporary and what bugs are relevant to this change? I clearly am not very good at searching Bugzilla because I couldn't find anything about this despite considerable efforts.
#5 Re: classic borders
Monday December 9th, 2002 2:21 AM
I noticed that too, though I did not care for the new status bar look. These changes are not within the theme itself-- I do not know enough about Mozilla to know where they come from, but they are not in the theme... the same theme that looked okay on the 11-28 build has these little glitches on the newest builds.
Another error is that the progress bars, in downloads for example, are not "sunken in" like they should be. Also, in MailNews, the tree column headers have a heavy black line above them.
If you delete the -moz-appearance tags in the .css files inside the classic.jar, these changes go away. I have a modified version of classic I use (looks almost exactly like Classic when icons+pictures are selected), and I have put it back to the way it was a week ago. You can see my meager Mozilla page and install my theme at http://home.att.net/~ascaris1/mozilla.html.
#6 Re: Re: What's new in 1.3?
Monday December 9th, 2002 11:49 AM
How about voting for Bug 183929 so that we have a filter after the fact that doesn't take 5 minutes to use?
#7 Scrolling with arrow keys broken
Monday December 9th, 2002 1:55 PM
Scrolling with the arrow keys hasn't worked for over a week. (Right now I have build 2002120908 for linux)
Whenever I load a page and press the down arrow, it jumps to the bottom of the page. The up arrow isn't functional to scroll up. Also an annoying blinking cursor appears when I click in the web page (not on a link). It is similar to the cursor you would see in an editable text area.
Does anyone have a bug ID for this? Bug 181366 is kind of close if it extends over to linux too.
#8 Caret browsing is a feature, press F7
Monday December 9th, 2002 3:21 PM
Arrow keys work for me - 2002120904 Win32
Monday December 9th, 2002 3:30 PM
That makes mozilla suck much less!! Now if only they could get "Back" in the context menus again. (bug 135331)
#9 Password Manager
Monday December 9th, 2002 3:23 PM
Why does my password manager insist that the Title: box of the response is where my username goes? I have a list of choices of all the Titles of all the posts I've posted to mozillazine.org pop up everytime I load this page now.
#11 Re: Password Manager
Monday December 9th, 2002 5:42 PM
"Why does my password manager insist that the Title: box of the response is where my username goes? I have a list of choices of all the Titles of all the posts I've posted to mozillazine.org pop up everytime I load this page now."
The Password Manager works by detecting pages that have a password field and at least one text field. It takes the value of the first text field - in this case the title - as your username.
The best workaround is to let it save your data once and then respond 'Never for this Site' the next time. It'll stop bugging you then but you'll have to remember to correct the title of each post you make.
#12 Works on other sites
Tuesday December 10th, 2002 7:25 AM
And it doesnt fill in the Google search or the bugzilla bug# box on this page. Many other sites it the password manager locates the textbox closest to the password box or something, I think, automatically, but not here, just Title and Password... You think being Mozillazine.org they would make it work with Mozilla... somhow :)
#13 Re: Works on other sites
Tuesday December 10th, 2002 7:59 AM
"And it doesnt fill in the Google search or the bugzilla bug# box on this page."
That's because they're in different <form>s.
"You think being Mozillazine.org they would make it work with Mozilla... somhow :)"
Maybe one day it will be. Perhaps after fetchBuilds has been updated.
#14 I like Asa's explanation here
Tuesday December 10th, 2002 9:31 AM
You nominate a bug by setting the "blocking1.3a" flag to "?". If drivers agree that it should block the Mozilla 1.3alpha release then they will set the flag to "+" and if they're not going to hold the release for that particular problem they will mark it with a "-" flag.
This explanation could be the kernel of a fix for Bug 183758 http://bugzilla.mozilla.org/show_bug.cgi?id=183758 , the Help! link for bug flags doesn't discuss bug flags. I'd write something to fix it but I don't have all the info about what the possible flags are.