We've all had to code up those ever-so-fun branching selects. I chose to implement it by showing or hiding (display:block/none) the container of the label+select corresponding to the appropriate branch. And IE6 decided to hemorrhage option innerHTML onto the page - for 1 of the 3 branches: the middle one. I solved it by adding "position:absolute" to the css for the container.
Wednesday, June 24, 2009
Friday, June 12, 2009
Some cross-browser findings
ff2 mac: doesn't understand floating-point percentages (ie: 107.3% = 107%) - ran into this with font sizes.
ff3 thinks that if your parent is visibility:hidden, but you are visibility:visible, that you should display. (wrong.)
IE8 VHD from microsoft on vpc2007 is not the same as ie8 in the wild. Button element widths seem to be at least 1px wider in the wild.
Friday, May 22, 2009
A Little Elementool Love
I started a google code project because I've been using elementool lately and felt that it needed some help.
Elementool firefox greasemonkey userscript
Current features
- Adds row-highlight rollovers
- Click anywhere to go to the only link in that row (that bug)
Suggestions welcome!
Friday, May 15, 2009
JASH - debug safari
Need to debug javascript/css on ..
(Not sure I'd recommend JASH for ie debugging, since the script debugger / debugbar / ie developer toolbar are a little more convenient)
UPDATE: I've used JASH a little more, and found it useful a little less.
jQuery settles down with dojo, gains weight
Sure, this is months-old news, but still. I remember back in the good ol' days when jQuery was a young, athletic rising star. Then it met dojo and settled down.. and gained weight. Look under the jQuery hood and you'll see .. two libraries blast-welded together, complete with their own separate prenups, er, copyright blocks: jQuery and Sizzle, from the dojo foundation.
Wednesday, May 13, 2009
Disabled input fires no events
Tuesday, May 12, 2009
IE JSON silent fail - size limit
Trying to get a ton (600K) of JSON via XHR into IE.. silently failing. Oh, it fetches the data, it just can't parse the data, either through jQuery's built-in JSON parsing or even by the ol' eval.
Trimming the data down to 60K, there were no problems. The data is a repeating set of dummy objects, so I'm almost certain that I didn't just happen to trim out some problem section of the data. I'm convinced that IE is choking on the data simply because it is more than it can handle. My guess is that JScript doesn't throw the usual "your script is taking too long to execute" warning when executing a single "eval".
I 'solved' the problem by ditching XHR and using dynamic script tags:
data.js
namespace.onData({theGigantic:json............});