I’m a very happy user of Toodledo, it’s almost always open on my computer and syncs with Appigo Todo on my iPhone.

I recently suggested that links in task item notes should open in new windows, or at least they should add the option to choose that behavior. Toodledo responded that they originally had this, but some people wanted every link to open in a new window, while others wanted subsequent links to recycle the new window. With both camps complaining, they just removed targets from the links altogether.

Anyway, here are two bookmarklets for Toodledo. Clicking these will modify the task note links to open in a different window.

• Open each task note link in a new window: ✔
• Open task note links in a reusable window: ✔°

Note: You will need to click this each time you load the page, or add a new item. Yes it’s clumsy, but this is only a band-aid until Toodledo adds the feature.

Those little search bubbles that popup on the New York Times website whenever you select text really annoy me. Clicking this bookmarklet on any NYTimes page will prevent them from appearing:

NYTfix

This is a 2-minute solution, there’s no domain checking or anything, all it does is remove existing bubbles then cancel the document’s mouseup observer, which the NYTimes site uses to trigger the search balloons. The bookmarklet was very quickly checked in Safari, Firefox and IE8, NYTimes text selection doesn’t work at all for me in IE6 or IE7.

update 2: These workarounds also work with Safari 2.0 in Mac OS X v10.4 .
update: There’s a simpler fix, jump to the bottom.

Yesterday morning I noticed a change to the JavaScript/DOM getSelection() behavior in the new Safari 1.3 (in 10.3.9) and the most recent version of Firefox 1.0.3.

I’ve been using this method for years to pull selected text from web pages for several of my bookmarklets. The one I use most frequently generates a link from whatever text is selected. If nothing is selected, it grabs the document’s title. The change in getSelection() broke that bookmarklet, no selected text was recognized.

After a bit of research, I found Mozilla’s Safely accessing content DOM from chrome page which describes the security fixes behind the modification and detailing other problems the changes had caused. Based on Mozilla bug 290777 and this post by Buzz Anderson, both browsers seem to have problems with the change. Despite those bugs, I managed to find the simple workaround as described below.

What Safari and Firefox now seem to be doing is creating a DOM selection object from getSelection() instead of treating it as a simple string. The result is that getSelection() appear to be a string, but few of the string manipulation functions work without additional considerations.

The following examples are all intended to be tested as bookmarklets, drag them to your bookmarks bar for testing:

• getSelection() test 1
  javascript:d=window.getSelection();
alert(d);

  Works as expected in Safari 1.2.4, Safari 1.3 and Firefox 1.03, popping an alert containing the selected text. Trying to measure that returned string fails in Safari 1.3 and Firefox 1.0.3 but works in Safari 1.2.4:

• getSelection() test 2
  javascript:d=window.getSelection();alert(d.length);

  The older version of Safari returns a character count for the string of selected text. Firefox and Safari 1.3 return “undefined”. There are quite a few other problems:

• getSelection() test 3
  javascript:d=window.getSelection();
alert(d.toString());

  Works in Firefox and Safari 1.2.4 but not in Safari 1.3.

• getSelection() test 4
  javascript:d=window.getSelection();
alert(d.toString().length);

  Getting the length after toString works in Safari 1.2.4 and Firefox.

Further inconsistencies between Safari 1.3 and Firefox 1.0.3:

• getSelection() test 5
  javascript:d=window.getSelection();alert(d.type);

  Returns “Range” in Safari with a selection, returns “Caret” or “None” with nothing selected. Fails with “undefined” in Firefox. (I think the Firefox 1.0.3 DHTML regression bug might be preventing it from working in Firefox but I didn’t try any of the recent nightly builds.)

• getSelection() test 6
  javascript:d=window.getSelection();
alert(d.getRangeAt(0));

  Fails silently in Safari, returns selected text in Firefox. Safari dumps this into the Console log:
  [5956] :TypeError - Value undefined (result of expression d.getRangeAt) is not object.

• getSelection() test 7
  javascript:d=window.getSelection();
alert(d.typeDetail);

  Fails with “undefined” in both.

There is some good news:

• getSelection() test 8
  javascript:d=window.getSelection();
alert(d.isCollapsed);

  Works in both Firefox and Safari 1.3; fails in Safari 1.2.4 as “undefined”. This means (finally!) there is a workaround for my problem.

I was using the length property to determine whether a selection was empty or not, then fetching the title of the window if that value was 0. Knowing that length no longer works in Firefox and Safari, isCollapsed can be used as a conditional switch.

• getSelection() Workaround
  javascript:d=window.getSelection();
d=(d.isCollapsed||d.length==0)?document.title:d;
alert(d);

  That will return any selected text or the document title if there is no selection. Tested successfully in Safari 1.2.4, Safari 1.3, Firefox 1.0.3 and presumably Safari 2.0 as well.

Line breaks were added to visible code examples because my style-sheet choked on long lines and I can’t redo the CSS right now…

Update: After working through all of the above, I realized there is a far simpler solution: +''. The Safari problem seems to be that string methods do not work on the returned object from getSelection(). Forcing the result into a string by concatenating with an empty string fixes all of my bookmarklets. Concat() fails because it’s a method of string, use the "+" joining operator and an empty string '' instead.

• getSelection() Faster Fix
  javascript:d=window.getSelection()+'';
d=(d.length==0)?document.title:d;
alert(d);