From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:a4e7:4600:12bf:48ff:fe7c:5584]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id A972D77F9B for ; Tue, 11 Mar 2014 06:49:05 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20140210082719.eklhad@comcast.net> Date: Tue, 11 Mar 2014 06:47:45 -0700 In-Reply-To: <20140210082719.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 10 Mar 2014 08:27:19 -0400") Message-ID: <87zjkwx2wu.fsf@mushroom.PK5001Z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] Setters and Post Scan X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2014 13:49:06 -0000 Karl Dahlke writes: > The fact that js could completely rearrange the page, > makes it likely that we will move away from setters and towards > a post scan for these things. I think so. I don't think it would really be feasible to handle a fully dynamic page in setters. How expensive is this going to be in terms of runtime? -- Chris