Tag: web

dom-checker

A simple utility to thoroughly validate DOM, XMLHttpRequest, and cookie security restriction handling in modern web browsers. Notable features include exhaustive hierarchy crawling, cross-domain IPC system for blind write verification, page transition

.aspx considered harmful

I guess I’m extra-sensitive to the .aspx thing now that I work for Microsoft, because I know that to folks outside the Microsoft ecosystem it screams: We don’t get the web. It’s true there are plenty of .php and other extensions floating around on the web. But non-Microsoft-powered sites are far more likely to suppress them than are Microsoft-powered sites, because you have to go out of your way to get IIS and ASP.NET to do that. I hope that cool URIs will become the default for Microsoft-powered websites and services. Meanwhile, there are a variety of add-on URL rewriters for IIS that can streamline and normalize web namespaces. I wish they were used more extensively.

Jon Udell it only took them 10 years to get clean urls. wtf?

Acid3

Now the top 4 browsers have either released or announced a version of their browser that passes Acid2 work on Acid3 has restarted and Ian Hickson has been adding testcases over the last few weeks. Acid3 is primarily concerned with ECMAScript and the DOM though Selectors Level 3, Media Queries, and data: URIs are also tested. The idea of the test is to run 100 ECMAScript functions that either return true (pass) or false (fail). I believe 16 of those functions are missing at the moment and people are encouraged to contribute. Tests need to be justified by a specification at W3C Candidate Recommendation, W3C Recommendation, or equivalent for non-W3C consortia, and be from 2004 or before. I believe that if browsers once again commit to fixing the bugs found by this test Web authoring will improve tremendously.