Navarr's Tech Side » (X)HTML 5

Making More Natural Desktop Notifications in Chrome

Navarr — Tue, 09 Nov 2010 03:40:01 +0000

Do you have a website or application that uses Google Chrome Desktop Notifications? Well, let me just share with you this very simple snippit of code that will make their interaction a lot more natural.

Code block    

>
>
	 charset="utf-8">
	>
		html * { font-family: sans-serif; }
		h1 { padding: 0; margin: 0; font-size: 12pt; font-weight: bold; }
		body { font-size: 10pt; }
	>
	>
		function changeLinks() { for(var i = 0;i < document.getElementsByTagName("a").length;i++) { ele = document.getElementsByTagName("a")[i]; ele.target = "_blank"; } }
		function detectClick(e) { var rightclick; if (!e) { var e = window.event; } if (e.which) { rightclick = (e.which == 3); } else if (e.button) { rightclick = (e.button == 2); } if (rightclick) { self.close(); } }
	>
>
 onload="document.timeout = setTimeout(self.close,5000);changeLinks();" onmouseover="clearTimeout(document.timeout);" onmouseout="document.timeout = setTimeout(self.close,5000);" onmouseup="detectClick();">
	 style="display:block;cursor:normal;padding:0;margin:0;color:black;text-decoration:none;" onclick="self.close();" href="/link/" target="_blank">
		>Title>
		>Message>
	>
>>

Thats really all there is to it. Lives on a 5 second time. If you hover over it, it stays longer, if you right click it it closes. If you click it it goes to /link/. Quite nifty, if I do say so myself.

Its slightly buggy regarding links in the message.. but meh.

Making Google Analytics Work in XHTML

Navarr — Sun, 04 Apr 2010 16:37:29 +0000

I was moving my website, Google Voice for Outlook, over from HTML5 to XHTML5 today, and as soon as I did the basic content negotiation filters in PHP so that it would send the appropriate headers if the client supported XHTML as well as only outputting the

The fix was simple, replace the current four line inclusion code with:

Code block    
<script type="text/javascript">
	var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
	var script = document.createElement("script");
	script.src = gaJsHost + "google-analytics.com/ga.js";
	script.type = "text/javascript";
	document.getElementsByTagName("head")[0].appendChild(script);
script>

This will work fine, unless of course you have no head tag. In which case you should replace getElementsByTagName(“head”) with getElementsByTagName(“html”).

HTML5 Being a Pain in My Ass Again

Navarr — Sat, 03 Apr 2010 14:09:32 +0000

This time in regards to the highly acclaimed and very well received element.

On my website, Google Voice for Outlook I use the tag to show a demonstration of the system working. I don’t currently have a way to encode in ogg, and/or am too lazy too, so I decided that if the web browser didn’t support h264 video, it’d fall back to the YouTube video. The expected result (from me, of course) was that if it can’t display the video, it’d display the YouTube. Apparently though, in FireFox it does not fall back to the YouTube video and instead just displays a gray box, and the fault this time doesn’t lie with FireFox, but with the standard:

Content may be provided inside the video element. User agents should not show this content to the user; it is intended for older Web browsers which do not support video, so that legacy video plugins can be tried, or to show text to the users of these older browsers informing them of how to access the video contents.

Ugh! This means that if you want to use on any website, ever, properly, you’re going to have to encode it in both h264 and Theora until the industry decides on a set standard.

Purely Atrocious.

Needed in (X)HTML 5 – An extension to the Meta Tag

Navarr — Tue, 02 Feb 2010 23:07:25 +0000

I was thinking today, while reading an article about redirect – that there is currently no way to accurately and semantically tell a user/bot that a web page is located somewhere else when you only have access to static (X)HTML files. However, there is a workaround a lot of people use that dampens usability, and there is an attribute whose name would seem to imply that a way to do it should be possible.

By this of course, I’m referring to .

Currently, people wanting to relocate their web pages rely on an older value to this tag that seems to have been originally designed for moving one person from one page to another in a set increment of time:

This doesn’t appear to be what this value should be used for, and has very negative consequences for search engines and parsers. Instead, don’t you think we should be using http-equiv to its full potential?

To this, I propose the addition of , to properly match the HTTP Header for redirection.

I think there should be two ways to use this:

and

Obviously, the second example gives us both a *three digit* HTTP Code, and the URL for redirection. Since HTTP codes are only three numbers (though in the future may be greater digits) there still should not be any problem.