From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 15FCA797B5 for ; Sat, 4 Mar 2017 03:31:32 -0800 (PST) Received: by mail-wr0-x243.google.com with SMTP id g10so16073739wrg.0 for ; Sat, 04 Mar 2017 03:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=v0XrYyLF2Mv1w+SxRoD4fPHM282oFYjKoC/Oz/Db1u8=; b=EsExhMI/x4OPQLmrHlQXdYcN9KePSvnJku4xmQNS6k+uvID+UyH7Z6z3jMdKR+5Vww Z1T24vXYxUn6Hzvh1qmav2PXOowhaF6+XRtMOdMxRAgSsDRzbyEOD+/WDb9dgVkehh/9 Ko+0wOG46erPVVUEUBV05JJkQ22IRENnxjFUOdYoFPP8kCh5TdKS7sAfYsRQxI1Kysy5 c9G8Rf8hcZ9ceLFqqU0LBuulaO5X2c/kGgYs3d1Pgj61sI8dwiUB7haqKtjWgCOWaXQF h7IqaBF+ZLG41mDyY86jYqp7Aa+WX/joBwODIfaO7TXAlCqZafA/OwEES6+kCl7/qRYv GbMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=v0XrYyLF2Mv1w+SxRoD4fPHM282oFYjKoC/Oz/Db1u8=; b=naMsQCNiKz30Lhmh9GUTmflalLAbM0txL9YmL8ODKLXsRSO7zrV3/rq85oypmg068L r8D/fXBGVfRj4yHFOLtEomkfpB1sYH/Cqr9zQFxEv2+0GGqZhBLy3DBqrVJqyB6jYEE6 pAk5vcofd1eoFlc8TG4/jjtkRRAfY0h/mwPY0/OT40Cfc9dgDI2NUx3KQdBGRtylq5p+ HBkj4aJglr9JUPgG9eAi/S3mvONzvNNKFgdk+cULck3NWxXLzBhea8lQHuqJ9rBgP3Q3 NEHnBD5zAuLEF9fNihXJIsur4u9IXnDhjKaVtsM5HR1xRNRPXQln7FeLcA0UYQou+K73 1nuw== X-Gm-Message-State: AMke39l+0a8IcKMg9Js2zliUB4OVQCkLUD/zmbZeMMvtLwwirXPmx608o6yZc9ONJ2EaIw== X-Received: by 10.223.170.3 with SMTP id p3mr7352721wrd.100.1488627109466; Sat, 04 Mar 2017 03:31:49 -0800 (PST) Received: from odin (odin.sdf-eu.org. [178.63.35.194]) by smtp.gmail.com with ESMTPSA id 36sm18860377wrk.57.2017.03.04.03.31.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Mar 2017 03:31:48 -0800 (PST) Date: Sat, 4 Mar 2017 11:31:33 +0000 From: Adam Thompson To: Kevin Carhart Cc: Karl Dahlke , Edbrowse-dev@lists.the-brannons.com Message-ID: <20170304113133.GA27435@odin> References: <20170127123441.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [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: Sat, 04 Mar 2017 11:31:32 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sorry, have been having much work done on the house so my home internet connection has been a bit patchy hence why it's taken a while for me to rep= ly. Anyway, I think the js objects in frames thing is may be more common than w= e'd expect, depending on what sites are used. I'm not sure how much work it'd = be to implement such a thing as js access between frames yet, but it looks like t= here may be some way to do this in spidermonkey at least; I think that's what all that cross-compartment stuff is for. I'm not sure how that'll work from our side though since I'm unclear as to whether compartments need to share a js context or something... I'll try and have a look. On Mon, Feb 27, 2017 at 09:48:13PM -0800, Kevin Carhart wrote: >=20 > Hi Karl >=20 > One observation I have is that I think find & fix and the spec-based > approach have converged. The javascript in the acidtests.org page is a l= ong > series of scenarios to work on and fix. And this is a good thing, I thin= k, > because (a) you know that there will be bang for the buck in the time you > spend on something, since they have hand-designed the scenarios based on > what they exemplify. And (b) the writing style of this code is very huma= n. > It's indented, it's commented, the variable naming has a cleanness to it = and > doesn't have variables like 'a', 'b', 'c'. So I think acid3 and find&fix > are basically the same thing, even if the scenarios we wanted to investig= ate > are not the ones about frames. >=20 > On frames in particular, if there's an impasse, there's an impasse.. if y= ou > don't know how to write it, I seriously doubt that I do. >=20 > But, do you think there is any subset of these situations which might only > live on the JS side and then be discarded? For instance, suppose a frame= is > used as temporary storage, or in order to do a Towers of Hammurabi manuev= er > and put your interconnected nodes down in a frame, to rearrange them and = put > them back in the main document. >=20 > Is this worth pursuing? I can't quite tell what the example in acid3 is > trying to exemplify, but I think 'doc', the side document that is defined= as >=20 > var doc =3D iframe.contentDocument; >=20 > is only intratest. It produces a pass/fail result and so doc doesn't have > to create side effects. Maybe later in another scenario it does, but we = can > try to deal with this test and then take it from there. >=20 > Kevin >=20 >=20 >=20 >=20 > On Mon, 27 Feb 2017, Karl Dahlke wrote: >=20 > >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 ex= pand 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 accessi= ble 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 no= thing. > >One more acid3 test would pass, but I think very few websites do that, o= r 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 g= et 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 > >_______________________________________________ > >Edbrowse-dev mailing list > >Edbrowse-dev@lists.the-brannons.com > >http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev > > >=20 > -------- > Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists > _______________________________________________ > Edbrowse-dev mailing list > Edbrowse-dev@lists.the-brannons.com > http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJYuqWVAAoJED6sZNk+oYF/EcUP/iefNQPpXxi3jJZ0fd5bJy8r ImWPOoZCkIORXhRxwLuAF9OFu/k/S1PvnV3w+FwuO8MkMJQC76venCAdd9wGw0+4 MvbJboFjgm7MJgiVUMTKIHR6abOA5/V9hASzPWxDxVj/DMCbe3Fvw6CDHtJDbKBB UKyLl9qFRwGSK4vsRMQFqea6t6oOdASkN74TMGd8gL6pD0fJXRSvgGAFW59Hl4JC tXXN2nM46zhya42yViHSKxLM8mYysGa9QUFVq2VIc0ea6HQH1x6oiAyz4TQWIRgJ VqMblC7yLS8uWzOBKW6c+Mn1x9w+m7c9LHnP/7cR1Q/rbY6vZSEiDN4rjPnyQwGG 3I/Vi1p80DWWX75+5g1M+JoQ9rIbjnrdcS2N0ZPYhRGEcdWRlKDP5kwW0629rr51 Wy/+HHMB2UC2dOF6jm+Dka1mNAsU5AlMXsuiW1X/lcSEGsMQC1TAIvnjqwxwNeib OPbvrV1jtcBvyobiNdIaPC/cFtYjUTZrN7DDBlKHpZl52Dmg4UaNbucEt+IuJAKf gFSw8MKGFhSJk6ZjsfL3HNohsEYWRbTLqUnq31YitzW05Ix7WL68UHLXvsVEcUvL liIWZ38HKRtKCoI/OtO9sF4KCWcXRI0SC7x1TgXqYNl2affrybmsHgRnBEwgwjvY EFpyJRDZ1z9IzWsVjubP =JDrq -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--