diff --git a/archives/P90.html b/archives/P90.html index 07d6fc2..5875ed1 100644 --- a/archives/P90.html +++ b/archives/P90.html @@ -99,7 +99,7 @@

Post Archive 

A better createElementWithName()

-

Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

+

Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

Read more…

diff --git a/archives/a-better-createelementwithname/comments/index.html b/archives/a-better-createelementwithname/comments/index.html index 21522d9..e18f82e 100644 --- a/archives/a-better-createelementwithname/comments/index.html +++ b/archives/a-better-createelementwithname/comments/index.html @@ -100,7 +100,7 @@

Posted by a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there). The the time, I wrote

+

Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there). The the time, I wrote

function createElementWithName( type, name ){
var element;
// First try the IE way; if this fails then use the standard way
if( document.all ){
element =
document.createElement( '< '+type+' name="'+name+'" />' );
}else{
element = document.createElement( type );
element.setAttribute( 'name', name );
}
return element;
}
view raw createElementWithName-1.js hosted with ❤ by GitHub

It was a complete hack, but it worked. More importantly, however, it began a discussion of a better way to fix the problem in a cross-browser way. The best solution offered was Anthony Lieuallen’s very efficient one-time function definition:

function createElementWithName(){}
(function(){
try {
var el=document.createElement( '<div name="foo">' );
if( 'DIV'!=el.tagName ||
'foo'!=el.name ){
throw 'create element error';
}
createElementWithName = function( tag, name ){
return document.createElement( '<' + tag + ' name="' +
name + '"></' + tag + '>' );
}
}catch( e ){
createElementWithName = function( tag, name ){
var el = document.createElement( tag );
// setAttribute might be better here ?
el.name = name;
return el;
}
}
})();
view raw createElementWithName-2.js hosted with ❤ by GitHub
diff --git a/archives/a-better-createelementwithname/index.html b/archives/a-better-createelementwithname/index.html index 7b4bb7a..f18eb19 100644 --- a/archives/a-better-createelementwithname/index.html +++ b/archives/a-better-createelementwithname/index.html @@ -100,7 +100,7 @@

Posted by a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there). The the time, I wrote

+

Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there). The the time, I wrote

function createElementWithName( type, name ){
var element;
// First try the IE way; if this fails then use the standard way
if( document.all ){
element =
document.createElement( '< '+type+' name="'+name+'" />' );
}else{
element = document.createElement( type );
element.setAttribute( 'name', name );
}
return element;
}
view raw createElementWithName-1.js hosted with ❤ by GitHub

It was a complete hack, but it worked. More importantly, however, it began a discussion of a better way to fix the problem in a cross-browser way. The best solution offered was Anthony Lieuallen’s very efficient one-time function definition:

function createElementWithName(){}
(function(){
try {
var el=document.createElement( '<div name="foo">' );
if( 'DIV'!=el.tagName ||
'foo'!=el.name ){
throw 'create element error';
}
createElementWithName = function( tag, name ){
return document.createElement( '<' + tag + ' name="' +
name + '"></' + tag + '>' );
}
}catch( e ){
createElementWithName = function( tag, name ){
var el = document.createElement( tag );
// setAttribute might be better here ?
el.name = name;
return el;
}
}
})();
view raw createElementWithName-2.js hosted with ❤ by GitHub
diff --git a/archives/alex-russell-is-not-a-heretic/comments/index.html b/archives/alex-russell-is-not-a-heretic/comments/index.html index d4d5fa1..6d9eb03 100644 --- a/archives/alex-russell-is-not-a-heretic/comments/index.html +++ b/archives/alex-russell-is-not-a-heretic/comments/index.html @@ -234,7 +234,7 @@

Comments

  • -

    <blockquote cite=“http://www.easy-reader.net/archives/alex-russell-is-not-a-heretic/#comment-11827”>The vendor-specific prefix is present on these properties because the <abbr title=“Cascading Style Sheets”>CSS</abbr> 3 specification is still in draft.
     </blockquote>

    +

    <blockquote cite=“/archives/alex-russell-is-not-a-heretic/#comment-11827”>The vendor-specific prefix is present on these properties because the <abbr title=“Cascading Style Sheets”>CSS</abbr> 3 specification is still in draft.
     </blockquote>

    Right. I know that’s the intent, but the problem is that these features have been publicized and are now being incorporated into stylesheets as though they were part of the spec. I see that as somewhat of an issue. The spec itself states that

    @@ -288,15 +288,15 @@

    Comments

  • -

    <blockquote cite=“http://www.easy-reader.net/archives/alex-russell-is-not-a-heretic/#comment-11831”>I would like to follow up on the points regarding the correct patterns for degraded markup for each widget so that we can come up with a set of recommendations which can go in the Dojo docs.</blockquote>

    +

    <blockquote cite=“/archives/alex-russell-is-not-a-heretic/#comment-11831”>I would like to follow up on the points regarding the correct patterns for degraded markup for each widget so that we can come up with a set of recommendations which can go in the Dojo docs.</blockquote>

    Excellent, I’d love to help. Email’s on it’s way.

    -

    <blockquote cite=“http://www.easy-reader.net/archives/alex-russell-is-not-a-heretic/#comment-11831”>Progress on the <abbr title=“Document Type Definition”>DTD</abbr> front isn’t likely before Dojo 1.0, but may be possible afterward.</blockquote>

    +

    <blockquote cite=“/archives/alex-russell-is-not-a-heretic/#comment-11831”>Progress on the <abbr title=“Document Type Definition”>DTD</abbr> front isn’t likely before Dojo 1.0, but may be possible afterward.</blockquote>

    I understand that this isn’t the most pressing thing for you all right now, but I am glad you’re interested in it as an option. I’m happy to help in this regard as well, just let me know.

    -

    <blockquote cite=“http://www.easy-reader.net/archives/alex-russell-is-not-a-heretic/#comment-11831”>As for <abbr title=“Cascading Style Sheets”>CSS</abbr> rules being used to locate widgets, not very likely as the default why is the class selector more blessed than attribute selectors?) but perhaps pluggable. There are only a couple of things that would need to change for such a plugin to work in Dojo.</blockquote>

    +

    <blockquote cite=“/archives/alex-russell-is-not-a-heretic/#comment-11831”>As for <abbr title=“Cascading Style Sheets”>CSS</abbr> rules being used to locate widgets, not very likely as the default why is the class selector more blessed than attribute selectors?) but perhaps pluggable. There are only a couple of things that would need to change for such a plugin to work in Dojo.</blockquote>

    It’s not a hard gap to fill, for sure. I guess I am of the mindset that CLASSes are for classification of elements (not just application of <abbr title=“Cascading Style Sheets”>CSS</abbr>). That’s why I favor it as a means of including additional info about an element or using it as a hook for a script. We can talk more about this at length as well via email.

    diff --git a/archives/an-event-apart-nyc-post-mortem/index.html b/archives/an-event-apart-nyc-post-mortem/index.html index 2c19be8..4cbcb09 100644 --- a/archives/an-event-apart-nyc-post-mortem/index.html +++ b/archives/an-event-apart-nyc-post-mortem/index.html @@ -106,7 +106,7 @@

    Posted by Learning Web Design (note: the link still goes to the 2nd edition) and Andy’s Transcending CSS: The Fine Art of Web Design.

    Anyway, so, An Event Apart…
    I had such a great time at this conference. Not only was it a pleasure to speak at, but I met some awesome folks and got to spend more time with Jeffrey, Eric, Jason, Khoi, Tantek, and Rob. It was also great to spend more time with (Dr.) Kat and Carolyn (Eric’s family) and to finally meet Carrie and Ava (Jeffrey’s family) and Liz (Jason’s bride). I also got to hang out a bit more with Dan & Jon (both formerly of Pixelworthy). They are two truly fantastic gents and they played their roles as the AEA go-fers/whipping boys with gusto. Seriously, these guys rock. From purely a social aspect, AEA was fantastic; like an intimate SXSW.

    -

    As for the sessions, I thought they were incredible. I thoroughly enjoyed all of Jeffrey’s talks. He is such a great speaker, capable of moving an audience with even the simplest turn of phrase. It was nice to finally see Eric giving a CSS talk too. I’ve only seen him talk microformats (at SXSWi 2005) and general web standards stuff relating to search (on one of my panels at SXSWi 2006). I was delighted to find that he and I tackle layout problems very much the same way… making my methods not seem quite so mad. “Stan” was also a fantastic solo act (I’ve only seen him on panels) and he walked us through how the ALA redesign came to be. Being that I came on board just after the relaunch, it was nice to get some of the backstory.

    +

    As for the sessions, I thought they were incredible. I thoroughly enjoyed all of Jeffrey’s talks. He is such a great speaker, capable of moving an audience with even the simplest turn of phrase. It was nice to finally see Eric giving a CSS talk too. I’ve only seen him talk microformats (at SXSWi 2005) and general web standards stuff relating to search (on one of my panels at SXSWi 2006). I was delighted to find that he and I tackle layout problems very much the same way… making my methods not seem quite so mad. “Stan” was also a fantastic solo act (I’ve only seen him on panels) and he walked us through how the ALA redesign came to be. Being that I came on board just after the relaunch, it was nice to get some of the backstory.

    The guest speakers were also a lot of fun to listen to. ze frank had me in tears I was laughing so hard and I had no idea just how much work Khoi puts into blogging and other non-NYT-related activities. It’s amazing he gets any sleep at all. Tantek’s microformats talk was also good because it helped amalgamate a lot of the disperate (and not always clear) information available on microformats into something usable, allowing me to take it beyond the simple hcard and hcal stuff I’ve been using for the last couple months.

    I also thought the design and code critiques were excellent. The design one could have been a little more hmm, how to put this… aggressive? But design is such a subjective area, it’s hard to critique without some semblance of a creative brief or at least an understanding of the audience. Eric, Tantek and I were a little less forgiving in the code critique, but I think we brought up some really important points and kept it educational for everyone. Tantek’s got a nice write-up of the proceedings over at his site.

    In all, I had a great time at An Event Apart. You may be thinking sure, but you were a speaker, but I am positive I would have enjoyed it equally as much as an attendee. There were great people, great talks and the food was fantastic.

    diff --git a/archives/by-author/aaron-gustafson/P60.html b/archives/by-author/aaron-gustafson/P60.html index 49c5048..ce83bc5 100644 --- a/archives/by-author/aaron-gustafson/P60.html +++ b/archives/by-author/aaron-gustafson/P60.html @@ -316,7 +316,7 @@

    A better createElementWithName()

    -

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    +

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    Read more…

    diff --git a/archives/by-category/programming/P30.html b/archives/by-category/programming/P30.html index 9336e31..ece2ba8 100644 --- a/archives/by-category/programming/P30.html +++ b/archives/by-category/programming/P30.html @@ -192,7 +192,7 @@

    A better createElementWithName()

    -

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    +

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    Read more…

    diff --git a/archives/by-tag/coding/P30.html b/archives/by-tag/coding/P30.html index 140bb59..48f1a13 100644 --- a/archives/by-tag/coding/P30.html +++ b/archives/by-tag/coding/P30.html @@ -161,7 +161,7 @@

    A better createElementWithName()

    -

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    +

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    Read more…

    diff --git a/archives/by-tag/html/P20.html b/archives/by-tag/html/P20.html index 81df6c8..91ae9a9 100644 --- a/archives/by-tag/html/P20.html +++ b/archives/by-tag/html/P20.html @@ -378,7 +378,7 @@

    A better createElementWithName()

    -

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    +

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    Read more…

    diff --git a/archives/by-tag/javascript/P20.html b/archives/by-tag/javascript/P20.html index 1a1e756..32bfcb1 100644 --- a/archives/by-tag/javascript/P20.html +++ b/archives/by-tag/javascript/P20.html @@ -316,7 +316,7 @@

    A better createElementWithName()

    -

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    +

    Back in 2005, I wrote a piece about IE’s abysmal generation of NAMEd elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).

    Read more…

    diff --git a/archives/further-adventures-in-indifference/comments/index.html b/archives/further-adventures-in-indifference/comments/index.html index cf649e7..6d84c39 100644 --- a/archives/further-adventures-in-indifference/comments/index.html +++ b/archives/further-adventures-in-indifference/comments/index.html @@ -100,7 +100,7 @@

    Posted by my email conversation with the unnamed executive at my former employer about the Target.com lawsuit as a new entry. This is mostly for Derek’s amusement, but I thought of a few other things to say on the subject as well.

    +

    As opposed to just adding it to the comments in my original post, I decided to post the continuation of my email conversation with the unnamed executive at my former employer about the Target.com lawsuit as a new entry. This is mostly for Derek’s amusement, but I thought of a few other things to say on the subject as well.

    We’ll start with his response. This is copied directly from his email; I take no credit for the spelling, grammar, etc.:

    I understand all that you are saying. The difference I see is a “public” building like a Target store is an impediment of it doesn’t have a ramp, etc. and it does matter. It is a physical, public places that discriminates if they don’t have the ramps, etc.

    @@ -114,7 +114,7 @@

    Posted by Karova, users surfing the web with disabilities or (shock) JavaScript turned off might be able to choose to shop somewhere other than a Target or a Wal-Mart or any other store which does not meet their accessibility (or availability) requirements.

    -

    Anyway, he hasn’t responded to that last email and perhaps he never will. After all, I gave my notice the next day. And, no, this exchange was not responsible for that in any way.

    +

    Anyway, he hasn’t responded to that last email and perhaps he never will. After all, I gave my notice the next day. And, no, this exchange was not responsible for that in any way.

    diff --git a/archives/further-adventures-in-indifference/index.html b/archives/further-adventures-in-indifference/index.html index 79ff937..57be37b 100644 --- a/archives/further-adventures-in-indifference/index.html +++ b/archives/further-adventures-in-indifference/index.html @@ -100,7 +100,7 @@

    Posted by my email conversation with the unnamed executive at my former employer about the Target.com lawsuit as a new entry. This is mostly for Derek’s amusement, but I thought of a few other things to say on the subject as well.

    +

    As opposed to just adding it to the comments in my original post, I decided to post the continuation of my email conversation with the unnamed executive at my former employer about the Target.com lawsuit as a new entry. This is mostly for Derek’s amusement, but I thought of a few other things to say on the subject as well.

    We’ll start with his response. This is copied directly from his email; I take no credit for the spelling, grammar, etc.:

    I understand all that you are saying. The difference I see is a “public” building like a Target store is an impediment of it doesn’t have a ramp, etc. and it does matter. It is a physical, public places that discriminates if they don’t have the ramps, etc.

    @@ -114,7 +114,7 @@

    Posted by Karova, users surfing the web with disabilities or (shock) JavaScript turned off might be able to choose to shop somewhere other than a Target or a Wal-Mart or any other store which does not meet their accessibility (or availability) requirements.

    -

    Anyway, he hasn’t responded to that last email and perhaps he never will. After all, I gave my notice the next day. And, no, this exchange was not responsible for that in any way.

    +

    Anyway, he hasn’t responded to that last email and perhaps he never will. After all, I gave my notice the next day. And, no, this exchange was not responsible for that in any way.

    diff --git a/archives/i-wish-id-known-that/index.html b/archives/i-wish-id-known-that/index.html index 1907bcf..b899eae 100644 --- a/archives/i-wish-id-known-that/index.html +++ b/archives/i-wish-id-known-that/index.html @@ -101,7 +101,7 @@

    Posted by

    -

    So, upon returning home from SXSW and cracking open the new issue of Seed, I read something I wish I’d known before:

    +

    So, upon returning home from SXSW and cracking open the new issue of Seed, I read something I wish I’d known before:

    Having sex is the best way to prepare for a speech.

    diff --git a/archives/job-newyork-presbyterian-hospital/index.html b/archives/job-newyork-presbyterian-hospital/index.html index 89d1ff7..28680bd 100644 --- a/archives/job-newyork-presbyterian-hospital/index.html +++ b/archives/job-newyork-presbyterian-hospital/index.html @@ -101,7 +101,7 @@

    Posted by

    +

    NewYork-Presbyterian Hospital [logo]

    -->

    The fine follks over at NewYork-Presbyterian Hospital are looking for a designer/developer to join their 5-person Intranet team. This year, they will be redesigning their employee intranet and moving from a static website to a role-based portal. They will also be implementing a new CMS to run the show.So if you’re an experienced designer/developer with good information architecture skills (an ar comfortable working in a Microsoft shop) who is interested in leading a team (not just coding alone in the dark), give them a shout.

    diff --git a/archives/jstrace-two-days-on/comments/index.html b/archives/jstrace-two-days-on/comments/index.html index 47a9c93..e3d9a60 100644 --- a/archives/jstrace-two-days-on/comments/index.html +++ b/archives/jstrace-two-days-on/comments/index.html @@ -100,7 +100,7 @@

    Posted by latest script release, jsTrace, has been fantastic. From the write-up on the DOM Scripting Task Force blog to all of the emails and comments, it’s been great.

    +

    The reception for our latest script release, jsTrace, has been fantastic. From the write-up on the DOM Scripting Task Force blog to all of the emails and comments, it’s been great.

    The past few days have seen many ideas, requests and enhancements sent my way. Some have been rolled into the jsTrace 1.1 release which I made public today. One such enhancement (brought to us by Joe Shelby) I have dubbed “memory,” as it allows the debugging window to remember both its position and size the next time it is opened (via cookies). Further enhancements have been made to the underlying code to streamline development of additional tools for the bottom toolbar and the font size of the bottom toolbar has also been increased (per several requests).

    I hope you all enjoy the improvements. Keep ‘em coming.

    Update: We’ve also been mentioned in DOMScripting.com.

    diff --git a/archives/jstrace-two-days-on/index.html b/archives/jstrace-two-days-on/index.html index 6e3d6b8..3425edc 100644 --- a/archives/jstrace-two-days-on/index.html +++ b/archives/jstrace-two-days-on/index.html @@ -100,7 +100,7 @@

    Posted by latest script release, jsTrace, has been fantastic. From the write-up on the DOM Scripting Task Force blog to all of the emails and comments, it’s been great.

    +

    The reception for our latest script release, jsTrace, has been fantastic. From the write-up on the DOM Scripting Task Force blog to all of the emails and comments, it’s been great.

    The past few days have seen many ideas, requests and enhancements sent my way. Some have been rolled into the jsTrace 1.1 release which I made public today. One such enhancement (brought to us by Joe Shelby) I have dubbed “memory,” as it allows the debugging window to remember both its position and size the next time it is opened (via cookies). Further enhancements have been made to the underlying code to streamline development of additional tools for the bottom toolbar and the font size of the bottom toolbar has also been increased (per several requests).

    I hope you all enjoy the improvements. Keep ‘em coming.

    Update: We’ve also been mentioned in DOMScripting.com.

    diff --git a/archives/leap/comments/index.html b/archives/leap/comments/index.html index 6b2a603..d4fa8c4 100644 --- a/archives/leap/comments/index.html +++ b/archives/leap/comments/index.html @@ -204,7 +204,7 @@

    Comments

    Best of luck to you. You’ll do fantastic, and I have to say that you did a great job preparing yourself for this next step. It starts with all the writing and getting yourself well-known.

    -

    PS: After this entry, I’m not sure I would take your old job. That, and the big shoes I would have to fill.

    +

    PS: After this entry, I’m not sure I would take your old job. That, and the big shoes I would have to fill.