Firefox 3.0 and Livejournal

[dracodraconis]

I'm not sure if anyone else has tried Firefox 3.0, but it appears its version of Java doesn't like the javascript used by LJ's RichText option. Specifically, if you attempt to use RichText to add a hyperlink, the original window does not close, and the "link" that is, in fact, added is a javascript error.

I've submitted a service request so we'll see what happens. Other Rich Text features, such as tabulation and inserting images appear to work fine so it may the be peculiarities of one particular javascript function that can be fixed with a bit of code reuse and editing.

Until then it is back to hyperlinking by hand.

Edit: Here are some of LJ-support's responses to similar queries

http://www.livejournal.com/support/see_request.bml?id=896053
http://www.livejournal.com/support/see_request.bml?id=895951
http://www.livejournal.com/support/see_request.bml?id=895904

All with the same response:

"Thank you for your report. Several other users have also been reporting an inability to create links in the Rich Text Editor while using Firefox 3. The developers have been made aware of these reports and are currently investigating the issue. You may wish to watch the lj_releases community [http://community.livejournal.com/lj_releases/profile], as any information regarding fixes for this issue will be announced there.

"In the mean time, you will need to add links manually through the HTML editor. Information on how to do this can be found in the FAQ above, should you need it. Additionally, you may wish to use another browser to post your entries until the issue is resolved. I apologize for the inconvenience."

Comments

[corradus.livejournal.com]

Yay! I like new 'cuz New is Better!

[dracodraconis.livejournal.com]

I figured I'd check out the "New and Improved" version at work before trying it elsewhere, and I'm glad I did. There are some nice features and it is quite zippy, but the LJ javascript problem is annoying. I'll hold off on installing it anywhere else, and probably will stick with version 2.0 when the laptop comes in at work.

[zenten.livejournal.com]

I tried it running Swiftfox 3 (basically Firefox 3 optimized for Linux) and had a slightly different problem, I go to enter in the URL, click OK, and it acts like I didn't do anything.

[dracodraconis.livejournal.com]

Yep, the window that opens basically stays open as if nothing had happened.

[zenten.livejournal.com]

Sorry, I meant when I click "OK" the window where I enter the link closes, but the main entry window stays the same, with no change in the text.

[dracodraconis.livejournal.com]

Ah. That's different.

[samhaine.livejournal.com]

How's the plugin support so far?

[dracodraconis.livejournal.com]

Not bad. Some didn't transfer over, but they weren't anything I was using much and was planning to remove them anyway. The PicLens plugin is cool, though. On certain web sites (Flicker, Fotki, Facebook, etc.) the images can be launched in a new window in which the photos are displayed in 3D, as if along the surface of a cylinder. Clicking on each brings them to the front, and the mouse wheel can be used to enlarge or shrink them. Adblock and Noscript still works fine (those where the ones I wanted to keep). Basically, if you want a plugin to make Firefox more "pretty" (like coloured tabs and such), some of those plugins appear to not yet be supported.

A potentially useful feature is that they've added search tags to the bookmark list to make things easier to find. There is also a star to the right of the text in the address bar that turns gold when you are on a page that is already in your bookmarks. Clicking on the star automatically adds the bookmark to your list, and clicking on the star when it is gold lets you edit that entry without having to open the bookmarks file.

[zenten.livejournal.com]

I've found that disabling the plugin check makes most plugins that say they aren't compatible still work, but that was back in prerelease.

[dracodraconis.livejournal.com]

I haven't tried that in the full release, but I would expect that it would operate the same way. It's possible that a plugin being listed as "incompatible" simply means it hasn't been tested with FF3 so they can't guarantee that it works.