1067142 - URL #anchor not working on this page on fennec (works on desktop)

Status: RESOLVED INVALID

(Web Compatibility :: Site Reports, defect)

Description

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

STR:
- Type or follow URL on Fennec.

Expected result:
- Page loads and immediately jumps to "Note Asynchronous Steps Explicitly",
  like it does on desktop (OSX).

Observed result:
- Page loads at the top of the page.

Tried on 32 and Nightly.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Do other anchors work?

Is the markup sent to fennec the same as that sent to desktop?

Comment 2

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Attachment: beautified html from fennec

(In reply to Boris Zbarsky [:bz] from comment #1)
> Do other anchors work?

Yes, https://developer.mozilla.org/en-US/docs/Web/API/EventTarget#Methods works for instance.

> Is the markup sent to fennec the same as that sent to desktop?

Good guess. No it isn't. Though it contains the same anchor, it doesn't work on either phone or desktop. Attaching it here.

Comment 3

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

s/Good guess/Good point/

Comment 4

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Uh, nevermind.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Neither version of the page has any anchor targets called "note-asynchronous-steps-explicitly".

Both have this:

  <a name="user-content-note-asynchronous-steps-explicitly" class="anchor"
     href="#note-asynchronous-steps-explicitly" aria-hidden="true">


The "desktop" version of the site includes script that looks at hashchange events and manually does scrolling to the right thing, like so:

  function(){
    $.hashChange(function(){
      var t,e;
      if (location.hash&&!document.querySelector(":target"))
        return t = "user-content-" + location.hash.slice(1),
               e = document.getElementsByName(t),
               $(e).scrollTo()
    }
  )

The mobile version has nothing of the sort.

Seems like a basic bug on the github side of things...  I wish they just let the browser handle anchor scrolling instead of playing games and having bogus links.  :(

Comment 6

[Boris Zbarsky [:bzbarsky]]

I'm going to reopen this and move to tech evang, actually.  Please report this issue to github too?

Comment 7

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

I sent an email to their support.

Comment 8

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

An issue has been opened with the github team.

Comment 9

[Hallvord R. M. Steen [:hallvors]]

README.md is now changed, but if we do some digging in history we find an older version to demonstrate the breakage:

https://github.com/w3ctag/promises-guide/blob/2a1fc1df1736f779aa8af6a600188191b9bfe128/README.md#note-asynchronous-steps-explicitly

Comment 10

[Mike Taylor [:miketaylr]]

Let's close this, the doc has since moved to https://www.w3.org/2001/tag/doc/promises-guide.