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 9FD4678932 for ; Mon, 14 Sep 2015 22:20:36 -0700 (PDT) Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-11v.sys.comcast.net with comcast id HHPQ1r0012Bo0NV01HPQAZ; Tue, 15 Sep 2015 05:23:24 +0000 Received: from eklhad ([IPv6:2601:405:4002:b0a:21e:4fff:fec2:a0f1]) by resomta-ch2-05v.sys.comcast.net with comcast id HHPQ1r0040GArqr01HPQSL; Tue, 15 Sep 2015 05:23:24 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <55F75275.9020305@pcdesk.net> User-Agent: edbrowse/3.5.4.2+ Date: Tue, 15 Sep 2015 01:23:24 -0400 Message-ID: <20150815012324.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1442294604; bh=XNYTywPB3YEtZNTjEJMEf7kRZl0vNE/ASURlDlHnHfM=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=FWNeud4rOMrbES17dJSHzmzN1KnurhOVqO+BQ7yaQH46V/OnkkCEanK04HhxvrmPi 7GDnUTWuOMxlHpVb3Pj6WGZ+wRB/tvynbtpIpe+vTIXVY2X4xAbu3VIQ0+ABL82aii 8aKKxuErWWvUAoSz5Lcar075SJc0ryTuEMAEX/xOpVzfZNmAE3RaSshFIEqbLx8ufl v5O92lvdz6fj0PMAIdVCIVK5oAsHyMxjMLVy4rghKAr9Mmc5Vipo0IcBv2QynE55lM DIgbuDJmPjGQ0hFfhlGRdzsWOIHPJG+UdExn6tMckDR3VWRjXEYf7oBn4ruOWDTDTU C/sC7mNPp7Edw== Subject: [Edbrowse-dev] Fragments X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 05:20:36 -0000 > edbrowse not jumping to #foo, despite
  • There's a history here. Long long ago, the places you could jump to were all A named anchor. But html and js evolved, and you could jump to any tag that had its id attribute set. I implemented this for the most part in the old system, but I don't yet retain these id tags in the buffer in the new system. In other words, I haven't got round to it yet. As a proof of concept, I implemented the
  • tag. It is now present in the rendered buffer, so you can jump to it. I ran your example and it works now. But I only did it for
  • . I didn't do it for other tags. If the next page expects you to jump to #bar, and it has
    that still won't work. So why didn't I do all the tags, or at least the primary set? Because I like to take small incremental steps. Because I wanted to fix tyler's bug quickly, so he can find the next one. And because
  • is unique among the tags and requires special code anyways. Really? What's so special about
  • ? Consider a list where each item is a paragraph. I use to write it like this.

  • apple

  • banana

  • cherry I wrote it that way because it works with edbrowse, and my sighted friends say it works with other browsers, so I thought all was well, but now that tidy is checking up on me I know this is wrong, and I'm sure other web developers do it the right way, like this.

  • apple

  • banana

  • cherry If I render serially, as you would expect, it looks like this. 1. apple 2. banana 3. cherry The number then the paragraph break then the item. (Indeed the old system would do this.) So, what you're suppose to do is just remember that a list item is pending, and on the next occurence of some text, print out the number or the star or whatever and then the text. The rendering action of

  • is delayed. So I also delay, along with the number, the tag indicator of where to jump, so you indeed wind up on the paragraph of the list item. I hope all that was somewhat entertaining. I'll bring in more tags with id set over the next couple days, particularly
    , since that is use the most.