jcolebrand

101 reputation

bio	website	jcolebrand.info
	location	Plano, LA
	age	33
visits	member for	2 years, 6 months
	seen	Jan 20 at 7:10
stats	profile views	14

I'm now working for a group out of Plano, doing primarily front-end work for mobile and online banking for credit unions. Time for me to get involved in the local user groups!

combined Stack Exchange profiles for jcolebrand

You probably want to gmail me if you need me directly. If I have to tell you what gmail address to guess at, you're not trying hard enough.

Everything else can be found at http://jcolebrand.info or http://about.me/jcolebrand

	101 reputation	bio	website	jcolebrand.info	visits	member for	2 years, 6 months
3 badges		location	Plano, LA		seen	Jan 20 at 7:10

summary answers questions tags badges favorites bounties reputation activity

16 Actions

suggestions reviews revisions comments badges posts accepts all

Jun 25	comment	Should plus be encoded in mailto: hyperlinks? I disagree. "email addresses" are very peculiarly defined, and must be treated with some care in the first place. That standard is very confusing. Fortunately, we get to disagree here.
Jun 25	comment	Should plus be encoded in mailto: hyperlinks? I am not entirely familiar with that grammar, however, it lists the characters as separate from the unreserved pool, which indicates that + is a reserved character. It does not indicate that it must be encoded. Microsoft says to encode it. C'est la vie, I wait to see.
Jun 25	comment	Should plus be encoded in mailto: hyperlinks? well I did make a specific note of what Microsoft affirms works...
Jun 25	comment	Should plus be encoded in mailto: hyperlinks? that seems .... backwards in spirit to the way I read the instructions initially.
Jun 25	comment	Should plus be encoded in mailto: hyperlinks? `Since there are no reserved characters it should be encoded.` ummmm that doesn't make any sense.
Jun 25	revised	Should plus be encoded in mailto: hyperlinks? corrected some grammar
Jun 25	awarded	Editor
Jun 25	revised	Should plus be encoded in mailto: hyperlinks? I made it right and added references
Jun 25	suggested	suggested edit on Should plus be encoded in mailto: hyperlinks?
Jun 25	comment	Should plus be encoded in mailto: hyperlinks? The problem is the application parsing the URI request. If it expects to receive URLEncoded data then it will decode the data, but that is neither fair to you (to falsely encode) nor to the client (to make assumptions). The protocol does not dictate the encoding expected, the client does. See the further edits I make to the A by @Wez
Nov 14	answered	What new cross-browser features can we use if we drop support for IE6?
Nov 2	awarded	Supporter
Nov 2	comment	The Sitemap Paradox @Jeff Atwood "@John still,..." that's the point that I was attempting to make. It was beneficial at first, but now you don't need it. So why do you persist in trying to have it?
Nov 2	comment	The Sitemap Paradox @Frank ... that's what I'm trying to say!!! `;)`
Nov 1	awarded	Autobiographer
Nov 1	comment	The Sitemap Paradox I thought sitemaps were more of a simpler tool for a simpler age... I kind of figured the only reason to provide a sitemap nowadays was for human assistance in navigating the site, albeit technically inclined humans. I don't see a problem with "if your site isn't being properly crawled (for whatever reason), using a sitemap will not help you!" but it may just be me.