サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
iPhone 16
hsivonen.fi
The string that contains one graphical unit consists of 5 Unicode scalar values. First, there’s a base character that means a person face palming. By default, the person would have a cartoonish yellow color. The next character is an emoji skintone modifier the changes the color of the person’s skin (and, in practice, also the color of the person’s hair). By default, the gender of the person is und
Since version 56, Firefox has had a new character encoding conversion library called encoding_rs. It is written in Rust and replaced the old C++ character encoding conversion library called uconv that dated from early 1999. Initially, all the callers of the character encoding conversion library were C++ code, so the new library, despite being written in Rust, needed to feel usable when used from C
It was suggested at the Mozilla Summit that there isn’t good information around about what Encrypted Media Extensions (EME) actually is. Since I’m on the HTML working group and have been reading the email threads about EME there, I thought that I could provide an introduction that explains things that may not be apparent from the specification itself. TL;DR EME is a JavaScript API that is part of
Now that Firefox 10 has been released, none of the major browsers send only Chrome sends the Accept-Charset HTTP header. During the Firefox 4 development cycle, I noticed that IE, Chrome and Safari were not sending the Accept-Charset HTTP header in their HTTP requests. This meant that the Web had to work even without browser sending that header. It was already obvious that Accept-Charset was obsol
WebM-Enabled Browser Usage Share Exceeds H.264-Enabled Browser Usage Share on Desktop (in StatCounter Numbers) Looking at StatCounter stats, it occurred to me that they might not match the common narrative about H.264 market share. I decide to run some numbers using StatCounter stats. It turns out that during the first two weeks of 2012, on desktop, the usage-share of browsers that support WebM in
TL;DR: I think vendor prefixes are hurting the Web. They are hurting Web authors. They are hurting users of browsers. They are hurting competition in the Web browser space. I think we (people developing browsers and Web standards) should stop hurting the Web. It would also make sense for browsers to implement other browsers’ prefixed features to the extent existing content uses prefixed features.
A new implementation of the View Source HTML and XML syntax highlighting has landed in Firefox. Why? The reason there is a new implementation is that the old implemention was based on the old HTML parser that we want to get rid of. The old View Source implementation was standing in the way of the goal to remove the old parser. Also, the old parser did some incorrect highlighting. Most notably, it
I have been reading tweets and blog posts expressing various levels of disappointment and unhappiness about schema.org not using RDFa, not using Microformats or not having been developed in the open with the community. Since other people’s perspectives differ from mine, I feel compelled to write down my take. Disclaimer: I’m only speaking for myself on my own time and initiative. Expect blatant bi
In Firefox 4, script execution changed to be more HTML5-compliant than before. This means that in some cases sites that sniff for Firefox or Gecko may break. If you use LABjs… You should update to LABjs 1.0.4 (or later). If you use the “order” plug-in for RequireJS… You should update to RequireJS 0.15.0 (or later). If you use the multi-file version OpenLayers… You should switch to the single-file
So the W3C finally announced that the XHTML2 WG will be taken off life support at the end of 2009. I’m annoyed that Zeldman used the F-laden TLA “WTF” instead of “AFT” in title of his post about the announcement. Moreover, many of the comments on Zeldman’s post indicate that there are people who are badly misinformed about the matters surrounding this announcement. To help remedy that, here’s some
Henri Sivonen’s pages Articles encoding_rs: a Web-Compatible Character Encoding Library in Rust encoding_rs is a high-decode-performance, low-legacy-encode-footprint and high-correctness implementation of the WHATWG Encoding Standard written in Rust. chardetng: A More Compact Character Encoding Detector for the Legacy Web chardetng is a new small-binary-footprint character encoding detector for Fi
Browsers have supported the PNG bitmap format for quite some time. But still, even though PNG files can either be made smaller than GIFs or, alternatively, can contain more colors, lots of Web designers keep using JPEGs and GIFs. In fact, even designers who (for other reasons) don’t care about old browsers still often haven’t made the switch to PNG. Is it just about being stuck with the old ways o
In order to deal both with content written according to Web standards and with content written according to legacy practices that were prevalent in the late 1990s, today’s Web browsers implement various engine modes. This document explains what those modes are and how they are triggered. Summary for the Impatient The main conclusion to draw from this article is that you should start all your HTML
このページを最初にブックマークしてみませんか?
『Henri Sivonen's pages』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く