Ubiquity Command list cuts off after so many commands, currently mid "E"s.

You can also disable commands directly via the "disable" command if you happen to know which one might be causing the problem. I'd like to learn which command is the culprit here to see if I can reproduce it on my end.

My guess is that the command contains some bad markup which might be causing the output to get munged in the process resulting in what you're seeing. If that's the case its author might need to correct that.

By where it cuts off, I would guess it's the ESV Bible commands from Duncan and Meg, which might be why they've released a new version. Maybe something broke with the new Ubiq update. That's actually why I was looking at the list...he had emailed me, and said there was a new version out, but I think you had to unsub the old one and grab the new one somehow...except it's in the part of the list I can't see.

I did disable those commands just now. I'll have to restart FF and see if that makes a difference.

When I sort by date, I can see most of them, although ESV still doesn't show up. Sort by enabled, and only Herd shows up. Sort by feed name stops at Herd.

Problem persists after disabling all three ESV commands and restarting. Can't delete the actual feed unless I can find it in the command list, can I?

Here's the command site:
http://www.duncanandmeg.org/projects/...

I tested it out and currently it is possible to unsubscribe from the feed and purge it under 0.5.5.pre3 to restore the command list. It's not as broken for me as it appears in your image and I still have the unsubscribe/view source links available. Based on a quick analysis, it appears that the command is D.O.A. to begin with which also makes me believe it's incomplete in some way unless told otherwise.

In other words the command doesn't appear correctly formatted to work as was originally intended.

Ahh, yes Heather you're right that was the wrong feed. However I believe I did find the offending error in the feed with the actual problem, this is one which has cropped up a few times in getting some scripts to run under the updated about: pages.

Note: I'm not a JS expert by any means so hopefully someone can correct me on this or explain it better: But, JavaScript being executed in XHTML documents served up as XML under Firefox seem to choke on parsing character data defined as normal HTML entities (such as  ). Meaning if a command feed contains this kind of special character data in named format (within it's description) it has to instead be referenced by decimal ( ) to play nicely with the current command pages.

This issue shouldn't affect the ubiquity window output in any way at the moment to my knowledge so any tag soup which doesn't display in the command list shouldn't be affecting the Ubiquity window itself. But I can see how invalid markup in the description is capable of rendering that command D.O.A. or worse.

Whether the character data is being read the right or wrong way, I can't say for sure. But we'll want to probably want to investigate it a bit further and develop some command authoring guidelines to avoid problems like this in the future.

Hope that helps.

OK, I got with Duncan, and he's fixed the code, but the problem has moved down the alphabet to a ping command:
http://ubiquity.washing-up.co.uk/ping...

I've just commented on his blog, but it might be this is a common issue. I've not pieced through any others yet, though I can tell you the problem has been eliminated from the ESV commands.