Closed Bug 1273607 Opened 8 years ago Closed 5 years ago

Dismissing of NotificationBox scrolls to top of page

Categories

(Core :: XUL, defect)

48 Branch
x86_64
All
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: davejustishh, Unassigned)

Details

(Whiteboard: btpp-followup-2016-07-05)

When we show a NotificationBox (heartbeat or Test Pilot or w/e else) and the notification box is dismissed, the box disappears, but then the web page is scrolled to the top.

Linux 4.2.0-36-generic
Firefox Dev Edition version 48.0a2
Ubuntu 15.10

Steps to reproduce:
1) Navigate to a longish page and scroll down a bit (https://en.wikipedia.org/wiki/Anarchism#Spanish_Revolution)
2) Open up browser toolbox console and execute:
`bar = gBrowser.getNotificationBox(); bar.appendNotification('label', 'value', 'invalid.png', bar.PRIORITY_INFO_LOW, [])`
3) Dismiss notification with the 'x' icon.
4) if on linux, notification will disappear and page will scroll to top.
This also happens on Windows. Do you know if this is a regression?

Dolske, any thoughts here (sorry, blame)?
Flags: needinfo?(dolske)
Flags: needinfo?(djustice)
OS: Linux → All
Whiteboard: btpp-followup-2016-07-05
I can't reproduce this on OS X or Windows 10. Is this in a new profile? Does E10S / APZ have any effect?

The relevant code is http://searchfox.org/mozilla-central/source/toolkit/content/widgets/notification.xml

I'm not sure how this would be happening -- the notification doesn't touch web content. The only vaguely related thing is that the slide in/out animation affects the size of the <browser>, so if there's some bizarre and indirect scrolling/layout bug there...

A regression range would be helpful, especially if this is difficult for others to reproduce.
Flags: needinfo?(dolske)

The project I was seeing this on originally has been discontinued, it's been 3 years with no other reports, may be worth closing :/

Flags: needinfo?(djustice)

Thanks!

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.