> "Next major version" refers to that of Firebug, which will probably be out
> in a couple of months. It *will* have minVersion >= 29,
>

In other words, I'll never be able to run it, because I'm not downgrading
to Australis.

but seriously, don't worry, Australis is quite okay,
>

No, it's not okay. It's part of the general trend of over-simplifying
everything to cater to the mass audience, and screw the geeks and the
content creators. It's a trend being pushed by Apple, Microsoft, and now by
Mozilla. I test in lots of browsers, but if I wanted to use Chrome as my
primary browser, I would. Why should I run a Chrome wannabe?

The arrogance of Mozilla is stunning. They seem to think there's something
special about Firefox itself -- but actually the only thing that's special
about it is the amazing extensions ecosystem, which Moz itself does not
create, and which Moz's behavior often breaks. Many of those extensions
(including most of the ones I rely on) need a status bar and custom
toolbars and menus... you know, visible furniture. And also there's no way
I'm going to use a browser that crams the address bar, bookmarks, icons,
whatever into a single cramped bar at the top in the name of some misplaced
"minimalism."

and there are addons that give you the old appearance back.
>

I know, but very addon I add -- and I use many -- complicates keeping the
whole show running. New incompatibilities crop up. Moz breaks stuff. I have
to spend a lot of time testing every new update because of all the
interactions. I don't want to rely on extensions for something as basic as
toolbars. For example, is Chris Pederick's Web Developer toolbar still
going to be able to have its own toolbar in Australis? I asked him on his
forum months ago and he didn't know. The alternative, presumably, would be
something like his version for Chrome, which disallows those kind of
toolbars. The Chrome version is _clearly_ inferior to the Firefox version.
And so on.

Keeping with an up-to-date browser is important.
>

Getting my work done is important. I'll install the latest Firefox in my
Windows VM, since that's just for testing, but my development Mac
environment will use whatever tools I find the most powerful, even if
they're not the "latest." Not everything gets better; most things do, but
some things get worse. So I guess I'll be locked out of the latest versions
of Firebug too. Great.


> For the second error, can you post a link to some page online where that
> message can be reproduced, and somewhat more detailed instructions? It
> sounds like it's something like Firebug trying to copy styles from the page
> and failing because of CSS oddities, which isn't anything to worry about at
> all but clearly still ought to be fixed if possible.
>
>>
Unfortunately I can't, because it's running on a development server (not on
the Internet) and the project hasn't been made public yet. I can tell you
that those weird errors don't appear from the identical pages when viewed
in the Windows 7 versions of Firefox and Firebug. They only appear on the
Mac -- same pages, coming off the same development server, same behavior on
my part (clicking page components with Firebug's Inspect Element tool). Of
course, since Mac FF is my main development environment, I have far more
extensions installed there, so it's possible this is some kind of extension
interaction, in which case I'll probably never track it down. This all
seems to be going downhill fast.

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/firebug/CAJ-Ow5Bxs%2BucnnBBekni_q33Ph636VDyDr5h5sUK4MJNg%2BuaUw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to