Open
- Open Everything Hong Kong 2008 活動已經完滿結束
- 創用 CC 網頁多媒體編撰套件 網頁設計 CC 實例
- 親愛的Firefox,請原諒我的花心 LOL Quote: 其實Chrome的兄弟姐妹都過得不怎麼樣,這就是有錢家庭(Google)的小孩被寵壞的下場
Blog
I don't just mean that they should fail gracefully when thefeeds aren't well formed (although that's an important part ). There are all sorts of troublesome things thatfeeds can do; they can be longer than you expected, for example, or theycan be sent to you very slowly. In all of these cases, feed aggregatorsshould try to fail gracefully, to extract as much information from thefeed as possible unless it is utterly clear that something horrible hasgone wrong and you cannot
There is a pragmatic problem with strict XHTML validation (well, several,but I'm only going to pick on one right now). It goes like this:
Strict XHTML validation in the browser clearly punishes users . If there is more than a trace amount ofactual XHTML problems, this means that not doing strict validation issignificantly more user friendly and thus a significant advantage forany browser that is not XHTML strict.
Given that you are punishing people by failing strictly, you areeffectively engaged in a giant game
(星島日報報道)倪震與周慧敏發表聲明宣布分手,事前明顯沒有知會父親倪匡,本報
Let us suppose that you want to create an environment that insuresthat XHTML stays valid XHTML. The corollary of how validationfailures should punish the person actually responsible for them is that the site author should bepunished for invalid XHTML, and you need to punish them directly.
So let's make the web server itself validate your XHTML; if it's notvalid, it doesn't get served. Does this punish the site author? Notnecessarily, because in order for the site author to notice they have
Open
Blog