Updated Firefox 1.1 changelog
I updated and reorganized the unofficial changelog for Firefox 1.1. Boris helped by suggesting core changes to include.
I updated and reorganized the unofficial changelog for Firefox 1.1. Boris helped by suggesting core changes to include.
May 17th, 2005 at 6:52 am
I think bug 239218 should be added to your list, very painful mac-bug.
May 17th, 2005 at 7:01 am
And maybe bug 220589 as well.
By the way, was bug 238099 targeted at Web Developers?
May 17th, 2005 at 7:44 am
I added those two Mac bugs and moved 238099 from the Web Developers section to the New Features section. Thanks.
May 17th, 2005 at 8:05 am
The “API for prioritizing HTTP connections” is actually used to load inline images with lower priority. This helps make the browser more responsive to link clicks while a page is loading. It is important to note that this prioritization is for requests to the same host. Prioritization of requests across hosts is not implemented. The idea here is to make the browser handle the cap of no more than 2 persistent connections per host more effectively.
May 17th, 2005 at 9:26 am
Bug 76197 is fixed for Windows and Linux, but not yet for Mac. See bug 274036.
Also, why is this in the web developer features section? IMO, it’s simply a bug fix.
May 17th, 2005 at 12:51 pm
Bug 247884 was fixed in Firefox 1.0.3 which is a branch build and backported to the trunk.
May 17th, 2005 at 2:41 pm
Darin – That happened in bug 278531, right? I guess I need to read that bug.
Thanks, Uri and David. I’ve made those changes.
May 17th, 2005 at 2:58 pm
Nothing about Xforms?
May 17th, 2005 at 4:40 pm
XForms isn’t built into Firefox, and for the foreseeable future it will be made available in extension format only. That’s why it’s not in the list – it’s an extra that’s not in the default build.
May 17th, 2005 at 5:19 pm
Bug 251418 is not a new feature.
> ——- Additional Comment #9 From Scott MacGregor 2004-07-15 09:47 PDT [reply] ——-
>
> fixed on the trunk and the aviary 1.0 branch
May 17th, 2005 at 5:32 pm
231062 – this is merely a wrapper for the FX install; not a real MSI
245392 – Reopened
238099 – This is in 1.0.4. I use it in my userContent.css already
May 17th, 2005 at 6:23 pm
alanjst: bug 238099 has never landed on 1.7/aviary1.0, you’re probably using URIid
May 17th, 2005 at 11:30 pm
I added XForms-as-an-extension and XTF, and took care the last three comments.
May 18th, 2005 at 9:10 am
On my mac the scrollbar on the right just looks like a long grey strip. I think this definitely needs to be fixed. No matter how good the browser is in other respects, this bug still makes it look completely unprofessional. I’m sure that there are many large institutions not adopting firefox because of this bug alone, just because it makes it so obvious that it is a flawed product from the second you open it.
May 18th, 2005 at 2:28 pm
The online copy of alanjstr’s userContent.css has no uriid-type ids/classes in it … it has 238099-type declarations :
@-moz-document domain(mozilla.org) {
a[href*="mozilla.org"]:before {
content: "";
}
}
May 18th, 2005 at 2:30 pm
Is Alex Krupp using a Mac-specific theme ?
If not his / her scrollbar will be grey, because Mac still has a different scrollbar binding from Win / Lin : ]
May 18th, 2005 at 2:58 pm
I tried using @-moz-document in 1.0.4 and it didn’t work. Also, the bug says it wasn’t checked into Aviary. I have no idea why it works for alanjstr in 1.0.4.
May 18th, 2005 at 2:59 pm
Is there a bug report in Bugzilla about the problem with scrollbars on Mac?
May 19th, 2005 at 9:30 am
Jesse: I never submitted it because I assumed it was already widely known. Here is a pic of my firefox. I am just running a standard PowerBook G4 with Tiger 10.4.1 and no system modifications or anything like that.
May 19th, 2005 at 2:27 pm
http://developer-test.mozilla.org/docs/What%27s_New_in_Deer_Park_Alpha is a copy of new “New Features” sections with better descriptions. Deb Richardson created the wiki page, and descriptions have been added by Gavin, Doron, Benjamin Smedberg, and “Editmonkey” (who is that?).
May 19th, 2005 at 2:36 pm
That’s Phoenity – not the default Mac theme of Pinstripe … I don’t think cheeaun does a Mac version.
userChrome with
/* Mac scrollbars *//* ::::: scrollbar ::::: */
scrollbar {
-moz-appearance: scrollbar;
-moz-binding: url(chrome://global/content/bindings/nativescrollbar.xml#scrollbar) !important;
min-width: 16px;
cursor: default;
background-color: white;
}
/* ::::: square at the corner of two scrollbars ::::: */
scrollcorner {
-moz-binding: url(chrome://global/content/bindings/scrollbar.xml#scrollbar-base);
cursor: default;
background-color: white;
}
/* :::::::::::::::::::::::::::::::::::::::::::::::::::::::: */
/* ::::::::::::::::::::: MEDIA PRINT :::::::::::::::::::::: */
/* :::::::::::::::::::::::::::::::::::::::::::::::::::::::: */
@media print {
html|div scrollbar {
-moz-appearance: scrollbar;
-moz-binding: url(chrome://global/content/bindings/nativescrollbar.xml#scrollbar) !important;
min-width: 16px;
cursor: default;
}
}
AND
userContent.css with
/* Mac scrollbars *//* ::::: scrollbar ::::: */
scrollbar {
-moz-appearance: scrollbar;
-moz-binding: url(chrome://global/content/bindings/nativescrollbar.xml#scrollbar) !important;
min-width: 16px;
cursor: default;
background-color: white;
}
/* ::::: square at the corner of two scrollbars ::::: */
scrollcorner {
-moz-binding: url(chrome://global/content/bindings/scrollbar.xml#scrollbar-base);
cursor: default;
background-color: white;
}
/* :::::::::::::::::::::::::::::::::::::::::::::::::::::::: */
/* ::::::::::::::::::::: MEDIA PRINT :::::::::::::::::::::: */
/* :::::::::::::::::::::::::::::::::::::::::::::::::::::::: */
@media print {
html|div scrollbar {
-moz-appearance: scrollbar;
-moz-binding: url(chrome://global/content/bindings/nativescrollbar.xml#scrollbar) !important;
min-width: 16px;
cursor: default;
}
}
help : )
May 19th, 2005 at 9:22 pm
Chris: That makes sense, thanks for the info. Being not a developer, how do I implement the fix you wrote out?
May 19th, 2005 at 10:33 pm
Alex, I think he’s telling you to add that text to a userChrome.css file in the chrome subdirectory of your profile.
May 20th, 2005 at 8:14 am
And userContent.css … since browser scrollbars are considered content [for some reason].
May 20th, 2005 at 8:57 am
Cool, thanks Chris, it actually works now. I didn’t even realize that this was because of Phoenity before because I hate the default theme so much that it is changed within thirty seconds of installing the browser. Anyway, thanks again for your help. This should really go in a FAQ somewhere :)
May 20th, 2005 at 5:26 pm
Alex: Um, how about you just not install Windows-only themes?
May 21st, 2005 at 2:03 am
The Mac theme scrollbar issue is bug 222654 (“global/scrollbars.css for native scrollbars different on mac”), in case anybody is interested in voting for it (or fixing it).
May 21st, 2005 at 3:01 am
The intentional removal of the CMD-arrow page forward and backward functionality on the Mac is absolutely maddening. I’ve avoided using a mouse to browse the web since I was running Lynx in 1992; I’m not going to start now. It’s hard to understand why Firefox has become increasingly unusable since v.0.8, the last time all the keyboard shortcuts actually worked. If functionality keeps arbitrarily being removed for no conceivable reason, pretty soon it’ll be as useless as Navigator 6.0 was.
May 21st, 2005 at 7:23 am
amake: I just went to the phoenity download page and it said nothing about windows.
May 21st, 2005 at 7:16 pm
the command arrow problem in Firefox Mac is bug 291516.
The new shortcut creates many problems for people using non-US keyboards
May 22nd, 2005 at 1:26 am
http://www.phoenity.com/firefox.html states :
Sub-skins
The Phoenity theme is very customizable. To further enhance the look of this theme, please go to the Phoenity Sub-skins page.
Then http://www.phoenity.com/subskins.html has :
Using Phoenity on Mac Firefox, the scrollbar is buggy. To fix this, Mac users must add the following codes to both userChrome.css and userContent.css:
@import url(“chrome://browser/skin/subskins/macscrollbar.css”);
Which will be neater than my fix above.
May 28th, 2005 at 2:01 am
Hmmm. I swear my userContent.css worked with 1.0.3. And then I upgraded to 1.0.4 and that mozilla.org rule stopped working. I’ve seen it work, I swear! And I’ve never used trunk after 1.0 came out.