From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) by hurricane.the-brannons.com (Postfix) with ESMTPS id BFD5C797B5 for ; Mon, 27 Feb 2017 09:34:32 -0800 (PST) Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-11v.sys.comcast.net with SMTP id iPA3ccWGFEyOCiPC6cheKe; Mon, 27 Feb 2017 17:34:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1488216882; bh=SZABjSSbnPYoHrVR4lMKY3e77TNIXxGuZ3dp2bHe0oU=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=Ela1/Pn45Zl07NCXlmTDI8wqwFJvLAxIBMVSualF5SW4N14pX8lqt7r0Mi2lNBTpO RnO3zJJpUiQ5LeP23NIpA9M4Flx2D+Ql6KbThfLd+faTjCm33YPDTTDCTc601LZKBU x2hGRP3jqa1wCcS8CWLdtmB90zcYq0LtopIqBDqCGbdcD42m4Rdpw11awywN7HRw3W rM2i91qX+O7B/I+Dcr8TK47a6JpggF2HLP02piGsp9FU0ZskgeSeWNiJ5Gzi1z07fs KkB0m2MiDxJgy8+oq4Ry1mtZDQaL1nnUi/hbpzNV3uYPU4iGAMTn/nMpX0datj8rPA 3Odej5uJIl8/Q== Received: from unknown ([IPv6:2601:408:c301:784d:21e:4fff:fec2:a0f1]) by resomta-ch2-12v.sys.comcast.net with SMTP id iPC6cN0kJRzW6iPC6cvgsA; Mon, 27 Feb 2017 17:34:42 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.6.2+ Date: Mon, 27 Feb 2017 12:34:41 -0500 Message-ID: <20170127123441.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfNGuSk17RXjhSvz/Vvc1buxUf83CzRfdK6Il+Qeky1c0SRC0CmLiyWnDGqdfNjVZuGQ8b4LMtoxbjVZMC47Ex9V+d7uxL85mATObZxXft+Ip7UjJcwc2 JNSUJh0H4zYXqkD3WYFrfYdTw6S+NbwEvPpw7zC6jYldWSYv35eEU5Dr Subject: [Edbrowse-dev] thoughts on frames X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 17:34:33 -0000 This is way to long for the irc. I am both optimistic and pessimistic about frames. Version 1 allows you to expand a frame inline, instead of the g command that expands it in a new buffer. It works, pretty much. Browse jsrt and look at line 4. Expand it with the exp command. (Contract not yet implemented.) So far so good. Still problems though, a frame in space.com causes a seg fault when I expand it. So still bugs to fix. When finished, version 1 will allow expand and contract of frames inside a window, which is neat, and worth doing I suppose, but it will not make a single website accessible to us that is not already accessible. No progress there. Version 2 might let the js worlds interact. The window can see the js objects in the frames etc. I have no clue, no flippin clue, how to do that. I'm sure it's a lota lota work, and I believe it would gain us almost nothing. One more acid3 test would pass, but I think very few websites do that, or need that functionality. Frames tend to be independent ads, or videos, and that's it. Rather, the vast majority of inaccessible websites will be brought into the fold by Kevin's find&fix work. That's where the real world problems are. That's where the rubber meets the road. That's what I believe anyways. So I will get frames version 1 working, but not sure if or when I will get round to frames version 2. I don't think it's a lot of bang for the buck. As always, I welcome opposing points of view. Karl Dahlke