This is page 1, displaying results 1-6

W3C Password Reset

Published:

By: Ted Guild

  • security

JavaScript required for basic textual info? TRY AGAIN

Published:

By: Dan Connolly

Sam says he's Online and Airborne. "Needless to say, this is seriously cool." I'll say! But when I follow the link to details from the service provider, I get:Sorry. You must have JavaScript enabled to view this page. Click the...

  • html
  • javascript
  • security
  • web-architecture

How to evaluate Web Applications security designs?

Published:

By: Dan Connolly

I could use some help getting my head around security for Web Applications and mashups. The first time someone told me W3C should be working on specs help the browser prevent sensitive data from leaking out of enterprises, I...

  • html
  • security
  • webapps

Interview: David Baron on Firefox 3 and W3C Standards

Published:

By: Ian Jacobs

At the news of the official release of Firefox 3 (FF3), I asked David Baron, Mozilla's Advisory Committee Representative at W3C (see photo), a few questions about the browser release and support for standards. Note: I anticipate interviewing (lots...

  • css
  • firefox
  • html
  • security
  • standards
  • svg
  • xforms

If you had to fix the Web...

Published:

By: Karl Dubost

"If you had to fix the Web... what would you do?"

  • auto
  • css
  • html
  • http
  • security
  • usability
  • w3c

When Widgets Go Wrong

Published:

Widgets provide front-ends to all kinds of information sources on the Web; several thousand are available for download. Obviously, the use of Web technologies has been a huge success here, enabling people to adapt their programming experience from the Web to their local platform. With the Web programming platform, though, come the Web's programming practices and security issues, sometimes with more serious consequences than before.

  • ajax
  • javascript
  • json
  • security
  • widgets