 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 17 Jul 2008 14:39:42 +0100, Orchid XP v8 <voi### [at] dev null> wrote:
><Warp> You should demand your money back. </Warp>
I did, but want to charge me a 15% restocking fee!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 17 Jul 2008 10:02:13 -0400, Kyle <hob### [at] gatenet> wrote:
>I did, but want to charge me a 15% restocking fee!
Please insert "they" in the appropriate location.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> I did, but want to charge me a 15% restocking fee!
>
> Please insert "they" in the appropriate location.
That's OK - 15% of 0 is approximately 0. ;-)
(BTW... I went to a shop and asked for a GA K8N-Ultra393, and they gave
me a GA K8NU instead [because they had one in stock]. When I complained,
they wanted to charge me a *50%* restocking fee. (!!) And it was them
that stuffed on in the first place! It was an expensive board too...)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Kyle <hob### [at] gatenet> wrote:
> At home, I upgraded to version 3. Now, I can't get DOM Inspector to work, no matter
what I try. I finally gave up for now and will wait to see if the next update helps.
OTOH, there are about 5 billion extensions of Firefox. Should Firefox 3
wait for all of them to be upgraded and tested before publishing?
(No, I don't know if the DOM inspector is produced by the same team which
is in charge of the main Firefox browser, but I assume it isn't.)
I'd say on the contrary: Publishing puts pressure on the authors of the
extensions to update and fix them.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17 Jul 2008 11:18:54 -0400, Warp <war### [at] tagpovrayorg> wrote:
> OTOH, there are about 5 billion extensions of Firefox. Should Firefox 3
>wait for all of them to be upgraded and tested before publishing?
No, and I'm not laying blame on Mozilla for releasing FF3. However, DOM Inspector is
supposed to be compatible with FF3, and FF3 give it the thumbs up when it is
installed. It just doesn't work for
me, so I get to complain. :p
> (No, I don't know if the DOM inspector is produced by the same team which
>is in charge of the main Firefox browser, but I assume it isn't.)
I believe the Mozilla team maintained the version for FF2, but I'm not sure about the
new version. As a matter of fact, I think that the DOM Inspector was an optional
component during the
installation of FF2, but not so for FF3.
> I'd say on the contrary: Publishing puts pressure on the authors of the
>extensions to update and fix them.
It's supposed to be fixed. The version for FF3 is new.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 17 Jul 2008 15:14:03 +0100, Orchid XP v8 <voi### [at] devnull> wrote:
>That's OK - 15% of 0 is approximately 0. ;-)
Exactly. :-D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 17 Jul 2008 08:10:28 -0400, Kyle <hob### [at] gatenet> wrote:
>Since I've had issues with DOM Inspector in version 3, I haven't upgraded from
version 2 at work yet. Now, an update that was rolled out to version 2 has broken
another feature that I use allot, the
>ability to launch multiple URLs from a shortcut by adding a pipe character between
each URL.
The latest update to FF3 breaks this too.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
My own Firefox 3 experience:
I go to getfirefox.com. Redirects me to mozilla-europe.org/es or something,
with a huge button to download Firefox 3 in Spanish (Spain). I'm in
Argentina and would hate to see File called Fichero instead of Archivo and
other spainisms...
Couldn't find the link to see the list of all languages.
I noticed my Firefox 2 was configured to send es-es in the accepted language
list. So I change it to send "es-ar, es, en-us, en" as I want it. Reload
getfirefox.com. Now it shows the page in English. Way to go! Particularly
since that "download Firefox 3 today and help us get in the guinness book"
was featured in a local newspaper; who would then get that bad website user
experience...
Finally I find the link to see all languages. I download the "Spanish
(Argentina)" version. The installer tells me that $brandSohrtName is
currently running and I have to close it first. How did they NOT notice
that typo? I decided to close the installer instead and stay with Firefox 2
on that machine.
I *hate* the new huge back button anyway :)
On my main machine, I run Linux, and Konqueror as main browser.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Quote:
>
> Kyle <hob### [at] gatenet> wrote:
> > At home, I upgraded to version 3. Now, I can't get DOM Inspector to work, no
matter what I try. I finally gave up for now and will wait to see if the next update
helps.
>
> OTOH, there are about 5 billion extensions of Firefox. Should Firefox 3
> wait for all of them to be upgraded and tested before publishing?
>
> (No, I don't know if the DOM inspector is produced by the same team which
> is in charge of the main Firefox browser, but I assume it isn't.)
>
> I'd say on the contrary: Publishing puts pressure on the authors of the
> extensions to update and fix them.
DOM Inspector used to be bundled with Firefox. I don't know if that changed in v3.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Alvarez wrote:
> I *hate* the new huge back button anyway :)
I will say that I like in FF3 how the Ctrl-+ key actually makes
everything bigger, rather than just the text. Now I can actually make
3-point web sites comfortably readable without completely destroying the
layout.
And whose bright Web 2.0 idea was it to start writing web sites in grey
on black or light grey on white? :-)
--
Darren New / San Diego, CA, USA (PST)
Helpful housekeeping hints:
Check your feather pillows for holes
before putting them in the washing machine.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
