JavaScript Shell 1.4
Changes since JavaScript Shell 1.3.1:
- Up/down now navigate history as long as the caret is within the first/last line of the input. (Previously, the caret had to be at the beginning of the first line or the end of the last line.)
- Navigating to the previous history entry now puts the caret at the end of the textarea.
- Added tooltips for the links with accesskeys at the top of the page. (Fixed by Jesper Rønn-Jensen.)
- Added
overflow: auto;
to the input field to prevent scrollbars from appearing in IE unnecessarily. - Alphabetize properties in props() output.
- Added a hidden option for props() to print one property per line (pass true as the second parameter to props()).
- props() now complains if you pass undefined or null.
- Tab completion no longer causes an error in IE. (Fixed by Jesper Rønn-Jensen.)
October 30th, 2005 at 8:33 pm
Btw, I use this tool to turn each new version of the JavaScript Shell into a bookmarklet.
October 31st, 2005 at 4:25 pm
JavaScript Shell: Useful tool for editing DOM and JavaScript
Jesse Ruderman has a tool for live-editing JavaScript and DOM on any webpage. I have found it very useful and indispensable for rapid JavaScript development, bug finding in unknown code.
Couple of days ago I asked Jesse to consider some improvements…
November 1st, 2005 at 1:07 am
Thanks. I haven’t realized before what powerful tool this is. I’ll start using it some more.
I have one wish. Make all the lists be links, like del.icio.us post page, where clicking a link will inject it into the command line.
By “lists”, I mean the lists generated by the props() command, and in the Matches… message when ambigous prefix is used for tab completion (BTW, I get two colons after Matches)
November 1st, 2005 at 1:36 am
Great!
November 2nd, 2005 at 7:38 pm
[…] Jesse’s updated the bookmarklet. Go get it. […]
November 3rd, 2005 at 2:32 pm
The diff appears to be incomplete, at least in IE6 under XP SP2.
November 3rd, 2005 at 3:21 pm
Jeremy, try viewing it with Firefox or using View Source in IE. IE has a bug where it ignores the text/plain mime type for anything that looks remotely like HTML. What am I supposed to do, send it as “text/plain; really”?
November 30th, 2005 at 8:04 am
Web developer’s collection of browser tools
With the release of Firefox 1.5, I thought it’s time to make a round up on the tools and plugins that makes my everyday work faster, more efficient. Here are some of my favorite tools for Firefox and a few for Internet Explorer.
…