- From: Sam Ruby <rubys@intertwingly.net>
- Date: Fri, 10 Oct 2014 10:20:23 -0400
- To: Domenic Denicola <domenic@domenicdenicola.com>
- CC: "www-tag@w3.org" <www-tag@w3.org>
- Message-ID: <5437EB27.3080309@intertwingly.net>
On 10/10/2014 08:39 AM, Domenic Denicola wrote: > From: kosmo.zb@gmail.com [mailto:kosmo.zb@gmail.com] On Behalf Of David Sheets > >> If you insist on calling a set of browsers the web platform, please include web servers, deployed software, and development libraries which also implement the standards you seek to achieve. > > In actuality the URL Standard is super-important for web servers and libraries as well. I think if you survey them you will find that servers and libraries conform much more to the URL Standard than to the RFCs it obsoletes. > > Anecdotally at least, in Node.js we initially implemented the RFCs, only to find out that this was incompatible with lots of web content and we had to implement several extensions to be deployable on the wider web and especially within the enterprise. At the time we did not know about the URL Standard (I am unsure it existed at that time) but looking back most of our extensions were indeed things covered by the URL Standard. It's amazingly great that Anne was willing to take the time to specify these things that are necessary for web compat---not just for browsers but for servers as well. I'd be glad to add node.js to the set of implementations I'm tracking. Can you verify that the attached testnodejs.js captures the results correctly? You can run this yourself if you download [1] and [2]. Also, I have node.js v0.10.26 here. Is that current enough or should I run with a different version? - Sam Ruby [1] https://raw.githubusercontent.com/w3c/web-platform-tests/master/url/urltestdata.txt [2] https://raw.githubusercontent.com/w3c/web-platform-tests/master/url/urltestparser.js
Attachments
- application/javascript attachment: testnodejs.js
Received on Friday, 10 October 2014 14:20:51 UTC