Comments on: __defineSetter__ in Mozilla http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla scratched tallies on the prison wall Tue, 02 Dec 2008 02:05:05 +0000 http://wordpress.org/?v=2.6.5 By: Hallvord R. M. Steen http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-105483 Hallvord R. M. Steen Sun, 27 Jan 2008 06:20:51 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-105483 The problem with looking up the element that owns the style property is basically a shortcoming of JavaScript/ECMAScript, I've been there many times and still don't know how to do it. Would be nice with a generic obj.__parent__ or something. (The problem is much worse with getters and setters BTW, in other contexts you are much likely to have the information in a variable anyway.) The only real solution I know so far is to use closures where you define the setters/getters but this naturally sucks because you can not use prototype.__define[GS]etter__ to that extent. Maybe ES4 comes to the rescue? The problem with looking up the element that owns the style property is basically a shortcoming of JavaScript/ECMAScript, I’ve been there many times and still don’t know how to do it. Would be nice with a generic obj.__parent__ or something. (The problem is much worse with getters and setters BTW, in other contexts you are much likely to have the information in a variable anyway.)

The only real solution I know so far is to use closures where you define the setters/getters but this naturally sucks because you can not use prototype.__define[GS]etter__ to that extent. Maybe ES4 comes to the rescue?

]]> By: as days pass by » Off to Austin http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-4034 as days pass by » Off to Austin Wed, 19 Oct 2005 01:08:49 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-4034 [...] There are times when this weblog is silent because I’m not up to much. There are also times when it’s silent because I’m up to too much and don’t have time to post. This most recent silence has been the latter sort, although a couple of nuggets (like the thing about mousewheel scrolling and the thing about defineSetters came out of my current work. Still not ready to reveal it, but I do have one other thing to say: I’m going to SxSW 2006! Yes indeed. I shall be there in Austin. I got well sick last year of everyone going on about it, and Simon ragged on me for thinking about not going, pointing out that it is great and fantastic and now he works at Yahoo, and I examined his argument and found it compelling. We’ll ignore, for the moment, all the 64oz steaks for $0.99 that you get in Texas, although I shall not be ignoring them when I get there, no sirree. Bring me another. And another plate of chips, too. Oh yes. Anyway, I’m really looking forward to it. It’s going to be cool. I’m also speaking at a couple of upcoming conferences; details when they go public. Blimey — jetting off to other countries, speaking at conferences…I’m turning into Jono. Heh. [...] [...] There are times when this weblog is silent because I’m not up to much. There are also times when it’s silent because I’m up to too much and don’t have time to post. This most recent silence has been the latter sort, although a couple of nuggets (like the thing about mousewheel scrolling and the thing about defineSetters came out of my current work. Still not ready to reveal it, but I do have one other thing to say: I’m going to SxSW 2006! Yes indeed. I shall be there in Austin. I got well sick last year of everyone going on about it, and Simon ragged on me for thinking about not going, pointing out that it is great and fantastic and now he works at Yahoo, and I examined his argument and found it compelling. We’ll ignore, for the moment, all the 64oz steaks for $0.99 that you get in Texas, although I shall not be ignoring them when I get there, no sirree. Bring me another. And another plate of chips, too. Oh yes. Anyway, I’m really looking forward to it. It’s going to be cool. I’m also speaking at a couple of upcoming conferences; details when they go public. Blimey — jetting off to other countries, speaking at conferences…I’m turning into Jono. Heh. [...]

]]> By: sil http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3869 sil Wed, 28 Sep 2005 17:22:37 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3869 OCB: for a mighty cool project, which I shall be revealing as soon as I get it working :) OCB: for a mighty cool project, which I shall be revealing as soon as I get it working :)

]]> By: OCB http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3864 OCB Wed, 28 Sep 2005 11:07:01 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3864 One question - WHY ? Why on earth would you ever want to do this - bored maybe ? Too much time on your hands ? :-) One question - WHY ?

Why on earth would you ever want to do this - bored maybe ? Too much time on your hands ?

:-)

]]> By: sil http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3863 sil Wed, 28 Sep 2005 10:43:07 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3863 What I can do is, in cssdisplay, walk through all the elements on the page and say if (thiselement.style === this) { // do something with thiselement } which works, and should be fine as long as the page isn't *too* massive, which it won't be for this project. What I can do is, in cssdisplay, walk through all the elements on the page and say

if (thiselement.style === this) { // do something with thiselement }

which works, and should be fine as long as the page isn’t *too* massive, which it won’t be for this project.

]]> By: sil http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3862 sil Wed, 28 Sep 2005 08:38:16 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3862 Hm. New problem, then; what I actually want to do, in cssdisplay(), is get the computed style of the element. However, I don't *have* the element; "this" in cssdisplay() is the style declaration. Any suggestions for how I can get the element, or how I can pre-prep all elements (including dynamically created ones) so that I can get a reference to an element from its CSSStylrDeclaration object? Hm. New problem, then; what I actually want to do, in cssdisplay(), is get the computed style of the element. However, I don’t *have* the element; “this” in cssdisplay() is the style declaration. Any suggestions for how I can get the element, or how I can pre-prep all elements (including dynamically created ones) so that I can get a reference to an element from its CSSStylrDeclaration object?

]]> By: sil http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3861 sil Wed, 28 Sep 2005 08:25:27 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3861 Dylan: nice one! That works. DIdn't even *know* about setProperty(). Dylan: nice one! That works. DIdn’t even *know* about setProperty().

]]> By: Dylan Moreland http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3860 Dylan Moreland Wed, 28 Sep 2005 02:06:32 +0000 http://www.kryogenix.org/days/2005/09/28/__definesetter__-in-mozilla#comment-3860 What about calling this.setProperty("display", newstyle, "")? What about calling this.setProperty(”display”, newstyle, “”)?

]]>