Viewing profile — timdown
timdown
HN member- Joined
- Mon, Dec 14, 2009, 12:27 PM UTC
- HN karma
- 23
- Public activity
- 20 items
- HN profile
- View on Hacker News ↗
About timdown
No profile information was provided.
Recent public activity
-
comment
Comment #9309634
I've had a go at implementing a simple version of innerText: https://github.com/timdown/rangy/wiki/Text-Range-Module
-
comment
Comment #7441399
How does it work?
-
comment
Comment #7149887
I'm not convinced. I think not knowing that apply() and call() exist would lead to unnecessarily clunky code, but even after over a decade of using them occasionally I still someti…
- comment
-
comment
Comment #4654261
The first thing I tried to do (in current Firefox) failed: select text over two paragraphs, change text colour. The selection then changes. Not a great start.
-
comment
Comment #4233690
Obviously your decision to implement feature detection in jQuery was your own, but you're doing a disservice to the comp.lang.javascript regulars who laid this out for you. Describ…
-
comment
Comment #4202236
Looks similar to the serializer module of my rangy project: http://rangy.googlecode.com/svn/trunk/demos/serializer.html
-
comment
Comment #2992123
The module pattern has its place and can be used alongside prototypes, as you know, but I absolutely agree.
-
comment
Comment #2936645
Why is IE < 9 support a low priority? Adding support would be pretty simple and wouldn't add much code, and IE < 9 is still used by a significant proportion of users.
-
comment
Comment #2661262
You can't remove all the craziness in JSLint. The warnings about using == instead of === and not having your var statements at the top of the function, for example.
-
comment
Comment #2544196
Whether the property/attribute distinction is necessary for jQuery users is one question (I strongly believe it is), but if not, the correct move would be to remove the prop() meth…
- comment
-
comment
Comment #2544111
This release is a fudge, and a partial backwards step. The jQuery team seem uncertain about what the prop()/attr() change is trying to achieve (an uncertainty that probably stems f…
-
comment
Comment #2520438
Generally not bad, but there are some errors and oversights in here: - At the end of the "Always Use === Comparison" section, the example will throw a ReferenceError if (as is sugg…
-
comment
Comment #2520405
No. forEach() being native doesn't prevent it from generally being slower than a foor loop, because it still has to do a function call on every iteration.
-
comment
Comment #2513265
The difference between attributes and properties is not an inane detail. It's fundamental, and if you don't understand it then you can't work reliably with the DOM, either with or …
-
comment
Comment #2513258
That's quite a simplified explanation which sidesteps the issue of properties that correspond to attributes, which is where most of the confusion is going to be. And I totally disa…
-
comment
Comment #2513209
In the case of attr(), the convenience jQuery was adding was an enormous fudge and attempted to gloss over the fundamental difference between attributes and properties, which has d…
-
comment
Comment #994041
For that specific case, the more verbose version is definitely better, since the undefined property of the global object can be altered. For example, this silently redefines it for…
-
comment
Comment #994036
The good side of David Mark: I have read plenty of his stuff on comp.lang.javascript over some time, and my own JavaScript is good enough to tell that his understanding is deep and…