We're swiftly approaching the release of Mozilla 1.7.6. You can find the candidate builds at:
Posted by asa at March 19, 2005 03:23 PMI don't know if you're aware of this but your Atom feed keeps claiming to have been updated when there are no new or updated entries in it. Bloglines keeps telling me I've got one entry to read because of it. Is Movable Type re-creating the feed for some reason or what? If you or your host could sort it out it would be one less small annoyance. Thanks.
Posted by: Rory Parle on March 20, 2005 09:48 AMI seem to be having the same problems as Rory... It's not bugging me, persay, but its a little strange since I keep getting my Bloglines notifier telling me somethings new when its not... Thanks!
Posted by: Steve Eyre on March 20, 2005 11:25 AMSame here with my Bloglines account.
Posted by: Chris G. on March 20, 2005 11:43 AMI am having the same problem with 1.0.2 that I had with 1.0.1. I may have a setting wrong (or is it a J-Script problem?) but I cannot use bloglines as my reader. It only works correctly as Bloglines Mobile. When I try to access the full feeds-I cannot open the links in my left side frame (they should open in the Right side frame but
instead they open a new tab). What am I doing wrong? Sometimes it works (especially when Bloglines|my feeds is the first tab placement on the left side).
Is it a Firefox 1.0.2 bug? or is it my ignorance?
TIA
Joel Krumerman
JHK@POBoxes.com or jkrumerman@gmail.com
Coral Springs, Florida
It seems that nightly builds are using Gecko 1.8b but 1.0.2 is still rv:1.7* and this one has problem with catching CTRL+ALT combination (at least in windows), any chance of changing that?
Posted by: pooya on March 20, 2005 07:33 PMI'm a big Mozilla (not Fireox) fan. I've been too distracted by "other issues" to have been a participant in the Moz community.
Now that I know that 1.7.6 may be the last Moz I install for a while, I'd dearly love to see Moz regain full and proper use of its status line before it fades into the sunset.
Somewhere around v1.7 or so, Moz seemed to have gotten quicker, more responsive, but that apparently came, at least partially, due to less-frequent updates to the status line, which made it less useful as a result.
One huge omission is that the progress bar indicator no longer functions at all while sending. Some web forms permit uploading of files, which can be huge, and take a long time, and without that progress indicator, how's a user to know that any progress is occurring over the duration of the upload?
But also the text part of the status line frequently becomes frazzled in normal use, and a "Transferring data from foo.com..." message lingers even after the page has finished loading. If I click on a link and then use the Back button, the problem might clear, or it might change to "Read foo.com". When this occurs, the JS window.status commands seem to get ignored, though plain <a href=URL> tag URLs do appear in the status line as expected.
And, if someone in the Moz world is taking this to heart, and this message has actually been forwarded to or seen by someone who can actually improve the functioning of Moz's status line, one final request:
Netscape always showed me the appropriate URL in the status line as I moused over/down the list of sites under the Go pull-down menu, and Moz never has...
Thanks to all those who've done so much for so many for so little...