<Glazblog/>

For those who did not notice, the Twitter REST api was upgraded a week ago.

1. get the following email from addons.mozilla.org:

We've noticed that Glazoom is a very popular add-on which is not yet compatible
with Firefox 3.1. We'd like to update you on our progress with Firefox 3.1, as
well as provide some help and resources to make the transition as painless as
possible.

(...)

We ask that you please check your add-on for compatibility with the latest beta,
and if everything looks good, bump your maxVer on addons.mozilla.org (AMO) to
"3.1b3".

(...)

2. udpate extension as suggested bumping maxVersion to 3.1b3
3. submit it to addons.mozilla.org
4. get the following error message:

   The following errors were found in install.rdf:
   3.1b3 is not a valid version for Firefox

Webslices/Webchunks. My secret dream was a smooth integration of Webchunks into Places so the user's personal toolbar could contain Webchunks just as it can contain bookmarks, folders, feeds, microsummaries. But adding a new consumer to Places is anything but a trivial operation because Places' consumers are almost hard-coded in Places itself... I think Places should evolve into a consumer-agnostic architecture where bookmarks and all others are only consumers of Places and do not require a single line of code added to Places itself. A well documented and easy to understand API could trigger a new class of extensions to Firefox that other browsers could not immediately or easily afford. Places2 ?

Spot on. Including CSS and tables.

Although devmo does not list at this time a type attribute on <xul:iframe>, it's really a goooood idea to add type="content" to your iframe elements if you're a XUL author and if you're using those iframes to reach arbitrary remote resources. If you don't, the remote resources have chrome access to the container of the iframe...

I discovered this a few minutes ago because my current XULrunner-based app contains a XUL iframe and that iframe reached a document containing the following lines:

if(window.self != window.top &&
   !document.referrer.match(/https?:\/\/[^?\/]+\.anonymized\.com\//))
{
  top.location.replace(window.location.pathname);
}

Of course, that piece of script trashed all my XUL and replaced it with the remote HTML page... I'm sure you don't want this in your own app. Use type="content" on iframes unless you really want chrome access in your iframe.

So MIcrosoft is saying that Obama's blackberry is a security risk. This is such a joke. Let me tell you a true story about Microsoft Windows... A true story that did not happen to a third party but happened to me...

A few years ago, I was in Seattle for a CSS WG meeting hosted by Microsoft in Redmond. Like most of the CSS WG members, I was statying in a motel. Wifi did not exist at that time. Hotel rooms did not have ethernet access either. We relied on modem access (Hixie, that's the meeting when I told you "you're too young and fanatic and I was the same a few years ago", was it 1998 ?).  I used my laptop's internal modem to reach Electricité de France's network, retrieved my email, replied to urgent messages, and disconnected everything. I checked twice that the connection was dropped. Then I called my wife. And I heard that beeeeeeeptrrrrrtrtrtr that is so specific of a modem connection in the phone. I noticed I left my laptop's phone link connected and I immediately disconnected it. My phone was connected to something. Something was stealing data from my computer. When I came back to EDF R&D campus, I paid a little visit to the local security adviser and told him about this. He laughed. He laughed a lot. I still remember his words  "come on, you're so naive, we all know about that... Never trust again Microsoft Windows and a phone or internet connection in a hotel in the US, ok?".

And Obama 's blackberry is unsecure because it's canadian ? BWAHAHAHAHA !!!!!

According to Wired,

• The target for CSS support in IE8 is full and complete support for CSS2.1.
• The only CSS3 module in IE8 is writing-mode (for vertical text support). IE has supported this since version 5.x, so it will continue to do so.
• IE8 will not support CSS' border-radius, which is often used to make rounded corners without images. Microsoft's Chris Wilson confirms that border-radius support is "high on the wish list," though, and should make its way into the next release after IE8.

Full CSS 2.1 complete support is cool but it must be said that "full CSS 2.1 support" does not mean anything yet. CSS 2.1 is not yet a W3C Recommendation and it does not have an approved full Test Suite yet. Microsoft has submitted a rough 7,000 CSS 2.1 tests to the CSS WG but these tests need review before becoming official.

I am a bit surprised that Selectors are not fully or almost fully implemented in IE8. IE8 will then be far from Gecko, Opera and Webkit in terms of Selectors. Keeping a too low level on Selectors is a door open to CSS hacks based on selectors' sniffing, and that's a true disappointment to me.

If you want to send G.W.Bush a present for his last day at the White House, send pretzels