av9ash/GitBugs huggingface dataset:
Bug: AdblockPlus plugin blocks some webpages to work correctly
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-01-05 11:38:11+00:00
Resolved: 2020-01-05 15:02:31+00:00

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

Testing environment: Windows7 SP1 on desktop computer, Firefox 71.0 (64bit), AdblockPlus plugin installed (https://adblockplus.org/, version 3.7) and active.

1. Go to webpage www.idnes.cz and choose article to read. Most articles contains image gallery, which can be opened by clicking to images in the article - try to open the galerry. Here are some links for testing:
* https://www.idnes.cz/zpravy/domaci/jiri-matej-bruna-vysokoskolak-sest-titulu-rozhovor.A191217_161640_domaci_brzy/foto
* https://www.idnes.cz/revue/spolecnost/victoria-beckhamova-navrharka-velka-britanie-vzhled-sebevedomi.A200103_122502_lidicky_bib/foto
* https://www.idnes.cz/premium/sluzby/atlas-mraku-film-zdarma-online.A191230_151519_premium-sluzby_bhar/foto
* https://www.idnes.cz/cestovani/po-cesku/zanikle-trate-27-kadansky-rohozec-doupov-zeleznice-trat.A200103_123524_po-cesku_vrja/foto/VRJ807780_53stkuxx_18.10.2019_fotopetrovsenk.jpg


Actual results:

When Adblockplus plugin is active, gallery does not show. Screen show loading icon, but images do not show. Clicking Previous (<) and Next (>) buttons has no effect.

When plugin is disabled at all or disabled for specific site idnes.cz, gallery works normally, images are shown.
Same behaviour was seen at computer with Windows 10 installed.
AFAIR, thing get broken after update from Firefox 70 to 71.


Expected results:

Even with AdplockPlus plugin active image gallery should be shown.

This bug has probably relation with bug 1607064 (https://bugzilla.mozilla.org/show_bug.cgi?id=1607064)
Bug: Pictures have red tint due to Canvas Defender add-on
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-01-05 15:51:23+00:00
Resolved: 2020-01-07 12:06:06+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

Sometimes pictures on websites have a red tint (most times this is an issue with pictures uploaded by myself).

This time it's visible on this page: https://displate.com/displate/1213267


Actual results:

Interestingly during page load all pictures can be seen in their true, untinted color.
After a short period it then gets tinted red.
(See attached screenshot)
Bug: enterprise policy forces privacy.resistFingerprinting to true
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-01-05 18:50:53+00:00
Resolved: 2020-01-08 17:51:21+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Launch Firefox with and without a policies.json, check the user agent it reports back.


Actual results:

Without the enterprise policy I get "Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0", with it I get "Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Firefox/68.0".


Expected results:

The correct user agent (Linux 71.0) should be reported even when enterprise policies are enabled.
Bug: Wrong numbering of ol with nested ul.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-01-06 09:15:02+00:00
Resolved: 2020-01-08 20:30:40+00:00

User Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

I Have a ordered list containing more  unordered lists seperated be on li of the orderlist. 

After each ul the next li in the ordered list hast the number of the next element in the embedded ul not the next number of the ol


Actual results:


    test1
        test1
        test2
        test3
    test2
        test1
        test2
    test3
        test1
        test2
        test3
        test4



Expected results:

test1
test1
test2
test3
test2
test1
test2
test3
test1
test2
test3
test4
Bug: Crash in [@ mozilla::ipc::IProtocol::ChannelSend] called from Document::GetFailedCertSecurityInfo
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-01-06 10:11:27+00:00
Resolved: 2020-01-17 07:09:56+00:00

This bug is for crash report bp-e7a94e34-28c0-4ecf-8b4b-ff1410200105.

```
Top 10 frames of crashing thread:

0 xul.dll mozilla::ipc::IProtocol::ChannelSend ipc/glue/ProtocolUtils.cpp:487
1 xul.dll mozilla::dom::PContentChild::SendIsSecureURI ipc/ipdl/PContentChild.cpp:2372
2 xul.dll mozilla::dom::Document::GetFailedCertSecurityInfo dom/base/Document.cpp:1804
3 xul.dll mozilla::dom::Document_Binding::getFailedCertSecurityInfo dom/bindings/DocumentBinding.cpp:5635
4 xul.dll mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions> dom/bindings/BindingUtils.cpp:3151
5 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:544
6 xul.dll Interpret js/src/vm/Interpreter.cpp:3038
7 xul.dll js::RunScript js/src/vm/Interpreter.cpp:424
8 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:580
9 xul.dll js::jit::DoCallFallback js/src/jit/BaselineIC.cpp:2905

```
This is not a new crash, it seems to have started in version 69.0. It seems to involve `failedCertChain` so maybe it's related to bug 1555438? Just a guess, I don't know this code very well.

It's happening mostly on Windows but there's Linux crashes too with the same stack so it's probably not platform-specific.
Bug: Maximizing window after bookmarking causes address bar to consume toolbar and trigger overflow
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-01-06 10:17:08+00:00
Resolved: 2020-01-23 08:46:31+00:00

STR:
1. Click the bookmark star button.
2. With the bookmark panel still open, maximize the window.

The address bar fills the toolbar and the toolbar items overflow. Happens when the window is resized during the bookmarking animation which starts immediately after the bookmark panel being closed. The library icon may also float in an odd location until the bookmarking animation is finished.

After animation completes the address bar can be corrected by re-maximizing or resizing the window larger than the original size when the problem occurred.

Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ac5fc1e491a2bb5481d47247bea3c2b22318001c&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505

Regressed by Bug 1580538.
Bug: The card context menus from the "Recommended by Pocket" and "Highlights" sections are not fully visible if the browser is horizontally resized
Status: NEW
Priority: P3
Created: 2020-01-06 12:48:50+00:00
Resolved: 2024-02-26 12:20:47+00:00

**[Affected versions]:**
- Firefox Nightly 73.0a1 - Build ID: 20200106092427

**[Affected Platforms]:**
- Windows 10 x64
- Mac 10.15.2
- Ubuntu 18.04 x64

**[Prerequisites]:**
- Have a Firefox profile with the "browser.search.region" pref set to "US" in the "about:config" page.
	
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover the "Recommended by Pocket" card displayed in the third position.
3. Click the menu button displayed in the top-right part of the card.
4. Resize the browser horizontally to 75% and observe the displayed context menu.

**[Expected result]:**
- All the context menu elements are correctly displayed and fully visible.

**[Actual result]:**
- The context menu is not fully visible.

**[Notes]:**
- This issue is reproducible with any card from the "Recommended by Pocket" section.
- This issue is also reproducible with the card context menus from the "Highlights" section.
- Attached a screen recording of the issue.
Bug: search suggestions on google.com not displayed
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-01-06 15:17:13+00:00
Resolved: 2020-01-30 07:57:43+00:00

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko

Steps to reproduce:

open google.com type into search box. Using nightly.


Actual results:

google suggestions are not displayed correctly.


Expected results:

List of google search suggestions should be displayed.
Bug: Do not implement WebGPU spec.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-01-06 16:36:34+00:00
Resolved: 2020-01-06 19:18:06+00:00

WebGPU spec has issues mentioned in https://github.com/gpuweb/gpuweb/issues/534 . Despite that one of the spec repo maintainers behaves like they are by design. It may make sense not to implement the spec at all. If Google prefers to implement it, it should be a problem of users of their browser only.
Bug: Syncing storage-sync-crypto: request failed: Error: HTTP 507 Insufficient Storage
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-01-06 18:58:30+00:00
Resolved: 2020-01-10 08:35:14+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Synced Firefox.  Get the error msg in my sync logs.  It looks like it's trying to sync storage for extensions I no longer have.  I have maybe 4 of these but the rest are not on any of my devices.  I tried removing all of my sync'd devices and syncing again but it's not fixing anything.

Please secure file if it contains sensitive info.  I think it's just a log file of hashes of extensions, though.


Actual results:

I get this error message when syncing


Expected results:

Sync succeeds with no errors
Bug: Firefox lags whole computer
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-01-06 19:24:51+00:00
Resolved: 2020-02-03 09:51:35+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

Open any tab. Wait and browse the site until the Browser lags out the whole computer.


Actual results:

It stops any sounds from playing and all YouTube videos begin to load


Expected results:

The software should not stop all processes on my computer
Bug: Private Browsing Window data kept in parent process memory after closing
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-01-06 19:29:14+00:00
Resolved: 2024-05-30 17:06:09+00:00

Based on the significance of Private browsing stated as (1) "Private Browsing automatically erases your browsing information, such as passwords, cookies, and history, leaving no trace after you end the session."  within https://support.mozilla.org/en-US/kb/private-browsing-use-firefox-without-history  & (2) "Reality: Private Browsing works by removing cookies, browsing history, and passwords stored while you are browsing once you close your Private Window" within https://support.mozilla.org/en-US/kb/common-myths-about-private-browsing - it was identified that even after closing all the active tabs/windows of Private browsing still passwords and other sensitive information could be retrieved from OS process memory.

Description: While one opens private browsing and accesses any website, the parent process runs in background where the sensitive information is being saved. This leads to information leakage from process memory with privileged user even after all instances of Private browsing window is closed.

Exploitability rational: Attacker needs to have alternate local privilege account within same system (e.g. corporate environment where Sys. admin/IT support team is victim and another employee having Windows account can exploit) or needs to have physical access of victim user's account. No specific user interaction required once victim closes Private browsing window. Till the parent process is alive credentials should be accessible and for that the Normal browser instance should not be closed (this is possible since users may have multiple websites opened while surfing which they do want to access later on).

Impact: Primarily Loss of Data confidentiality. And there by causing Integrity and Availability loss based on if credentials are found (which would help account takeover).

Impacted version: Firefox 71.0 for Windows 10 64-bit 

STR:
1. Launch Mozilla Firefox in Windows user1 (Admin or non-admin anything will work).
2. Start Private browsing window and access some website and provide login credentials
3. Close all instances of Private browsing window (Do not close normal firefox window)
4. Now dump process process memory using tools like Task Manager of Windows or Process Hacker2 to extract strings. Search for Strings within firefox process (if multiple are there then manually check in all or using Process Hacker2 use filter)
5. Previously typed credentials would be found in the above process even if private browsing tab is closed.
6. Optionally login as user2 (Admin), it would be possible to dump above credentials in same way by this user also.


Video POC:
www.nestedif.com/temp/video_poc/Mozilla Firefox Private Browsing - Sensitive Information Disclosure.mp4


Recommendation:
Spawn new Parent-Child process while new Private window is launched. And kill both of them once it is no more required. e.g. Microsoft Edge or IE browser.
Bug: Intermittent browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-01-06 20:13:37+00:00
Resolved: 2021-05-04 17:01:04+00:00

**Filed by:** nerli [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=283656837&repo=mozilla-esr68
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/H3R53x2uT0mpGphCyVVpOw/runs/0/artifacts/public/logs/live_backing.log

---

17:20:52     INFO - TEST-START | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js
17:20:52     INFO - GECKO(1892) | 2020-01-06 17:20:52.956 firefox[1892:12662] Persistent UI failed to open file file:///Users/cltbld/Library/Saved%20Application%20State/org.mozilla.firefox.savedState/window_1.data: No such file or directory (2)
17:21:37     INFO - TEST-INFO | started process screencapture
17:21:37     INFO - TEST-INFO | screencapture: exit 0
17:21:37     INFO - Buffered messages logged at 17:20:52
17:21:37     INFO - Entering test bound 
17:21:37     INFO - TEST-PASS | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | Default zoom is 100% for about:mozilla - 
17:21:37     INFO - TEST-PASS | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | Zoom is changed to 110% for about:mozilla - 
17:21:37     INFO - waiting for mutation of attribute 'label'.
17:21:37     INFO - TEST-PASS | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | mutation occurred: attribute 'label' changed to '100%' from 'null'. - 
17:21:37     INFO - TEST-PASS | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | Default zoom is 100% for about:robots - 
17:21:37     INFO - waiting for mutation of attribute 'label'.
17:21:37     INFO - Ignoring mutation that produced value 100% because of filter.
17:21:37     INFO - Ignoring mutation that produced value 100% because of filter.
17:21:37     INFO - Ignoring mutation that produced value 100% because of filter.
17:21:37     INFO - Buffered messages finished
17:21:37     INFO - TEST-UNEXPECTED-FAIL | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | Test timed out - 
17:21:37     INFO - Cleaning up.
17:21:37     INFO - GECKO(1892) | MEMORY STAT | vsize 7638MB | residentFast 402MB | heapAllocated 127MB
17:21:37     INFO - TEST-OK | browser/components/customizableui/test/browser_934951_zoom_in_toolbar.js | took 45174ms
17:21:37     INFO - checking window state
Bug: browser.bookmarks.onChanged event has datedAdded 1000x too high
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-01-06 22:19:59+00:00
Resolved: 2020-02-15 09:58:51+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

Bookmark a web page on Firefox mobile.  Then wait (or force) synchronisation to desktop browser via Firefox Sync.


Actual results:

The "dateAdded" field in the event (supposed to be milliseconds since epoch) is 1000 times too high.


Expected results:

The "dateAdded" field should be in the correct number of milliseconds since epoch.
Bug: Session is not restored
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2020-01-07 03:35:28+00:00
Resolved: 2024-01-25 12:33:00+00:00

I'm consistently seeing a trivial (but annoying) issue on a mac machine: session doesn't get restored, FF always start with a new fresh session. That, despite the "Resource previous session" clearly enabled.
Bug: Everything looks large, including image, tab width when "Large Text" is enabled from Linux OS preferences
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2020-01-07 07:43:07+00:00
Resolved: 2020-01-07 19:02:21+00:00

Linux MINT cinnamon 19.

Reproducible: always

Steps To Reproduce:
1. mint menu - Preferences - Accessibility -  Visual
   turn on "Large Text"
2. Start Nightly

Actual Results:
Everything looks large, including image, tab width.

Expected Results:
Text only should be large.
Bug: Re-enable tracking protection messages
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2020-01-07 09:14:34+00:00
Resolved: 2020-02-18 11:02:05+00:00

Need to bring back the TP messages disabled by bug 1603483.
The trigger rename bug 1604563 did not make it to 72 so the messages might only be re-enabled for 73+ depending on how the profiler data looks like for 72.
Bug: Pinned tabs order are reversed every time Nightly is restarted
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-01-07 13:33:51+00:00
Resolved: 2020-02-18 15:40:30+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Build ID: 20200107095722

### Steps to reproduce
1. In a new profile, pin 2 or more tabs, preferably with different favicons to differentiate them easier.
2. Restart, or close & reopen Nightly.

### Actual result
Order for pinned tabs are reversed.

### Expected result
Order remains unchanged.

This is regressed by bug 1242912. Is bug 1606633 related?
Bug: Pinned tabs are jumping out of their normal position while being dragged
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2020-01-07 15:15:10+00:00
Resolved: 2020-01-19 18:25:58+00:00

**Affected versions**
* Firefox 72.0 (BuildId:20200103162918)
* Firefox 73.0b1 (BuildId:20200106175743)
* Firefox 74.0a1 (BuildId:20200107095722)

**Affected platforms**
* Windows 10 64bit.
* Windows 10 32bit.
* Windows 7 32bit.
* Ubuntu 18.04 64bit.
* macOS 10.11

**Steps to reproduce**
1. Launch Firefox.
2. Open around 20 tabs.
3. Pin several tabs.
4. Drag a pinned tab in order to change its position.

**Expected result**
* The pinned tab is successfully dragged and placed in a new position without any UI issues.

**Actual result**
* It seems that during the drag event the pinned tab shifts downwards (outside of its normal position), overlapping the beneath buttons.

**Regression Range**
* This seems to be a regression: 
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0b0779e6ebe39537f30b6bed33a0201f0434d308&tochange=e7c2e224629a2245860707cc92080b204014f61b
* This issue seems to be caused by Bug 1576946 - Remove nsStackFrame platform code

**Notes**
* For further information regarding this issue please observe the attached screencast.
* It seems that this issue is only reproducible if multiple tabs are opened ( until the tab navigation buttons ( "<" and ">" are displayed).
Bug: Search engines don't respect top sites ordering
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-01-07 15:37:49+00:00
Resolved: 2020-01-08 01:06:32+00:00

STR:
1. On the new tab, click the meatball menu above the top sites section and add a search engine to your top sites.
2. Move that search engine to spot #2 - #8 in the top row.
3. Navigate to any website and click into the address bar and you will see the search engine you added to top sites in the #1 position instead of the position you placed it in.

Expected result:
The list of top sites in the address bar dropdown should match the content and order of the first row of top sites on the new tab/home page.
Bug: about_home_topsites_first_paint scalar is recorded on first about:home sighting even if it wasn't the first page loaded
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2020-01-07 20:02:24+00:00
Resolved: 2020-02-20 15:09:53+00:00

STR:

0. Ensure Firefox is configured to load about:home by default, and not to restore the previous session.
1. Launch Firefox Nightly via `./mach` with `./mach run https://www.mozilla.org`.
2. Once the initial tab finishes loading, open a new tab, and browse to `about:telemetry`
3. Choose "Scalars" along the left-hand side, and note that the `about_home_topsites_first_paint` scalar is (correctly) absent.
4. Open a new window.
5. Reload about:telemetry

ER:

The `about_home_topsites_first_paint` scalar should still be missing.

AR:

The `about_home_topsites_first_paint` was recorded.

This might account for some of the truly egregious measurements we're getting on the `about_home_topsites_first_paint` probe, which is supposed to measure the time between process start and rendering the initial about:home.
Bug: Remove from Toolbar option is disabled for What's New button
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-01-07 20:30:56+00:00
Resolved: 2020-01-07 21:37:10+00:00

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Updated Firefox to new version. "What's New" button is displayed next to menu button. In its context menu "Remove from Toolbar" option is disabled.


Actual results:

Impossible to remove this button from toolbar.


Expected results:

I don't care about What's New after updating, as I usually read change log before update. It would be great to have option to permanently hide "What's New" button from Toolbar. I'm not sure, but I think on previous version "Remove from Toolbar" option was not disabled, although button is still displayed, so it probably did not work.
I know that it will disappear after clicking, but I would like to prevent it appearing after next update.
Bug: WebVR/WebXR turns Steamvr chaperone boundaries off for controllers
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-01-07 22:22:54+00:00
Resolved: 2020-01-07 22:49:33+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Open a webvr or webxr page in firefox. I have tested with different pages. I noticed the issue today after the ff (developer and public) update.


Actual results:

The Steamvr (v1.9.16) chaperone boundaries detection of the controllers turns off. No boundaries detection off the controllers for all, even you close firefox. You need restart Steamvr for the detection works again.


Expected results:

The Steamvr chaperone boundaries detection should work correctly.
Bug: History and bookmarks not syncing, sent tabs never arrive, one synced device not visible
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-01-07 23:27:01+00:00
Resolved: 2020-01-09 02:20:46+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

Have four synced devices (Windows desktop, two Windows laptops and Android phone).
Sending tabs between devices does not work, sent tabs never arrive.
When sending tabs one of the devices (Android 9 Phone, Firefox 68.3.0) is not visible from other devices, but all devices are visible from the phone.
History and bookmarks are not syncing.
Tried signing out from Firefox account and singning back in on all devices, nothing changed.
Attached the most recent error-sync log file from about:sync-log.



Actual results:

Sent tabs never arrive, history and bookmarks not syncing, one of the devices not visible


Expected results:

Sent tabs should arrive, history and bookmarks should sync, all connected devices should be visible.
Bug: Session Restore Buttons are Misaligned
Status: RESOLVED
Priority: P2
Resolution: DUPLICATE
Created: 2020-01-07 23:28:59+00:00
Resolved: 2020-01-14 19:35:18+00:00

To reproduce, go to about:sessionrestore in trunk.

The buttons for restore/start new are aligned to the far left, and vertically stacked. The issue is purely aesthetic.