Daniel Friesen's Blog - Latest Comments

Re: css3 border-radius and vendor prefix fud

Jonas Hovmand — Tue, 11 Sep 2012 13:34:07 -0000

Awesome post, never thought about the order of the same properties. I think most people just puts the standard property above the others to indicate a section or something like that.

Re: A HTML5 Browser maze, oninput support

Grant Husbands — Tue, 11 Sep 2012 08:10:11 -0000

It's worth noting that IE9 can't detect text removal through the oninput or onpropertychange events, so feature detection may be insufficient.

Re: A HTML5 Browser maze, oninput support

J. Campbell — Thu, 28 Jun 2012 13:16:41 -0000

Please change your website design! This is too painful to read, despite the value of the information. And do you really need moving backgrounds?

Re: A HTML5 Browser maze, oninput support

John Cusak — Sun, 06 May 2012 00:36:17 -0000

You really need to consider a few improvements to this site, namely:
1) increase the font size - it is much too small and reading a huge block of text at this font size is horrendeous.
2) get rid of green on green - this is 2012 and we don't need another iteration of "yellow text" schemes.
3) don't use a horizontally fluid layout that aligns all the way to the left and right (view this on an hd screen to see why).

Re: A HTML5 Browser maze, oninput support

Zoltan Hawryluk — Wed, 11 May 2011 09:53:19 -0000

Excellent research! I was directed to it because of my blog post about the deprecation of the onforminout tag and my erroneous assumption that there wasn't a replacement for it:

http://www.useragentman.com/bl...

I had already wrote a polyfill for onforminput in my html5Widgets library, and plan on refactoring it to support oninput as well, and your support test will definitely help with this.
Thanks a mil.

Re: A HTML5 Browser maze, oninput support

nottRobin — Fri, 18 Mar 2011 08:15:53 -0000

Back in December when I was looking into this I did also post to a W3C DOM mailing list to get them to come up with a standard for DOM event detection. I don't know if anything came of it though.

Re: A HTML5 Browser maze, oninput support

Mathias Bynens — Fri, 18 Mar 2011 06:24:17 -0000

The problems in Firefox are described as bug 414853: https://bugzilla.mozilla.org/s...

By the way, the final IE9 release supports oninput :)

Re: A HTML5 Browser maze, oninput support

Daniel Friesen — Thu, 16 Dec 2010 12:53:02 -0000

Well, to be specific I "did" have this https://gist.github.com/743725 code, but as you can see I had most of it commented out because we never used it and I don't remember how much I tested it.

Re: A HTML5 Browser maze, oninput support

Daniel Friesen — Thu, 16 Dec 2010 12:42:57 -0000

Yup, I never made a plugin. All our target browsers already supported oninput so I didn't really have a reason to build and maintain one.

Re: A HTML5 Browser maze, oninput support

nottRobin — Thu, 16 Dec 2010 12:24:50 -0000

I've been trying to work out how to detect support for Fx for ages! Thanks for posting.

I am working on a jQuery plugin to fix this, as I'm guessing you didn't create one. Under my solution "input" events fired twice in Fx because it couldn't correctly detect support. I'm going to add in your solution for detecting support, and I'll also try to add something to solve the IOS and Opera issues.
https://github.com/nottrobin/j...
http://static.robinwinslow.co....

Robin.

Re: A HTML5 Browser maze, oninput support

Hollister — Tue, 07 Dec 2010 16:55:07 -0000

Nice post, but this color scheme made me copy/paste it to an editor so I could read it without melting my retinas. Yuck.

Re: HTML5 Implementation Flops

Barefootdaddy — Wed, 10 Nov 2010 15:15:14 -0000

There might be some interesting stuff here, but your choice of color scheme makes the site a pain to even try to read, so I will not even bother trying.

Re: HTML5 Implementation Flops

Andreas Kuckartz — Thu, 06 May 2010 15:27:36 -0000

I have created a bug entry and linked to this page:

Allow "size" attribute for input-type "number"
http://www.w3.org/Bugs/Public/...

Re: Disqus For Comments

Daniel Friesen — Sun, 31 Jan 2010 10:02:39 -0000

Side note I didn't include in the blog post I'm working on replacing the recent posts on the home page with something hand rolled using ajax and a local php script so that disqus doesn't kill load times on my blog's main page. ;) I'm actually posting this here on purpose so I know what a comment from an authenticated user looks like.

Re: with(obj) { ... } a necessary evil.

Daniel Friesen — Sun, 27 Sep 2009 20:52:00 -0000

@Ionut G. Stan
Ya, I know. A real shame especially since ES5 strict actually makes with() {} safer because `foo = "bar"` without var throws errors instead of making global variables.

@Diogo Baeder

with({Foo:function Foo() {}, Bar:function Bar() {}}) {
Foo(); Bar();
}
(function(o) {
o.Foo(); o.Bar();
})({Foo:function Foo() {}, Bar:function Bar() {}});

Closures don't do the same thing. The anonymous function is good for adding another scope, but passing arguments to it is just like setting variables on your own. Both good techniques, just different in purpose and effect.

Re: JavaScript; A beauty, the mistake we made about libraries

Isaac Z. Schlueter — Thu, 27 Aug 2009 22:42:00 -0000

Also, Hedger Wang's JOT is quite nice. http://code.google.com/p/jot-p...

Re: with(obj) { ... } a necessary evil.

Diogo Baeder — Thu, 06 Aug 2009 10:08:00 -0000

Wouldn't closures be a cleaner way of using shortcuts to object properties? Like (function($){ })(jQuery); What's your opinion about the two aproaches in the same context?

Re: with(obj) { ... } a necessary evil.

Ionuț G. Stan — Fri, 10 Jul 2009 04:39:00 -0000

I agree with you. I have learned a great deal of JavaScript from Crockford, and I'm grateful for that, but lately it seems that every single thing that caused his programs a bug is an unwanted feature in the language and often he's not even arguing for his statements. The sad thing is that the with statement is banished from ECMAScript 5 when in strict mode, but I think you already know that.

Re: JavaScript; A beauty, the mistake we made about libraries

Mic Cvilic — Tue, 07 Jul 2009 15:28:00 -0000

My 2 cents in your quest, you can have a look at PURE for templating.
Although it was intended for client side rendering, it seems to work fine on Jaxer and Rhino.

A demo of the new version is available at: http://beebole.com/pure/versio...
And the sources are at http://github.com/pure/pure/tr...