Talk:Beta Features/Archive

Please share your feedback about Beta Features.

What do you like about Beta Features?
The Media Viewer is a good idea for viewing pictures at a larger size without having to jump away from a page with their file description content. It loads rather slowly, which could be improved, but it is nice I can enlarge thumbnails wihtout having to go to another page to see the bigger picture. Arcane21 (talk) 06:34, 5 November 2013 (UTC)Arcane21


 * Thanks for your thoughtful comments, Arcane21. I'm glad you generally like the Media Viewer concept, and your feedback is much appreciated :) We are already working to improve the image loading speed, but your input is helping us give this task a higher priority. We are now fixing the most urgent bugs, and will be rolling out more tweaks and new features in coming weeks, with our next release due on 21 November, and more updates in December. If you have any more suggestions or questions, you are welcome to post them here, and/or on this Media Viewer discussion page. I am out of office until 19 November, but you can contact our community liaison Keegan (WMF) or lead developer Mark Homquist with any urgent requests. Thanks again for helping us improve this tool! Fabrice Florin (WMF) (talk) 03:09, 12 November 2013 (UTC)

How to channel feedback?
I think that the intention is to gather as much quality feedback for the particular features as possible. Therefore we should promote links to feature descriptions, talk pages but I think we should also point to BugZilla components where some issues can be quickly filed; also a link to BugZilla existing issues isn't a bad idea either.

But below introductory text we have links that says:

About Beta Features | Leave feedback

I think we should get rid of them or at most embed them into the introductory text (for those who want more about WMF initiative). I believe we should be promoting particular features, not a particular WMF programme, which is irrelevant to 95% of users. We probably don't want feedback accumulating on Talk:About Beta Features.

Also when I read on About Beta Features "Can you help us test Beta Features in coming days?" I have some trouble guessing is it about some features du jour we are testing right now (Formulae, etc.) or is it about Extension:BetaFeatures as a little supporting tool?

For example right now I am much more concerned with getting the preferences page and translations right and much less about actual features to be deployed and tested.

« Saper // talk » 00:16, 2 November 2013 (UTC)


 * Thanks, Saper. We wanted to get some immediate feedback about the whole 'Beta features' program, though your point is well taken that over time we could move these general links to a less prominent place, to invite more feedback on the features themselves. Fabrice Florin (WMF) (talk) 03:09, 12 November 2013 (UTC)

Name
Horrible, end-user-unfriendly name. We are scratching our head already how to translate it not to scare anybody with the IT slang. « Saper // talk » 23:30, 30 October 2013 (UTC)


 * What would be better name? Experimental features? I don't think that it's a unfriendly name, but translating maybe can be hard for some languages (e.g. if they don't have suitable word for beta). --Stryn (talk) 10:42, 1 November 2013 (UTC)
 * We have Gadgets, so may be Experiments ? « Saper // talk »  13:20, 1 November 2013 (UTC)
 * Experiments was the original name, it was changed due to possible confusion with "Labs" which is a separate project.—
 * Jaredzimmerman (WMF) (talk) 22:58, 1 November 2013 (UTC)
 * Didn't know that, honest! Still much better name than the current one. I dislike the word "beta" going mainstream (I think it was Google's fault:). I had also some other ideas, like testing ground (or similar) that that should be easy to convey to other languages/cultures (Poligon in Polish for example). Are we soon going to run out of words to describe tinkering? I hope, not! « Saper // talk »  23:09, 1 November 2013 (UTC)
 * I am sure "Experimental features" would not cause confusion with Labs (although "experiments" would), and I think translating that is easier than translating "Beta Features" (unless we consider "beta" to be a word in all languages, but that's just not true). "Experimental" describes the features better than "Beta", since that they are in beta is only relevant to developers (and may in fact not even apply to all of these features) while that they are experimental is what is relevant to users. -- Rastus Vernon (talk) 21:47, 2 November 2013 (UTC)
 * I'm sure the same applies to German. German users will not confuse "Experimental" and "Labs". I think "Beta" could be confusing because we already had "Beta" stuff in the past years that's not included here. For example [ the wikieditor toolbar stuff] is still called "wpusebetatoolbar" in the source. --TMg 12:27, 6 November 2013 (UTC)


 * User:Matma Rex filed 56537 for this. « Saper // talk »  13:05, 4 November 2013 (UTC)


 * Dear Saper, Stryn, Rastus Vernon and TMg: Thank you all for your good insights about the name of this program. We understand that 'Beta Features' is harder to translate than we had anticipated, and we appreciate all the good work of our volunteer translators in finding solutions to address this issue. As Jaredzimmerman (WMF) pointed out, we already considered 'Experiments' and 'Labs' as alternate names, but this would have created more confusion, due to the fact that we have other programs in place that already use these names. At this stage, it would be difficult for us to change the name in the middle of our worldwide release, since so many people have translated it already -- and we don't have enough resources to do a complete rebranding and overhaul in coming weeks. But we would be open to revisiting this next year, if it is a serious issue for a lot of users. Note that whatever name we use has to be short, so it doesn't take too much space in our user interface. Thanks for your understanding :) Fabrice Florin (WMF) (talk) 03:09, 12 November 2013 (UTC)
 * Speaking of the user interface. I really hope the "Beta" link at the top is only a test here at the MediaWiki wiki and will not be included in the Wikipedia wikis. This stuff belongs to the "Preferences", next to the "Gadgets" tab, nowhere else. Two different links at the same place that link to the same preferences are superfluous, confusing and will be threaded as disturbing by the users. Disable this please, when you deploy this. Thanks. --TMg 09:52, 12 November 2013 (UTC)

HTML
This is ugly (taken from my experimental deployment):

w3m for example does not really get it. […] There is lots of classes and metadata but simple spaces between "information" and "discussion" are missing, not sure why we have  twice; lots of paragraphs which we don't want. « Saper // talk » 23:29, 1 November 2013 (UTC)

Checkboxes
…were originally imagined to be on a white background (beta features wasn't in prefs at that point) so it wasn't explicitly called out that they should actually have a white fill in all states, without the white fill they don't really look like controls (hover state would probably help too)— Jaredzimmerman (WMF) (talk) 23:02, 1 November 2013 (UTC)
 * I did not like them as they are inconsitent with the rest of the interface. « Saper // talk »  23:29, 1 November 2013 (UTC)

In Opera 12 the checkboxes do not respond. I have to click them ten or twenty times to mark them. What's this? I don't see an error in the console. --TMg 00:33, 6 November 2013 (UTC)
 * It's a bug in Opera! It doesn't like it when you change the state of a hidden checkbox. I encountered it myself and I have already submitted a workaround to this that was merged, but it's not yet deployed. (Mark promised me it will be before the wider deployment on Thursday.) Matma Rex (talk) 09:31, 6 November 2013 (UTC)
 * Cool. Thanks! You know, I love my Opera 12 so much. --TMg 11:20, 6 November 2013 (UTC)

Thumbnails
I wanted to test the "VisualEditor formulae editing" feature but couldn't tell from preferences page what it does. I think this can be fixed by changing the description (remove the "remember" stuff and describe what it does instead) and the image ([//bits.wikimedia.org/static-1.23wmf2/extensions/VisualEditor/betafeatures-icon-VisualEditor-formulae.svg this one]). I suggest to make the image more realistic. The Σ bigger and darker and a popup like the one that opens when using the Σ in the editor. --TMg 12:18, 6 November 2013 (UTC)


 * Thanks, TMg, you make a good point that better descriptions and more realistic thumbnails would make it easier for people to understand what each feature does. I am passing on your recommendation to our design and development teams. Much appreciated. Fabrice Florin (WMF) (talk) 03:09, 12 November 2013 (UTC)

Mechanism to mark a feature as depending on another
Beta Features might need to have a mechanism to describe a feature as depending on another. The VisualEditor Formula feature, for example, depends on the VisualEditor feature being enabled on wikis where it is opt-in. One solution is to prevent the user from enabling a feature before all the features it depends on are enabled, and another is to automatically enable the features required, with or without notifying the user that the other features have been enabled. Yet another is to put the features that depend on a feature under the feature they depend on and to indent them to show this. -- Rastus Vernon (talk) 21:57, 2 November 2013 (UTC)
 * Hey Rastus, on Test wiki I do see a red warning in my Preferences, "This feature requires the following feature to be enabled: VisualEditor". Do you think this is not enough? Thanks, --Elitre (WMF) (talk) 13:45, 4 November 2013 (UTC)
 * Aaand... it's gone (I can't see it anymore today). --Elitre (WMF) (talk) 13:25, 5 November 2013 (UTC)

Enable all features
I was confused by the first tickbox, "Automatically enable all new beta features". I didn't read that properly and simply assumed that, being at the top, it allowed one-click activation of all the available features. Provide another option for this? Thanks. --Elitre (WMF) (talk) 13:54, 4 November 2013 (UTC)
 * I wasn't confused by this, but may be it should be called "subscribe to ... " or something like this? In a translation I am working on I say "I would like to participate in new experiments; enable new features as soon as they get installed." (rough translation). « Saper // talk »  14:01, 4 November 2013 (UTC)
 * I was confused about this as well, I think it should be clarified TheDJ (talk) 09:38, 5 November 2013 (UTC)
 * Same here. I don't think it should be clarified though -- it should just be what people intuit it to be. That is, enable all beta features, and automatically enable all future beta features. equazcion � 08:58, 8 Nov 2013 (UTC)
 * +1 to Equazcion's suggested solution. –Quiddity (talk) 21:49, 9 November 2013 (UTC)
 * +1. I was confused too. Helder 14:12, 8 November 2013 (UTC)


 * Dear Elitre, TheDJ, Equazcion, Quiddity, Helder and Saper: Thanks for pointing out this confusing feature and suggesting possible solutions! I also find this feature confusing, as I would expect it to enable all the current features right away, not just future ones -- for the reasons you mention above. My recommendation to the development team is to change both the functionality and the wording to say something like 'Automatically enable all current and new beta features'. This would match user expectations more closely than the current solution. It's a pleasure to be working with you all to improve this tool together :) Fabrice Florin (WMF) (talk) 03:09, 12 November 2013 (UTC)

A few questions

 * 1) Will the Beta word get highlighted, or will a number appear nearby, to let users know when there are new features they might want to test?
 * 2) Can the interface in each project please specify that other projects might have more features to test, and which ones, if not all the projects are getting all the features? Thanks! --Elitre (WMF) (talk) 15:05, 11 November 2013 (UTC)

What new Beta Features would you like to see?
I would like to see functionality to add columns and rows to tables. Timboliu (talk) 08:17, 8 November 2013 (UTC)
 * Hey Timboliu, are you perhaps suggesting that this feature is made available in VisualEditor? In this case, this is a common request - and you can follow updates via this tracking bug. --Elitre (WMF) (talk) 10:46, 8 November 2013 (UTC)

At de:Wikipedia:Umfragen/Technische Wünsche the German community is currently preparing a giant list of "Beta features" they "would like to see". A few currently top voted features are: --TMg 10:40, 12 November 2013 (UTC)
 * Cross-wiki watchlist.
 * Search in the category tree, in old versions, in logfiles and histories, search for colors in images and much more.
 * Preview of  while editing sections (5984).
 * Real possibility to move files to Commons.
 * Less JavaScript bulk users don't really need.

Link in personal tools
Do we really need that ? It's getting a bit busy up there and hitting the right link after initial page load can be like a game of whack a mole, with many of them being loaded after the initial DOM. TheDJ (talk) 07:10, 12 November 2013 (UTC)
 * Isn't the "Beta" link at the top only a test here at the MediaWiki wiki? It doesn't make sense to have two identical links to the preferences. I really hope this is a misunderstanding and such a developers feature will not be deployed to all Wikimedia wikis. --TMg 10:14, 12 November 2013 (UTC)