spjwebster

12 ms·

61.
by spjwebster 15y ago
> I'm not doing it wrong by writing sites that aren't IE6 compatible. I'm deliberately deciding their business isn't worth the extra engineering or testing cost. That was the whole point of the article. Don't drop IE6 support because al
62.
by spjwebster 15y ago
The point of the article is that if you're "recoding something" then you're not approaching cross-browser development in the right way. Dismissing IE users as "people who couldn't care less" and writing off proper cross-browser support beca
63.
The Web Development Discipline(isolani.co.uk)
20 points by spjwebster 15y ago|11 comments
64.
by spjwebster 15y ago
Thanks. I promise I did search for a permalink for the article itself. I blame the tumblr theme :)
65.
Making history with the August Dev Derby(hacks.mozilla.org)
2 points by spjwebster 15y ago|0 comments
66.
What do you mean, you don’t like IE6? Really?(remy.tumblr.com)
3 points by spjwebster 15y ago|4 comments
67.
by spjwebster 15y ago
DOMNodeInserted is deprecated in the DOM Level 3 Events recommendation, along with all the other mutation events: http://www.w3.org/TR/DOM-Level-3-Events/#event-type-DOMNodeI... They have been deprecated because they perform poorly: >
68.
by spjwebster 15y ago
It's actually IE7 and IE8, and only for CSS file URLs (as opposed to URLs in CSS files). Details of protocol-relative URLs here: http://blog.httpwatch.com/2010/02/10/using-protocol-relative... ...and the unfortunately double-loading bug
69.
by spjwebster 15y ago
I'd advocate learning JavaScript, learning the DOM and BOM, and only then learning a JavaScript framework like jQuery or YUI. Sooner or later you'll need to do some pure JavaScript development, and you'll need to know how to handle events o
70.
by spjwebster 15y ago
Sometimes templating isn't an option, or isn't enough. You have to make sure you escape in the right context. I've seen developers use PHP's htmlspecialchars() (or hand-rolled versions thereof) when rendering snippets of inline JavaScript.
71.
by spjwebster 15y ago
Please read again. I said: "Firefox doesn’t actually issue a warning, which would have made my job tracking this issue down much easier. Moreover, functions declared within a block before being called work just fine, so it's not that functi
72.
by spjwebster 15y ago
Also, if you hand-code these encoding routines, you're almost certain to miss something out. Please follow the OWASP reference implementations: https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_P...
73.
by spjwebster 15y ago
It's common courtesy to at least give the vendor a chance to fix the bug before you go public. I don't use Skype, and I'm no fan of Microsoft, but this security advisory is just shameless (and harmful) self promotion.
74.
by spjwebster 15y ago
According to the stats gathered by HTTP Archive, the average response size (i.e. after compression) of a JavaScript file is 15kB: http://httparchive.org/interesting.php#responsesizes This will make JavaScript parsing faster for the vast m
75.
by spjwebster 15y ago
Anyone who is looking for the "cool HTML5 future" to be ad-free is going to be bitterly disappointed. Online ads predated the ubiquity of Flash, and they'll be around long after Flash is forgotten.
76.
by spjwebster 15y ago
The spirit of these regulations was undoubtedly to inhibit the practice of cross-site tracking using third party cookies or cookie-like technology. However, neither the EU directive nor the laws that implement it make a distinction between
77.
by spjwebster 15y ago
I built a similar library on top of YUI called Feature Cue while I was at Yahoo! Sadly it was never open sourced, got rewritten, over-engineered and (as far as I know) faded into obscurity. I'm glad the Optimizely guys have released their v
78.
by spjwebster 15y ago
I know the title says "in brief", but it's a little too brief for me. From the horse's mouth: http://www.varnish-software.com/blog/varnish-30-changes-esi-... http://www.varnish-software.com/blog/bans-and-purges-varnish... http://www.
79.
by spjwebster 15y ago
Owing to the lack of options, this is only useful for linting CSS written by the authors or anyone who happens to agree with their opinions on what constitutes good CSS. Crockford may be an opinionated cantankerous old goat , but at least h
80.
by spjwebster 15y ago
Also see Jeff LaMarche's response: http://news.ycombinator.com/item?id=2620020
81.
by spjwebster 15y ago
Jeff LaMarche's follow-up to http://news.ycombinator.com/item?id=2618298
82.
On Being Excellent to Each Other(iphonedevelopment.blogspot.com)
2 points by spjwebster 15y ago|1 comments
83.
by spjwebster 15y ago
> Why do they not impose a legal obligation on google and ad agencies to not track, or on facebook or whatever. They do. As I understand it, this law applies just as well to the likes of Google, Yahoo and Facebook as it does to the site
84.
by spjwebster 15y ago
Ignoring this law means ignoring the privacy concerns of your users. If you're happy with that, you're part of the reason this law was introduced in the first place.
85.
by spjwebster 15y ago
There's a disconnect here. How does the absence of analytics mean the site continues to function with reduced usability? You could argue that over time the site's usability would not increase as much as it might be due to missing analytics
86.
by spjwebster 15y ago
The previous implementation of the law was opt-out. It didn't work, because most users were completely unaware they were being tracked. The real saviour will likely come in the shape of browser support for Do Not Track [1]. While it's not f
87.
by spjwebster 15y ago
The important bit is "but is essential for part of the site to operate." To me, that clearly falls under the "strictly necessary" banner, albeit that it probably shouldn't be set until you enter the part of the site that requires it. Govern
88.
by spjwebster 15y ago
I take it you didn't read the comments on that post then? The ones that explained why the upfront cost of £585 is not at all unreasonable.
89.
by spjwebster 15y ago
I don't get what's so hard about the concept of "strictly necessary". If you take the cookie away and the site ceases to function such that the user cannot complete tasks they are there to do, then the cookie is strictly necessary. If the s
90.
by spjwebster 15y ago
It's definitely a stretch to say we all run into these issues, but you'd be surprised how many beginner and intermediate-level developers don't know about this issue precisely because they've been insulated from it by frameworks. There ar

More ›