| Saturday, April 16, 2005 |
13:48 - Bug massacre
|
(top)  |
Holy crap! They fixed my freaking bug!
Hold on while I hyperventilate for a second.
...Okay, there we go. Now then:
Safari. The TEXTAREA rendering bug. The one I submitted months ago and was told it was already being worked on. The one where the final CR/LF character at the end of text in a TEXTAREA field gets stripped off every time it's rendered.
Sound trivial or obscure? Well then: Picture, if you will, a blog composition or message board composition screen where you can type a body of text, then click the "preview" button to see how it's formatted, and at the same time get your textarea back so you can continue editing.
Imagine that every single time you do this, a CR/LF gets stripped off the end... so every time you submit, you have to scroll down to the end of what might be a huge essay and add another return.
You'd think that final CR/LF would be unimportant, wouldn't you? Well, it is... except it isn't. Mostly because of external behaviors that depend indirectly on how it works, like software that's triggered by actual end-of-line characters (that wouldn't be present in this case), or blogs that render a certain amount of fixed line spacing after the customary return I put at the end of my blog posts and the comments I leave elsewhere. In any case, it's true that it shouldn't matter—but that's all just justifications for not treating stripping off the final CR/LF as the bug it is.
And now it's fixed. Woo-hoo! As is the other similar bug where if you were scrolled down in a long textarea, went to a different tab and then back again, you'd end up back at the top.
Now let's see if they've fixed the bit about how if you're editing text in a pre-rendered textarea, the text-insert cursor is invisible as you zoom around with the arrow keys...
...They did! Huzzah!
UPDATE: One negative: Google Maps has broken. Well, not the actual mapping part; but the text to the right of the map, with all the examples and the "Try it" links, is now rendered as a big run-on sentence without formatting. Some kind of weird CSS thing Google was doing that coded to an old standard of Safari CSS handling? They're still in beta, after all, and they're as likely to be at fault as Safari is.
UPDATE: As of 4/19, Google Maps has already been fixed. Well, we knew Google was full of Mac geeks...
|
|
Brian Tiemann
