Last modified: 2014-06-23 06:39:40 UTC
Created attachment 15483 [details] Example on en.wiki 1) [[Special:Random]] as logged in user (e.g. incognito mode) 2) Save any edit I. Observed: a signup invite popup appears that covers tabs and search box permanently (unless manually closed). II. Expected: I can continue using the wiki as I wish, without obstacles to editing/other actions or to search.
I think you mean logged out user, right? This is one of the possibilities in a 3-option experiment currently being run (this is the 'post-edit' version, there is also 'pre-edit', which suggests signing up before edit, and 'control', which does nothing new). The experiment will end today, and we'll look at the results and look at how to move forward. Any long-term version will take into account the feedback we get. Note, it should go away automatically when you go to a different page. If not, let us know.
(In reply to Nemo from comment #0) > Created attachment 15483 [details] > Example on en.wiki > > 1) [[Special:Random]] as logged in user (e.g. incognito mode) > 2) Save any edit > > I. Observed: a signup invite popup appears that covers tabs and search box > permanently (unless manually closed). > II. Expected: I can continue using the wiki as I wish, without obstacles to > editing/other actions or to search. The feature will be disabled today as the A/B test is ending. After analysis, it will be proven to work or not in attracting more signups without causing a significant negative impact on IP editing. At that point, one of the following will happen: 1. We will know this helps encourage valuable editors to register without causing too much annoyance to committed IP editors. In this case the feature may be re-enabled. If this is the case, we'll know that this is worth the minor annoyance required to dismiss the guider. 2. We will know it *does* cause excessive annoyance and/or does not attract additional registrations. In that case we will discard this code. In either case, there is no need to redesign the thing.
If that treatment does turn out to be successful, it is possible (we have done incremental improvements to successful features in the past), but not definite that we will tweak it further.
