While working on some accessible UI widgets I found strange behavior in IE8 related to when it does or doesn’t show the focus outline around…
Comments closedCategory: JavaScript
I have read Life above the Service Tier a few times now. Its a very good paper, one that really changes your perspective, but I wish it was better. If you work on web applications and you haven’t read this paper I recommend that you go read it now — but do come back.
I agree with the overall reasoning and the conclusion.
So one obvious way to correct the thin client architecture is to implement a true MVC framework on the client side… That means that all “Presentation Flows” must occur within the currently Âloaded web page… So one workable model is the Single Page Application (SPA).
First let me get some minor complaints out of the way.
5 CommentsThe HTML button element has given me trouble in the past. My conclusion was to not use the button element except to progressively enhance the look of buttons. This means the button would initially be an input of type button and JavaScript, if enabled, would change it to a button element.
Well at work I’m working on an app that requires JavaScript and all form submissions are done with JavaScript already so I thought it would be safe to switch over to <button>. The server never uses the button names or values (all needed information is in other inputs – hidden or otherwise) so the IE bugs should not be an issue.
This time the problems I found were exposed with Firefox but the real problem was in the web app code even if the browser behavior was surprising.
2 Comments[This originally appeared on my dev2dev blog 16-Nov-2007]
Here are instructions for using JSLint from Ant to check your JavaScript for common potential problems.