waider: (Default)
I've finally given in and run up Firefox on the Mac.

Why?

Because I can no longer access either my online banking or my motor tax renewal forms with Safari. Who'd have thought I'd be driven to open-source technology by a bank and local government?
waider: (Default)
I remember when firefox was the fast, sleek version of Mozilla.

Of course, I also remember when Mozilla was the fast, sleek version of Communicator. And yadda yadda yadda.
waider: (Default)
Here in my Firefox window I have some highlighted text. In my head this is, perhaps, the X Primary selection. For a transient period in time it is also X Cut Buffer 0. From Firefox's context menu I've selected Copy, so it should now also be in the X Clipboard selection. However, in the Emacs buffer I wanted to paste to, it is not in any of these places. I don't know where it is. Why is this, exactly? I've read what is probably the clearest doc available on what should be happening (Note that despite the fact that Emacs has scragged the X Primary selection through a kill operation in another window, the text remains highlighted in Firefox). Someone here is not reading from the correct hymn sheet, and I want them found and shot, because if I select and copy text I fully expect it to be available to the next application that says, "insert clipboard contents here". Of course, it could well be that emacs, in its wisdom, is scragging the X Primary selection, X Cut Buffer 0, and the Clipboard all in one go... gah.
waider: (Default)
or maybe not. It's not the first time I've encountered a persistently annoying bug that isn't being fixed or usefully flagged to the user because for the former case noone is addressing the underlying bug, and for the latter case noone wants to put in a stopgap such as, you know, telling the user what's going on.
waider: (Default)
It's too damned big.

I have a larger problem with the Mozilla family: they all identify their windows as whatever the top-level window is. In other words, for me, the Firefox main window identifies as Firefox-bin, as does the Calendar window. In Mozilla it used be that the browser identified as navigator:browser and the mail client as mail:3pane; now they all identify as Mozilla-bin.

Why does this matter? )
waider: (Default)
The "Menu" key works in Mozilla-on-Linux. I don't think this changes anything about my browsing behaviour, but I certainly wasn't aware of it before.

oh yeah

Aug. 31st, 2004 06:00 pm
waider: (Default)
while I'm whining about cookies... it'd be nice if I could tell mozilla to never, ever accept a cookie of the form "*WEBTRENDS*" or something.
waider: (Default)
If you were to judge by what I'm posting here, I've really been cranky the last few days... right now, and in fact for the last half-hour, Mozilla has been catatonic from a UI perspective. Because I pressed the "Remove All Cookie Sites" button on the utterly useless cookie manager. Now, because I'm an inquisitive soul, I ran strace against it to see what it was up to. As best I can tell, it's deleting the cookie sites one at a time and doing some sort of heavy processing between each delete. Since I had a 20-24k cookie permissions file, and each line is about 50 or so characters, it has been counting slowly backwards from 24000 in fifties for the last half hour. No indication onscreen of what it's up to, no way to interrupt the process.
waider: (Default)
Yay. There's a new version of Flash. Boo, it hangs when I take Mozilla to http://www.doonesbury.com/strip/dailydose/ and click on "previous date". So much for progress. Even the old version didn't do this once I'd allowed it (or Mozilla, I don't know which) to invoke esd despite the fact that I tend to use a perfectly good artsd for my audio serving pleasure.
waider: (Default)
Well, for what it's worth, it appears to be a Macromedia bug somehow. That said, I feel that Mozilla could be doing more to isolate plugin bugs and stop them from hanging up the entire browser (it's threaded; what's the excuse?)cuidados! hay stacktrace! )
waider: (Default)
I have a whole assload of bookmarks. Some of them have been following me around since the late '90s. I try to keep them organised, but there are dupes, dead links, etc. So I thought I'd do a little consolidation with Mozilla. Use the search to find duplicate bookmarks, then delete all but one copy.

You can't do that. For reasons best understood at Mozilla.org, you can't delete bookmarks once the search is active. Actually, depending on your Mozilla version, you may not be able to delete bookmarks at all.

Ok, so plan B. I noticed that the "Move..." menu option was enabled in search mode. So I created a folder called Junk and moved my duplicate bookmarks in there. Then I exited search mode and emptied the Junk folder. Then I activated search mode and searched for the same bookmarks, and lo... there's now an extra copy. Lather, rinse, repeat, and after a few cycles I've got 8 copies of a bookmark that I've been trying to kill outright. GAH. How hard is this stuff to do right?
waider: (Default)
djb doesn't win the case, but won't get prosecuted either. Doesn't really change the current situation any, and the law is still on the books.

VeriSign are bringing SiteFinder back despite complaints and ICANN, claiming it doesn't cause any security or stability problems. Funny, I don't recall too many people complaining about it being a security or stablity issue.

Nihongo no ki-bo-do - I didn't realise there was a QWERTY-equivalent Japanese layout. Or, I guess, a TA-TE-I-SU-KA-N layout.

SCO won't be invoicing you just yet. My cow orker Kevin still hasn't heard back from SCO on what exactly they're selling him a license for, either. Without that, their license is illegal under Irish law.

Mozilla Foundation needs cash is, I think, the subtext here. Also, Netscape Internet Explorer. It is to laugh.

And now, breakfast and more house-hunting.
waider: (Default)
I just got a bunch of mails from Bugzilla because "[bugzilla.mozilla.org]'s policy is not to use [the CLOSED] status. Obviously this is WAY more important than, say, fixing bugs.
waider: (Default)
Phrases like "Let's keep knowledge of the content-type header out of the loader ok?" are hugely unhelpful in the context of the end-user. It's like saying, "Let's maintain ideological code purity at the expense of the user experience, okay?".

May I refer you to an appropriate Jerkcity cartoon, particularly the final frame.

bug

May. 19th, 2003 03:12 pm
waider: (Default)
this page has some broken links. they're broken in an interesting way: when I scroll down to, say, the ICE 5500 link, Mozilla tells me that it's being offered an application/octet-stream file of type "Hypertext Markup Language", and what do I want to do, save or open with some application?

I think it's pretty damned obvious what I want to do, and I can't trivially do it.

Didn't Navigator have a "handle internally" option for crap like this?
waider: (Default)
Mozilla does another about turn.
waider: (Default)
Well, actually I'm lying on the bed typing this.

Anyway.

I just wanted to say that I find Mozilla's new-found anti-aliased fonts disturbing, perhaps because they're badly done. They look for all the world like poorly printed handbill text.

Profile

waider: (Default)
waider

April 2017

S M T W T F S
      1
2345678
9101112131415
16171819202122
232425262728 29
30      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 8th, 2025 04:23 am
Powered by Dreamwidth Studios