We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

'What's new' page broken

  • 2 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 3 views
  • Last reply by Jens Lyn IV

Jens Lyn IV
Jens Lyn IV
more options

The 'what's new' page displayed after updating 35.0.1 to 36 is broken - no buttons can be clicked. A carefully-timed interrupted page refresh gives me what I assume is the intended result. Removing "?oldversion=35.0.1" from the URI also unbreaks the page.

The 'what's new' page displayed after updating 35.0.1 to 36 is broken - no buttons can be clicked. A carefully-timed interrupted page refresh gives me what I assume is the intended result. Removing "?oldversion=35.0.1" from the URI also unbreaks the page.
Attached screenshots

தீர்வு தேர்ந்தெடுக்கப்பட்டது

hi Jens_Lyn_IV, this is probably caused by the ctr extension. what would normally happen is a doorhanger panel appearing under the menu button, offering to take a tour through the new features of the release...

Read this answer in context 👍 0

All Replies (2)

philipp
philipp
  • Moderator
more options

தீர்வு தேர்ந்தெடுக்கப்பட்டது

hi Jens_Lyn_IV, this is probably caused by the ctr extension. what would normally happen is a doorhanger panel appearing under the menu button, offering to take a tour through the new features of the release...

Jens Lyn IV
Jens Lyn IV கேள்வியின் உரிமையாளர்
more options

Thank you. I tried disabling my other extensions, but not CTR; the UI breaks in a weird way if CTR is disabled, and I have to manually restore it after reenabling the extension.

I thought there was no way to suppress the post-update 'what's new' page, but I discovered the browser.startup.homepage_override.mstone entry in about:config after submitting this question and set it to ignore.