Opened on 03/24/2014 at 01:05:11 PM

Closed on 03/19/2015 at 09:39:44 PM

Last modified on 05/07/2015 at 11:56:19 AM

#206 closed change (fixed)

Add a pre-configurable option to disable the first run page in Firefox

Reported by: treed873 Assignee: fhd
Priority: P3 Milestone: Adblock-Plus-2.6.9-for-Firefox
Module: Adblock-Plus-for-Firefox Keywords: growth, large-scale-deployments
Cc:, simona, sebastian Blocked By:
Blocking: #542, #2347 Platform: Unknown
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):

Description (last modified by fhd)


Is there a way to disable the first run tab from opening for new users in a domain? I have set up adblock plus to self install on a thin client system, where the C drive is static. Bottom line is, when a user logs in, they are basically a new user every time. Therefore they will receive the "Adblock Plus has been installed" page every time they log in.

What to change

Add a preference to skip the first run page.

Attachments (0)

Change History (27)

comment:1 Changed on 03/24/2014 at 01:10:15 PM by mapx

  • Type changed from defect to change

comment:2 Changed on 03/24/2014 at 01:17:16 PM by mapx

feature requested too by few chrome users

comment:3 Changed on 03/24/2014 at 01:18:22 PM by mapx

  • Priority changed from Unknown to P3

comment:4 Changed on 03/26/2014 at 11:59:34 AM by greiner

Currently, it is not implemented but we could introduce a setting for that which we'd check in the function that opens the first-run page and prevent it from being opened.

comment:5 Changed on 03/26/2014 at 01:06:04 PM by treed873

That would be a welcomed addition.

As a temporary workaround/hack, I simply removed this section of code from ui.js:

function notifyUser()
      let {addTab} = require("appSupport");
      if (addTab)
        addTab(window, "chrome://adblockplus/content/ui/firstRun.html");
        let dialogSource = '\
          <?xml-stylesheet href="chrome://global/skin/" type="text/css"?>\
          <dialog xmlns="" onload="document.title=content.document.title" buttons="accept" width="500" height="600">\
            <iframe type="content-primary" flex="1" src="chrome://adblockplus/content/ui/firstRun.html"/>\
                               "data:application/vnd.mozilla.xul+xml," + encodeURIComponent(dialogSource),
                               "_blank", "chrome,centerscreen,resizable,dialog=no", null);

This seems to work well in our environment.

comment:6 Changed on 03/26/2014 at 02:09:19 PM by philll

  • Component changed from Adblock-Plus-for-Firefox to Core
  • Description modified (diff)
  • Ready set
  • Summary changed from Firefox: disable First Run for corporate domain environment to Disable First Run for corporate domain environment

comment:7 Changed on 03/28/2014 at 08:33:18 AM by Gingerbread Man

I simply removed this section of code from ui.js:

That requires either not updating Adblock Plus, or redoing the changes every time. You should be able to accomplish the same thing without modifying Adblock Plus by locking the extensions.adblockplus.currentVersion preference.

Stores the last used Adblock Plus version, this will trigger actions that need to be done on upgrade or first install

comment:8 Changed on 03/28/2014 at 04:25:50 PM by treed873

I have the Preferences locked in my mozilla.cfg file:

// disable application updates
pref("app.update.enabled", false)

It will still show the first run tab every time. There really isn't an option that I can see that will enable me to disable this.

comment:9 Changed on 04/08/2014 at 07:40:09 AM by mapx

  • Cc added

comment:10 Changed on 04/08/2014 at 04:47:52 PM by fhd

  • Component changed from Core to Adblock-Plus-for-Firefox

IMO this is a pretty platform-specific issue, so I'm changing the component for this to Firefox again.

I've filed #278 about implementing this in Chrome.

comment:11 Changed on 04/13/2014 at 06:13:25 AM by Gingerbread Man

pref("app.update.enabled", false)

  1. That preference isn't locked.
  2. What does disabling Firefox updates have to do with this issue? I'm saying try adding the following to mozilla.cfg:
    lockPref("extensions.adblockplus.currentVersion", "2.5.1");

comment:12 Changed on 04/15/2014 at 10:50:45 AM by treed873

Yes, I see what you mean about disabling Firefox updates, but I really don't see how disabling ABP from updating will fix this either. Because of my environment (see above), ABP sees every login as a new user, therefore it will always bring up the Welcome tab.

comment:13 Changed on 10/21/2014 at 12:32:00 PM by sebastian

  • Blocked By 1487 added

comment:14 Changed on 10/21/2014 at 01:54:02 PM by sebastian

  • Blocked By 1489 added; 1487 removed
  • Platform set to Unknown

comment:15 Changed on 10/21/2014 at 02:06:11 PM by sebastian

  • Blocking 542 added
  • Description modified (diff)

comment:16 Changed on 10/21/2014 at 04:35:28 PM by sebastian

  • Summary changed from Disable First Run for corporate domain environment to Add a pre-configurable option to disable the first run page in Firefox

comment:17 Changed on 10/30/2014 at 01:09:58 PM by simona

  • Keywords growth added

comment:18 Changed on 11/21/2014 at 11:56:59 AM by simona

  • Cc simona added

comment:19 Changed on 11/21/2014 at 04:18:20 PM by simona

  • Keywords large-scale-deployments added

comment:20 Changed on 03/19/2015 at 05:55:36 PM by fhd

I'll add a pref for this.

comment:21 Changed on 03/19/2015 at 05:55:48 PM by fhd

  • Owner set to fhd

comment:22 Changed on 03/19/2015 at 06:09:03 PM by fhd

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:23 Changed on 03/19/2015 at 09:39:44 PM by fhd

  • Blocked By 1489 removed
  • Milestone set to Adblock-Plus-for-Firefox-next
  • Resolution set to fixed
  • Status changed from reviewing to closed

comment:24 Changed on 03/20/2015 at 02:55:30 PM by sebastian

  • Cc sebastian added

You added just a regular preference, not a pre-configurable one as specified in the issue description. The description is outdated anyway. And eventually what you did might be sufficient. But please update the description to reflect the actual change.

comment:25 Changed on 03/20/2015 at 03:14:37 PM by fhd

  • Description modified (diff)

It is preconfigurable, that's also why I removed #1489 from Blocked by. There's a discussion, in #1489 among other places, about a mechanism for preconfiguring preferences while still allowing the user to change prefs, but that's a separate thing IMO.

But you're right, the description said it should be a pre-configurable option as implemented by #1489, which is not what happened. Changed it.

comment:26 Changed on 04/18/2015 at 09:05:38 PM by fhd

  • Blocking 2347 added

comment:27 Changed on 05/07/2015 at 11:55:29 AM by fhd

Last edited on 05/07/2015 at 11:56:19 AM by fhd

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from fhd.
Note: See TracTickets for help on using tickets.