11.06.07
Gordon Brown appears to have his role confused with the monarch’s
07.31.07
Odd Google/ie7 Bug
Hello, haven’t posted for ages again. Been hunting giant children for sport in a far-away land.
Here’s an odd bug. Search for something in Google, then try clicking between the Search “the Web” and “pages from the UK” options (assuming you’re from the UK, if not then substitute as is obvious) under the search text box. If you’re in Firefox it should be fine. If you’re in ie7, you may not be. Sometimes the click doesn’t respond at all, and sometimes only when the mouse is hovering over the edge of the circle (so it highlights in yellow), but not in the middle (where it doesn’t have a yellow highlight).
Strange, no? Anyone else get that?
11.30.06
Combined Internet Framework
I’ve played with AJAX in the past, but have always found it quite limiting. XMLHttpObject is still quite a clumsy object to call, and AJAX doesn’t abstract detail away from me as nicely as it could. It also doesn’t interact well with other common Web technologies, such as Flash.
Enter the Combined Internet Framework. Obviously some developers far cleverer than me decided to solve this problem, and created a framework which is lightweight and fast, but is also easy to develop with and allows easy interaction between common Web/communication technologies such as AJAX, Flash and JML.
I’ll say no more, but it’s pretty exciting. The website’s here.
10.27.06
IE7 and the comment hack
IE7’s not bad. Getting close to Firefox 1 in terms of features. Firefox 2 however is ace, especially with its spell-checking, spangly glasspane interface and session restoration.
They have fixed some of Internet Explorer’s more glaring CSS errors (it’s great that they stopped pretending IE was any good and just admitted it wasn’t. I know I shouldn’t feel like this, but I’m glad it finally stopped any arguments from web developers who thought that IE was a good browser.) Unfortunately, some of the bugs were useful in distinguishing IE from not-IE, so one could use a bug advantageously. For example, only IE (before IE7) would recognise a CSS rule starting with *html. So any rule written with that at the start only had to work with IE. But no more!
Now, there are very few ways (other than HTML conditional comments) to direct broken, IE-specific CSS to IE. Here’s one.
Just use the // comment. IE (including version 7) only seems to recognise /* …. */ as a comment, and ignores the double-slash, treating anything after it as interpretable CSS. Firefox doesn’t.
Any more browsers people have that they can test it with? Try here.
10.02.06
The Answer
Relic got quite close. The answer to the problem is that the value of A changes. You can’t do that 