Profile_bird

Hey there! Hixie is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving Hixie's tweets.

Already using Twitter
from your phone? Click here.

Hixie

  1. @arun I think http://www.crockford.com/html/ says everything there is to be said about his credibility on the topic, really.
  2. @jklmnop <p>?
  3. @Malechite my pleasure. :-)
  4. @gcarothers It's the same as what the HTMLWG does to the WHATWG, so I don't really see a problem. How would _you_ have it work?
  5. @gcarothers ...and I've been mentioning this regularly since then... How much more advance notice should we have given? :-)
  6. @gcarothers The W3C was informed in November 2006 that we'd be going to last call in October 2009: http://bit.ly/fHYYx
  7. @gcarothers I mentioned it in http://bit.ly/16Gafk
  8. @gcarothers They're exactly the same from the table of contents on down. It's a joint project.
  9. @gcarothers Last Call at the WHATWG, not the W3C. See the end of the WHATWG blog post for details: http://bit.ly/BJUOh
  10. @shepazu Now's the time to send feedback if you know of things that aren't ready!
  11. @shepazu it was an automatic decision when we hit zero known issues
  12. HTML5 is at Last Call at the WHATWG! http://bit.ly/BJUOh
  13. @robinberjon i dunno, i'm at a loss as to what the UI should look like if a random server asks for proxy auth credentials
  14. @robinberjon well presumably if you're getting it from a proxy, you would prompt the user for credentials and then resend the request, no?
  15. @robinberjon but how do you know it's from the server and not a proxy?
  16. what does an HTTP client do when an HTTP _server_ (not proxy) replies with 407? What _should_ it do?
  17. @peirix validator.nu might not have the changes we made to the <footer> content model... @hsivonen has been working on other things
  18. @peirix you can
  19. @drewlesueur It'd be like a browser that doesn't implement the same-origin security model correctly: don't use browsers with security flaws.
  20. @drewlesueur Sure, but the only person who could be affected by a browser that lied would be the user of the browser