lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: firefox 3 problems


From: Patrick McCarty
Subject: Re: firefox 3 problems
Date: Sun, 19 Oct 2008 15:36:50 -0700

On Sun, Oct 19, 2008 at 3:24 PM, Reinhold Kainhofer
<address@hidden> wrote:
>
> Am Montag, 20. Oktober 2008 schrieb Patrick McCarty:
>> On Fri, Oct 17, 2008 at 2:12 PM, Neil Puttock <address@hidden> wrote:
>> > 2008/10/17 Werner LEMBERG <address@hidden>:
>> >> for me, using Firefox 3.0.3, the `back' button doesn't work while
>> >> viewing lilypond-big-page.html as compiled with the CVS version of
>> >> texi2html (and today's git version of lilypond) -- only the anchor
>> >> changes properly in the URL line, but nothing happens otherwise.
>> >>
>> >> Until now, I've never seen this.  Is this a bug in Firefox or a
>> >> problem with the lilypond page?
>> >
>> > It must be a page problem, since I get the same behaviour in Opera 9.60.
>>
>> Is anyone still having this problem,
>
> It happens in Opera 9.25 (Linux) as well as Firefox 3.0.3 (Linux and Windows
> running under wine), Galeon 2.0.4 (Linux), IE 6 (running in wine), which I
> just tested:
> 1) Open the LM big page
> 2) Click on e.g. "2.1. First steps" in the TOC
> 3) Click on e.g. "4.1 Tweaking basics" in the TOC
> 4) Press back... The URL changes to the anchor of 2.1, but the page position
> stays at the contents of 4.1 :((
>
> I haven't tested it with konqueror, since konqueror doesn't handle the anchors
> at all... It seems we are really good at pushing everything over the edge
> (texinfo, texi2html, browsers, etc.) ;-)
>
> I didn't find any browser where this works :(((

Oh, I completely misunderstood.  Yes, I've always wondered about this
problem, as the same behavior occurs in every browser I've tested.
I'm pretty sure the problem is at the browser level.  Maybe the HTML
4.01 specification dictates this behavior.

I was under the impression that this used to work for some users, and
it recently broke.

-Patrick




reply via email to

[Prev in Thread] Current Thread [Next in Thread]