Fixing the XML XSL Editor, specifically the Netscape 6 / Mozilla form bug, has given me superpowers.
Ok, no it didn't. But how else to summarize this post?
Which superpower would you prefer to have? Flight or invisibility?
First, last weekend NPR aired a great episode of This American Life, "Superpowers." [real audio] It includes an interview of Jimmy Ware, author of the supremely great Jimmy Corrigan: The Smartest Kid on Earth, and recounts the story of Zora, a woman who, as a child, decided to be a real-life superhero, made a long list of all the skills she would need (i.e. martial arts, bomb diffusion) and then set out and actually accomplished nearly everything on her list. Then she ran into the CIA...
Should be renamed "The Uncanny [se]X-Men..."
You are heterosexual. When you embrace and kiss someone, both of the faces involved look kind of squishy and funny. As does everyone's in that posture. But for some reason, in the heat of the moment you think that you look like this.
"Hush" is no longer the best episode of this series...
Prime-time TV is usually forgettable - but for Joss Whedon's disturbing, expressionistic meditation on time and the ritual that surrounds a parent's sudden death on the latest heart-wrenching episode of Buffy, The Vampire Slayer. You think I'm joking. For me, it was great television but was probably less entertaining for some...
On the Netscape 6 / Mozilla discovery...
I found a bug in my XML XSL Editor beta when testing it in Mozilla Seamonkey 0.8. Apparently the Gecko engine doesn't like the TARGET attribute of the <FORM> tag when it points to a new window. The page validates as XHTML, perhaps I'm missing something basic...is the attribute deprecated? Do I need to use XForms with XHTML? Here's the behavior I witnessed: A new window would open when the form was submitted but the method would be a simple GET (even if method="post" was explicitly declared) and none of the form information would be passed through the URL. However, if the form was ever submitted again and neither window had been closed, then the correct behavior would occur. This held true for Netscape 6 as well. Solution? I use Javascript to access the DOM on the client-side and the open method of the window object to get a new window to start loading the target page. Then I dynamically assign the target property of the form to the new window's name and submit() the form.