874027 - Scrolling to #anchor does not work with plugin on page

Status: RESOLVED WONTFIX

(Core :: Layout, defect, P5)

Description

[Alice0775 White]

Attachment: Reduced archive. open http://127.0.0.1/bug873926/index.html#readme

This is spun off from Bug 873926

Steps To Reproduce:
1. Extract archive into local HTTPD server
2. open http://127.0.0.1/bug873926/index.html#readme 

Actual Results:
Page does not scroll
Reloading by clicking Reload Button does not scroll.
Reloading by keypress Enter in Location bar scrolls to anchor.

Expexted Results:
Page should scroll at initial loading

Regression window(m-c)
Good:
http://hg.mozilla.org/mozilla-central/rev/b506d48ef7aa
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/20120131 Firefox/13.0a1 ID:20120131133632
Bad:
http://hg.mozilla.org/mozilla-central/rev/15b00ab7f22d
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/20120131 Firefox/13.0a1 ID:20120131135732
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b506d48ef7aa&tochange=15b00ab7f22d

Regressed by: Bug 90268

Comment 1

[Benjamin Smedberg]

Is serving it via HTTP necessary? This WFM when I load it from a file: URI (with click-to-play active, at least).

What parts of this testcase are necessary? The .css file is empty: can the testcase just be the single .html file?

Comment 2

[Alice0775 White]

(In reply to Benjamin Smedberg  [:bsmedberg] from comment #1)
> Is serving it via HTTP necessary? 
Yes. it is necessary in my enviroment.

>This WFM when I load it from a file: URI
Me too.

>(with click-to-play active, at least).
I do not know.

> What parts of this testcase are necessary? The .css file is empty: can the
> testcase just be the single .html file?

A empty CSS file is necessary in my environment.

Comment 3

[John Schoenick [:johns]]

There's a copy of this at http://people.mozilla.com/~jschoenick/bug873926/

Bug 90268 moves some scroll position listeners around for plugin tags, and the test case has an <object> tag. There's nothing that stands out though, it may just be tickling an underlying layout issue