Comments from Decius:

The MemeStreams bookmarklets now fully support Safari. You can select text in a window, hit the recommend bookmarklet, and that text will be quoted in your Meme!

In order for this to work you have to upgrade your bookmarklet. You'll find the latest bookmarklets by clicking on "help" in the navigation menu.

Now that I can actually use Safari with my website, I'm going to cut over to it for a while and see what I think. I hope the anti-aliasing doesn't give me headaches.

Now a short rant:

There is one correct way to implement text selections in JavaScript: document.getSelection. Thats how everyone does it. Thats the STANDARD. Everyone, that is, but Microsoft, who decided to implement a text selection object instead of a method. Very annoying. I have no idea why they did this; as far as I can tell there is no technical benefit. Then you've got Apple, who decided to make getSelection a method of windows instead of documents. So now there are three ways to do this.

I understand what Apple was thinking. By putting this under window you don't run into problems with frames.

Then again, I don't understand what Apple was thinking. Safari is not the only browser on the planet! I still have to support the other methods for other browers, I still have to do step through all the frames on a page, so you really haven't helped me at all. My code is more complex, not less complex. More importantly, almost nobody who uses this stuff knows how to make this work effectively. The result is that bloggers can't, and in general, don't use your browser.

In general, and in particular on the internet, being standards compliant is better then being more efficient. It doesn't matter how well your stuff works if no one can use it!

Decius wrote:
] The MemeStreams bookmarklets now fully support Safari. You can
] select text in a window, hit the recommend bookmarklet, and
] that text will be quoted in your Meme!
]
] In order for this to work you have to upgrade your
] bookmarklet. You'll find the latest bookmarklets by clicking
] on "help" in the navigation menu.
]
] Now that I can actually use Safari with my website, I'm going
] to cut over to it for a while and see what I think. I hope the
] anti-aliasing doesn't give me headaches.
]
] Now a short rant:
]
] There is one correct way to implement text selections in
] JavaScript: document.getSelection. Thats how everyone does it.
] Thats the STANDARD. Everyone, that is, but Microsoft, who
] decided to implement a text selection object instead of a
] method. Very annoying. I have no idea why they did this; as
] far as I can tell there is no technical benefit. Then you've
] got Apple, who decided to make getSelection a method of
] windows instead of documents. So now there are three ways to
] do this.
]
] I understand what Apple was thinking. By putting this under
] window you don't run into problems with frames.
]
] Then again, I don't understand what Apple was thinking. Safari
] is not the only browser on the planet! I still have to support
] the other methods for other browers, I still have to do step
] through all the frames on a page, so you really haven't helped
] me at all. My code is more complex, not less complex. More
] importantly, almost nobody who uses this stuff knows how to
] make this work effectively. The result is that bloggers can't,
] and in general, don't use your browser.
]
] In general, and in particular on the internet, being standards
] compliant is better then being more efficient. It doesn't
] matter how well your stuff works if no one can use it!

Awesome!!!! You rock!