hoodwink.d enhanced


Aha, Notice the Expando Which Precludes #

by why in cult

Mark Pilgrim: The UNSELECTABLE attribute is implemented as an expando. Setting the expando property of the document object to false precludes the functionality of all expandos.

Kxxxx, oh when the jargon on MSDN hits stride and blossoms into complete psychedelia.

Someone please assemble a Wikipedia page for this rare bird. I want creators’ bios. I want the original legal pads. I want pronunciation mp3s. GO!!

said on 04 Apr 2007 at 11:40

Is the point of this exercise to demonstrate how much you love the word expando? I can’t disagree with the fact that it is a good one. Nevertheless, your use of expando in this situation seems irrelevant to all browsers. For that, I commend you.

said on 04 Apr 2007 at 11:48

so in IE, the expando is not itself an expando?

said on 04 Apr 2007 at 11:59

If you set document.expando=false, IE will preclude the functionality of allowing unstationary to be set. Firefox precludes the preclusion of this functionality even with expando disabled. The W3C is crying now just like the Shoshone do when you throw an empty Yoohoo bottle on the ground.

said on 04 Apr 2007 at 12:07

I think expando is a great name for a function, but maybe not so great as a property. It seems to me like it needs to DO something itself.

There ought to be a place for it at the top of every Type or Object hierarchy.

So, let’s say, what does Object.new.expando do?

said on 04 Apr 2007 at 12:13

I disagree, the expando totally DOES something. Namely, it precludes other expandos.

said on 04 Apr 2007 at 12:18


said on 04 Apr 2007 at 13:44

Try setting document.expando=false in the global scope. It not only precludes the unselected attribute from being set, but also every other “arbitrary” attribute. The unselected attribute is affected by document.expando=false in the same way a user-defined attribute such as “unstationary”. Try this example in IE with expando set to false, and then set to true for clarification.

document.expando= true;
window.onload = function() {
<body id="unstationary" unstationary="on"></body>

said on 04 Apr 2007 at 15:25
said on 04 Apr 2007 at 17:08

Expando. Every programming term sounds like English, everyone knows why. Concept of expando is rather complicated, not to say irrational, psychedelic etc. It’s funny because it complicates meaning of 1/0, true/false and other binary thingies. So the best thing to do is to name it “EXPANDO” because it doesn’t sound as English at all. Spanish? Maybe.

said on 04 Apr 2007 at 18:21

Handwritten code is so pretty… can someone write a compiler that takes image files? :)

said on 05 Apr 2007 at 02:11

Totally Spanish. Expando == I expand.

said on 05 Apr 2007 at 07:34

I can hardly wait for the document.mondo property to be added. Think of the possibililties!

said on 06 Apr 2007 at 03:11

Daniel: Well, there’s piet

said on 08 Apr 2007 at 17:12

I just tried http://www.mozilla.org/newlayout/demo/expando.html and it is almost exactly to the beat of the music I’m listening to.

Creepy stuff!

said on 10 Apr 2007 at 08:01

Uh … just a small js thing … when comparing with undefined, you should use === instead.

said on 12 Apr 2007 at 02:01

said on 12 Apr 2007 at 02:02

sigh, my love was cleansed. it was an ascii heart. the beauty of which you may never see, now. damnable software.

said on 13 Apr 2007 at 16:28

turns out i was forced to disable ascii hearts on this blog due to rampant fanboyism. you’ll have to circumvent that restriction by resorting to the slightly more dated ascii: I LOVE YOU .

said on 15 Apr 2007 at 15:15

11 Jul 2010 at 20:32

* do fancy stuff in your comment.