W3C home > Mailing lists > Public > site-comments@w3.org > January 2003

Re: history vs xframes vs frames

From: Tim Berners-Lee <timbl@w3.org>
Date: Thu, 9 Jan 2003 10:41:26 -0500
Cc: site-comments@w3.org
To: "Mr. Raymond Kenneth Petry" <pdqbanker@justice.com>
Message-Id: <D0128F36-23E8-11D7-8E78-000393914268@w3.org>
Dear Mr Petry,

There are days when one would like things different, and one
for a moment forgets all the reasons why they are as they are:
the issues and needs of different people all needing to use the
technology, and the hard work together which made a standard
come out in the end.

Of course, I cannot help you with your javascript problems.

The only thing I can do is point out that as far back as I can remember,
FAQs have always been Frequenty Asked Questions.

Tim BL

On Wednesday, Jan 8, 2003, at 17:45 US/Eastern, Mr. Raymond Kenneth 
Petry wrote:

> Dear Sirs and Madams:
>
> 1. You're becoming historic: FAQs are now, Frequently Answered 
> Questions! [They always were, I think]
>
> 2. xframes or frames are an older discussion than you let-on: 
> Documents should have been self-framable---so, when noone listened 
> some months, I did it in javascript...meaning, HTML became historic...
>
> -.b. Of course, HTML should have been simpler, and had built-in 
> javascript, and had intrinsic text on everything:
> <href="window.open('http://w3.org','newhistoricwindow','noresize')" 
> "the-big-idea-little-yellow-pop-up-onmouseover text">w3.org</href>
>
> 3. Frames, are window-tables in the head instead of document-tables in 
> the body....
>
> 4. I've been working several days trying (again after years hiatus) to 
> get MSIE (5.5, this time) to capture onmouseup within a frame--a frame 
> of document.selection.createRange().text. At the moment I've 
> discovered that document.onmouseup=capturetext only detects click 
> events on the window edge 2px (or 10px of the white space between 
> frames border=0 framespacing=10 frameborder=10)...but---
> -.b. doesn't like the netscape's [undefined] "e" object...can't get 
> passed the if (e.which||e.button) detection clause...however---
> -.c. document.addEvent("onmouseup",capturetext) differs by declaring 
> netscape's "e" object is an "[object]" and, does get passed the 
> if-clause detection---MSIE crawled over to netscape...weird!
> -.d. frame onmouseup=capturetext doesn't do anything!
>
> I think HTML should be cleaned up, instead of revised...there's so 
> much more (<table><tr> should be one row without the redundant <td>; 
> <tc> should be column(s)---<tr> and <tc> and <td> are all the same 
> thing but with defaulted preferential dimension "options")...and...
>
> I'm about to rewrite the spec. for .HTML, and publish my results as 
> .HYPE!
>
> /rkp
>
>
>
>
>
> Mr. Raymond Kenneth Petry, Director
> pdqbanking services division of Lanthus Corporation
> Lanthus Surrogate Executive Accessions Management
> 1-8019982364 1-2063507450
> 1-206-350-7450
>
> _________________________________________________
> FindLaw - Free Case Law, Jobs, Library, Community
> http://www.FindLaw.com
> Get your FREE @JUSTICE.COM email!
> http://mail.Justice.com
>
Received on Thursday, 9 January 2003 10:41:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 24 October 2012 16:21:27 GMT