Summary

  • W3C publicly announced an early Amaya binary in August 1996 as a browser and authoring tool built to test Web specifications, with WYSIWYG editing and HTTP PUT publishing.
  • A February 1997 W3C Note described an active client that could browse, edit and publish remote documents in one environment, while publication still depended on permission to write to the server.

Most browsers are built to bring pages home. In August 1996, Vincent Quint announced one that could bring a pencil to the page. W3C's Amaya combined browsing with WYSIWYG editing, CSS, HTML 3.2 and a way to publish on an HTTP server using PUT. Its early binary was offered for the Web community to evaluate and send feedback. The client was a testbed for new specifications, not a stage prop meant to sit beside the standards documents. W3C wanted its own ideas to survive contact with a working interface.

The 1997 W3C Note explains what made Amaya active. A person could retrieve a document, view it, change it and publish it from the same environment. Several documents could be open at once, with browsing and editing available in each. A link could be made by opening the target and clicking the relevant document or anchor, rather than typing an address from memory and hoping the punctuation held. For an author, the Web became a workspace with doors between its pages. For a standards lab, each door was also a test of the protocols and formats it was trying to advance.

Amaya's friendliness had a strict internal backbone. It showed the author a formatted page, yet represented HTML as a structured tree governed by the document type definition. Editing a heading or list through the visual interface changed that structure. The Note openly acknowledged the nuisance: much of the live Web contained malformed HTML. Amaya's parser therefore tried to reshape such documents so they could be opened. When the author edited them, the tool performed valid operations. The browser wanted to work on the messy Web while keeping the result fit for other tools to process. A useful pencil needs more than a pretty nib.

The publishing move was strikingly plain. The Note told authors to save to a URL instead of a local filename, and Amaya would transfer the document and included objects to a remote server. It used GET to fetch, POST or GET for forms, and PUT to publish. The decisive phrase in the Note is that the server must be one where the author is allowed to write. Amaya could make editing feel immediate; it could not turn someone else's server into an open notebook. The client supplied the pencil and the transport. Permission remained a server decision.

That boundary makes Amaya more interesting than a nostalgic tale about a forgotten browser. The 1996 announcement placed WYSIWYG editing, CSS support, HTML 3.2, PNG and PUT in one early release. The 1997 Note shows why W3C cared: a client that could both consume and create Web documents exposed the practical seams between specification, editing model and server behavior. It also shows the cost of that ambition. Real pages had syntax defects; remote servers had gates; a standards testbed had to meet both. The browser could bring a pencil to every page it visited. The server decided where the mark could stay.