Extension talk:Media Viewer/About/Archive02

What do you like about Media Viewer?

edit

Clarity

edit
  • I like that I can see all the most relevant information about the image in one page only and the graphic display. --Daniele Pugliesi (talk) 06:29, 9 November 2013 (UTC)Reply
  • I like that it is possible to watch more details present on a picture, exactly text explaining what a part or a component of some graph means, so eliminates some confusion of not being sure what is on that picture. Cornel24 (talk) 17:53, 10 November 2013 (UTC)Reply
  • Hello, it's a very good idea : now we can have a look on the picture without having to go to Commons and then click again to see it in a larger size. It is quite clear, also : we easily and quickly see the picture and the information, and all the links we need are there. Thank you for this new feature ! Best regards, --Daehan (talk) 10:06, 22 November 2013 (UTC)Reply
  • Very good all round. Being able to just click on images to see data without having to leave the page or open another tab on my browser is very useful. It's also far smoother than most similar functions on other sites. A big thumbs-up from me. --ProtoDrake (talk) 11:52, 25 November 2013 (UTC)Reply
  • It's very good that such an application is being updated by the Wikimedia team. It really helps to save time and in the mean time shows a clarified image. --Shalini Ghose (talk) 2:43, 3rd December 2013

Context

edit

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 without having to go to another page to see the bigger picture. Arcane21 (talk) 06:34, 5 November 2013 (UTC)Arcane21Reply

More intuitive

edit
  • I think that this is a more intuitive experience for the casual reader than the current behaviour of clicking on a link which takes you to a page about the image.--NHSavage (talk) 22:40, 18 December 2013 (UTC)Reply
  • I find this to be a much more efficient way of viewing content than leaving the main article or taking up space in my generally overcrowded tab bar. Why didn't anyone think of this earlier? --Yea55 (talk) 18:46, 19 December 2013 (UTC)Reply

What would you change in Media Viewer?

edit

By wording

edit
edit

Talk page

edit
  • TALK PAGE! - Wikipedia is all about read-write capability and when I have this option enabled it makes it LESS write and MORE read. A button that links to the existing talk page ANYWHERE would be nice, otherwise I think this is a great tool. Victorgrigas (talk) 04:00, 25 November 2013 (UTC)Reply

No good as default (we redirect to Commons directly, in french Wiktionary)

edit


Closing the window

edit
I agree with this, at first I was not sure how to close the window with the image in. I resorted to using the escape key, which worked, but I think that to roll it out for general use, you probably need the way to close the window to be very clear.--NHSavage (talk) 22:49, 18 December 2013 (UTC)Reply
...and if you use a touchscreen and no keyboard, you're trapped... I'm using a tablet, and had to go to this current page and conversation to understand there is a cross appearing on mouse hoover. Generally, events triggered by mouse hovering with no alternative (such as menus who can't be clicked) should be avoided, due to the generalization of touch screen devices. Epok13 (talk) 22:55, 28 December 2013 (UTC)Reply

Licensing and attribution

edit

I have several problems with the media viewer:

  1. The "Use this file on another website" has a relative link to the image description page - "/wiki/File:Donna Shalala - Knight Foundation.jpg". That link is not going to work if you are using the image on another website.
  2. Many images are not suitable for reuse on every conceivable website. For example, fair use images should definitely not have anything encouraging people to reuse them. And even some of our licensed images - if it's not public domain and not creative commons, then we shouldn't encourage someone to use it without reading the detailed licensing information. If you just embed a GFDL image, for instance, you are probably not in compliance with the terms of the license.
  3. It's not obvious which thing on the popup is the author. Unless you already know who the author of a particular image is, you're going to think that the uploader is the author and would incorrectly attribute that person.
  4. We've been telling photo contributors that if someone clicks on an image, it will take them to the description page, which will show their license, attribution information, etc. Now, that's not necessarily true any more.
  5. It doesn't actually do anything useful for the reader - they are already one click away from viewing an enlarged version of the image ... you've just made the click do something different.

--B (talk) 13:51, 22 November 2013 (UTC)Reply

This is absolutely vital. Any software hosted by Wikimedia should meet not only the legal requirements of attribution, but should provide an example that respects the spirit of the licenses by providing meaningful and easy to find attribution. The summary page does not name the author or link to their user page. The software shouldn't go out of beta until this is added. -Pete F (talk) 23:31, 30 November 2013 (UTC)Reply
+1, and then some! The new viewer is very attractive, but unfortunately it optimizes the graphic display by making the attribution information less visible. We need to compensate for this by adding an image credit section along with the references on the article page. Can adding an image credit section to articles be automated somehow as a part of this project?
We need to be proactive about making image attribution visible because it is so important to image donors! The software should not go out of beta without consulting with our donor partners on this question. Djembayz (talk) 06:50, 1 December 2013 (UTC)Reply

I love this but it's not for me

edit
 
An image for testing the version installed on MediaWiki.org.

This is a tremendous gadget, and I honestly can see it being deployed as the default with very few changes from how it is now. I would ask, however, that if this does become the default, there is a way to turn it off. As someone that works with files, when I click on an image, I want to go directly to the local file description page (i.e. as it functions now), because the work that I'm doing with files happens on that page (and because my internet is so bad right now that the extra loading time for the large versions of images will be problematic.) So yeah, I think that for 99% of the people that use Wikipedia, this is a great thing. But for the 1% of people that spend a lot of time in the File namespace, doing the behind the scenes stuff, please make sure that there's a way to skip the lightbox. Sven Manguard (talk) 03:34, 23 November 2013 (UTC)Reply

Why not add a modifier key to the click, that would bypass lightbox and take you straight to the description page. Easy to do, simple to learn for advanced users, doesn't bother the rest of the users. TheDJ (talk) 18:03, 26 November 2013 (UTC)Reply
Adding an off switch also doesn't bother the rest of the users. I don't like modifier keys, because I prefer to do as much as possible with the mouse. It's also very tedious for someone that, on some days, will view 200, 300 images in rapid succession, to have to constantly use a modifier key. Sven Manguard (talk) 19:57, 26 November 2013 (UTC)Reply
I also would like a possibility to turn off this option. I more often want to see full description page than to see bigger image. BartekChom (talk) 00:36, 10 January 2014 (UTC)Reply
  • Thanks Sven, others, for thoughts on this. As we look toward a global release out of Beta Features, we'd absolutely love to get more community feedback about if/how to provide an option to disable and/or go right to the file. Tell a friend to let us know :) Keegan (WMF) (talk) 06:23, 27 February 2014 (UTC)Reply
    • Keegan (WMF) - If I have to right click and open in a new tab, I have to right click and open in a new tab. In all honesty, the ability to disable this is purely a convenience. The interruption to my workflow is, in most situations, quite minimal. I'd like to be able to bypass it, but it's not serious. That being said, I would definitely reach out to the Commons community before any deployment there, as the people on that project have very different workflows and very different needs when it comes to working with files. Galleries on Wikipedia are mainly there for visual effect. Galleries on Commons are there either 1) so that someone can find the image that they want, then click on it to pull up the full file name, and cut/paste that into a page on another project, or 2) large collections of images that are gathered together in a non-public facing page for either a tracking or an administrate/maintenance purpose. Any change to how files are pulled up will impact the workflow on Commons much more than it will on other projects. Sven Manguard (talk) 00:59, 1 March 2014 (UTC)Reply

Would be nice to have a bypass option or a link underneath the image to the image description page. It's especially bothersome when viewing pages like this where a lot of thumbnails are located and you want to select a photo to be included in an article on Wikipedia. I mostly use galleries to select good photos, as good shot have been pre-seelcted and I don't need to browse through a category of say 2,000 images. But anytime I click on an image, I get the viewer, and it drives me nuts. The viewer is perfect for end users and people who want to download and reuse images elsewhere but it is a nuisance to WIKIPEDIANS who work with images to improve the encyclopedia articles. Please try to develop the gadget in a way that it would be beneficial to both end users AND editors of Wikipedias. Thanks for the hard work. Teemeah (talk) 13:49, 3 March 2014 (UTC)Reply

Problem with location maps

edit

One thing I have just noticed is that location maps where a background image has dot added on to it to indicate locations does not work well with this feature as it only shows the background map. See for example en:List of monastic houses in Devon. This is probably tricky to fix as you have the same problem at the moment - clicking on the image only shows the background map as that is the actual image.--NHSavage (talk) 16:10, 2 January 2014 (UTC)Reply

Regression with where clicking an image goes...

edit

With a note that people may react negatively to change, including one of positive nature, please understand that clicking an image took me to the image page, before, with author and licensing information. Now, the behaviour suddenly changed... --Gryllida 02:58, 30 January 2014 (UTC)Reply

Thank you, Gryllida. It will be a big change, and it will surprise people. Particularly the hundreds of thousands to millions of users/editors/contributors that don't subscribe to mailing lists, check local Village Pumps (or equivalent), or participate in any of the social engagement side of Wikimedia projects. We will develop a Media Viewer that will look different, but should not feel different as far as the file information that the Viewer displays. It's important to have the core functionality and your feedback below has been wonderful. I'll be working as a Community Liaison part time on this project to help ingest feedback like yours over the coming months as Media Viewer is deployed. My apologies for us not having much Wikimedia Foundation presence here over the past couple months as we were early on in Beta Features. This is a high priority product and as we enter the second half of the current development cycle Fabrice and I will be here :) Keegan (WMF) (talk) 07:17, 27 February 2014 (UTC)Reply
Thanks Gryllida 11:52, 28 February 2014 (UTC)Reply


What do you think of these new features?

edit

We'd be grateful for your feedback on some of the new or updated features we are working on for our upcoming release of version v0.2. Please add your feedback in the third 'Feature comments' section below, as we would like keep the first two sections above as simple listings we can update regularly, rather than use them as discussion areas.

Ready for testing

edit

You can test recent features of Media Viewer v0.2 on this MediaWiki.org this test page, as outlined in these testing tips. (If you feel adventurous, you can also check the latest features on this slower beta site).

Coming soon

edit

We invite you to check those specifications before requesting features that may already be included in those tickets.

Feature comments

edit

Please add your comments about the above features in this section (we would like keep the first two sections above as simple listings we can update regularly, rather than use them as discussion areas).




What new Media Viewer features would you like to see?

edit

Text Message/GpS Tag

edit

Zoom

edit

Hi guys, Based on your requests below, we’ve started design work for the upcoming Zoom feature in Media Viewer.

Here’s a first prototype for your review.

A more detailed [https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/167 specification is outlined here.

What you think? These first designs were prepared by Pau Giner and and Kaity Hammerstein and they’d love to hear your feedback.

Once we hear from you, we’ll start development in a few weeks, and hope this feature can make a lot of users happy! Fabrice Florin (WMF) (talk) 17:07, 28 February 2014 (UTC)Reply


Thanks, guys. Based on your feedback, we are starting work on this Zoom feature, which we hope to include in v0.2, if time allows. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply
FocalPoint, Daniele Pugliesi, Saehrimnir, Stu Phillips, Peteforsyth: I filed this bug a while back. You can follow the mingle card or the bug for updates. It'll be out soon :) Keegan (WMF) (talk) 07:37, 27 February 2014 (UTC)Reply

Pre-loading

edit
  • Pre-loading the next image(s) would facilitate the navigation. Currenttly, loading the next image is only done when the next arrow is pressed. Pre-loading is invisible to the user and greately increase the loading perception time. --Pannini (talk) 13:43, 22 January 2014 (UTC)Reply
Thanks for this suggestion. We are now working on this feature to preload the next and previous images. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply

Slideshows

edit
  • It could be nice a function to see a slideshow of the images in the same Commons category or in the same Wikipedia page, showing the next image after few seconds. It could be great a tool to create a personalized list of pictures, then see the slideshow and to save it as a .ppt file, so it can be used to create easily and quickly some presentation to use offline (for example by the teacher in a school during a lesson). --Daniele Pugliesi (talk) 06:45, 9 November 2013 (UTC)Reply
Thanks for this recommendation. We have included View files in slideshow mode for the next version v0.3, tentatively scheduled for next quarter. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply
    • -1. Too confusing. It's simple: nobody requested or needs this at Wikipedia or sister projects, and it's getting in the way.
  • When I'm viewing a file at Wikipedia or another sister project, have no arrows.
  • When I click a file from a Commons gallery, it's ok to have arrows or do a slideshow.
Gryllida 00:29, 9 March 2014 (UTC)Reply

Annotations

edit
You probably mean annotations? If so, we have a bug open for that: 56666 --MarkTraceur (talk) 01:19, 22 November 2013 (UTC)Reply

Other features

edit

What bugs or issues have you found with Media Viewer?

edit

Some more feedback

edit
  1. It takes much longer (10 seconds or more) than normally to load/view an image. Normally i open files in a new tab which is quicker.
  2. The date given is wrong. For example "Erstellt am -2147483629. Dezember 1969" (=photo taken december 1969) when you view the photo commons:File:Hattingen - Rathausplatz - Rathaus 03 ies.jpg on commons:Ennepe-Ruhr-Kreis. I don't know from where the media viewer could have taken this information. The photo was made in 2010 see its information template and the exif informations. Holger1959 (talk) 21:32, 7 November 2013 (UTC)Reply
    This date shown (in December 1969) is in fact 2010 seconds before 1 January 1970 00:00 UTC, which seens to be used like the base date for Unix timestamps (or the time() and localtime() API's and similar in standard C language libraries).
    "2010" alone is not interpreted as a year, but as an Unix timestamp (Unix timestamps are not used in image description page for the date field, dates containing only digits, possibly without any separators as in this case where there's only a year) should be interpreted using ISO parsing rules). Additionally the display format used to render it should not add any unspecified precision (here we just have a year, but NO month, NO day of month, NO day of week, and NOo time of day in hours, minutes, seconds). Parsing should be done like date properties in Wikidata.
    Verdy p (talk) 20:10, 5 January 2014 (UTC)Reply

Jiggle when resizing the window

edit

Resizing the window (e.g. by going to fullscreen mode) makes the UI jiggle around a bit (Firefox). Skalman (talk) 07:21, 22 November 2013 (UTC)Reply

Hangs my Internet Explorer Browser

edit

I've given up on the Media Viewer, every time I tried to use it, it hangs my browser. Using Windows Explorer 9. Wee Curry Monster (talk) 10:30, 1 February 2014 (UTC)Reply

Scrolling broken in Monobook

edit
 

In Monobook, the information scrolls up beyond the bottom of the screen (see screenshot). Monobook, Firefox 26, Windows 7 Jay8g (talk) 20:14, 9 February 2014 (UTC)Reply

edit

Hi, the link on images says "Learn more on Wikipedia", but links to Commons. Thanks, Matty.007 (talk) 20:25, 4 February 2014 (UTC)Reply

Media Viewer bug

edit

Hello, When Media Viewer is activated we can't play a diaporama. I tested it here. 92.89.123.3 12:10, 12 December 2013 (UTC)Reply

Thank you for the feedback, I filed a bug for this enhancement here. Keegan (WMF) (talk) 22:56, 21 December 2013 (UTC)Reply


Image resolution, downloads, and license

edit

The media viewer currently does not indicate to the viewer that other (specifically higher) resolutions may exist, or how to download them. Since reuse is an important value of the Wikimedia movement, some useful information about downloads should be available on the main screen. As it currently stands, clicking on "use this file" also does not indicate that there are higher resolutions available; one has to know to click "Learn more on Wikimedia Commons" in order to find them.

To somebody not familiar, "Learn more on Wikimedia Commons" is not a very appealing link -- this is the kind of language that many sites use to link to a very generic "about us" or "about this site" page, not specific information tailored to a specific image (as is the case here). I am concerned that an Internet savvy (but not Wikimedia savvy) audience will completely overlook this highly useful link.

The "CC BY-SA" (or other) license abbreviation looks like a Martian language to most readers. It should be introduced with text like "You are free to reuse this image in accordance with this license" (which should automatically detect when the file is Public Domain, and say something more like "You are free to reuse this image, to which nobody has ownership rights.") Also, this text should probably be next to the "Use this file" link -- the license is currently in a different part of the UI.

Some parts of this, but not all, are addressed in v2, available on mediawiki.org. -Pete F (talk) 23:41, 4 January 2014 (UTC)Reply

Personality rights are currently not addressed in the UI. The WMF board and many community members have expressed that it's important for files to indicate clearly, where needed, that the subject has consented to its broad publication. This tool should reflect that desire.

Longtime readers of Commons and other MediaWiki-based sites may be very used to the idea that clicking the image itself brings you all the information available about the file. In this case, once one is in the Media Viewer, clicking on the photo itself does nothing. In order to respect the principle of least astonishment (as an idea, not a policy), this should be altered so that the second click on the photo (i.e., the first click within the Media Viewer) takes one to the expected place, i.e. the full Commons description page.

The following issue is addressed in v2, visible on Mediawiki.org. -Pete F (talk) 23:41, 4 January 2014 (UTC) Finally, a small detail: the "X" used to close the box is in a slightly different place than on sites like Flickr and Facebook. Conforming to evolving design consensus seems like a good idea. On those sites, the "X" is in the upper right corner of the window, not the upper right corner of the image. (Nice to see that the escape key works as expected, though.) -Pete F (talk) 18:13, 26 December 2013 (UTC)Reply

addendum This last one might not seem significant depending on what file you're looking at -- I suggest a narrow, portrait-oriented photo like File:Washington County Fair drop ride 3 - Hillsboro, Oregon.JPG. (The dark background also contributes to the difficulty finding the X.) -Pete F (talk) 18:54, 26 December 2013 (UTC)Reply
Hi Pete F, we are now developing a brand new version of 'Use this file', which will address many of the issues you raise above. The key specifications for this improved feature are included in these three Mingle tickets:
We appreciate all your detailed suggestions above, and are taking them into consideration. This doesn't mean, however, that we will implement them all. I would be happy to discuss them with you in greater detail in our upcoming IRC 'office hours' chat on Fri. Feb. 21 at 10am PT -- or set up a separate call to go over this, since you have so many ideas that would take too long to respond to individually in this discussion. Cheers. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply

Attribution in a little more depth

edit

It seems like some improvement has been made around attribution since this discussion was started (but it's hard to tell what has changed, I haven't seen any response on this from the dev team?)

As it currently stands, the name of the "author" appears below the file name. This is a good place for it, but in many cases it is not apparent that this is attribution to the author/photographer etc. Many of these will be Wikimedia usernames, which at first glance might not appear to represent a person. We also have readers and authors from many different cultures, so a name is not always recognizable as such.

I'm not sure what the best way to resolve this is, because in some cases "photographer" might be the best title, in others "producer," etc. But it seems to me we have used "Author" pretty consistently on Commons, and it works OK. So I think unless somebody has a better idea, the name should be preceded by "Author: "

-Pete F (talk) 19:20, 31 December 2013 (UTC)Reply

Thanks, Pete F. Our current plan is to add a 'By' label in front of the author name, which should clarify that this person is responsible for creating that image, without taking up any more space than needed. This is also consistent with the attribution practices of Creative Commons, and therefore with other parts of our user experience. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply

Transparency

edit
 

The lightbox doesn't really work that well with transparent images. Might I suggest:

.mlb-image img { /* or using :hover */
 background: url("//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png") repeat;
}

or

.mlb-image img {
 background-color: white;
}

or

.mlb-image img {
	background-color: white;
}
.mlb-image img:hover {
	background: url("//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png") repeat;
}

Android 4.0.3 and the stock browser

edit

It does not work for me. I use Android 4.0.3 on Asus Eee Transformer tablet (TF101) with the sock browser. The only thing I get is a black and white screen with 2 links - to the about and bugs pages. There's something like the close button (unusable) as well. Kpjas (talk) 10:48, 23 February 2014 (UTC)Reply


Click 'full screen' icon reduces image size

edit

The image is then downsized to a small thumbnail and stays that way even after clicking same icon again to leave full screen mode. I use Windows 7, Chrome 33.0.1750.117, screen resolution 2560x1600 Erik Zachte (talk) 09:38, 28 February 2014 (UTC)Reply

+1 (Mac OS 10.9, Chrome Version 33.0.1750.117, Retina Display --Sebaso (talk) 10:50, 1 March 2014 (UTC)Reply
I put this into Bugzilla. That's not expected behavior :) Keegan (WMF) (talk) 21:57, 3 March 2014 (UTC)Reply

"more info" drawer

edit

The drawer concept is really nice. But it could be better used: The "more info" drawer should work on mouseover, not on click. "tags" aka categories should be visible without any further action. The link to the commons image should be under title, the link under CCBYSA should link to some kind of "yes, you can use this"-explanation, not to the commons page. --Sebaso (talk) 10:57, 1 March 2014 (UTC)Reply

Great feedback. Sebaso. To clarify your last point: As I see it the CC-BY link goes to the .png commons file. You're suggesting it should go to a page like reuse, correct? That would be a good thing to incorporate in some way to the licensing. Keegan (WMF) (talk) 07:41, 4 March 2014 (UTC)Reply
yes. but it should be a new page with a claar "invitation to reuse". --Sebaso (talk) 08:28, 16 March 2014 (UTC)Reply

Breaks back button

edit

I like a lot of things about this new viewer. The appearance is better, the ability to click to the next or previous image is great, the quick access to the meta data works well. I'm having a problem though with my back button. After viewing some pictures, the back button in my browser will take me back through the pictures then to the original page, but won't take me back to where I was before I got to that page. Right clicking on the back button and picking from the list still works. I'm using Firefox 27.0.1 on a Windows 8.1 machine. SchreiberBike (talk) 17:20, 2 March 2014 (UTC)Reply

Thanks for the report. I filed a bug to see if we can fix that :) Keegan (WMF) (talk) 21:52, 3 March 2014 (UTC)Reply


Team Updates

edit

Thanks for your great feedback!

edit

Thank you all for your wonderful feedback, everyone! Especially Daniele Pugliesi, Cornel24, MarkJurgens, Ainali, Elitre, Micru, Ragesoss, Jarekt, Holger1959, Barcex, Raymond and Julian Herzog, to name but a few. Your detailed feedback is absolutely invaluable to us -- and much, much appreciated :) We are passing on to our development team recommendations to address the issues you raised. Some of these issues were already on our to-do list, but your comments are helping us give these tasks 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 your amazing suggestions, and for all that you are doing to help improve this tool as a collaboration between the community and the foundation! Fabrice Florin (WMF) (talk) 03:11, 12 November 2013 (UTC)Reply

Fabrice, can you clarify when you are planning on making the new beta live on Commons and other sites? I think the version there is still "v1"-- it looks very different from the "v2" on this site. Was there ever an update in November / December? Has it been pushed back? -Pete F (talk) 23:33, 4 January 2014 (UTC)Reply
Hi Pete F, we push new versions of Media Viewer every Thursday, so all wikis should now have version v0.2. However, the latest version takes a couple weeks to reach all wikis, because we use the 'platform train' that works roughly like this: we test new features on beta for about a week, then new accepted code merged on a Wednesday gets deployed to MediaWiki.org and test sites on the next Thursday, then to Commons and 'sister projects' the following Monday, then to all wikis the following Thursday. So if you want to see the most recent features, check them out on this beta test site (with slow performance) or this test page on MediaWiki.org (faster, but several days later). Hope this helps. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply

Update on Version v0.2

edit

Thank you all for your thoughtful comments about the Media Viewer v0.1! Your suggestions are really helpful to our multimedia team, and we have been acting on many of them already in the new version v0.2 which we are now developing.

Some of your key recommendations have been outlined in this feedback section of our main product page, then turned into concrete action items for version v0.2 and v0.3 on our Mingle project management system.

For example, requests for a larger image size (by MarkJurgens, Daniele Pugliesi, Frank Schulenburg) and a darker background (Ragesoss, Another Believer, equazcion, Daniele Pugliesi, Cornel24, Kelvinsong) have already been addressed in the current version. Concerns about slow image load (by (Mono, Arcane21, Ragesoss, Another Believer, Daniele Pugliesi, Cornel24, Holger1959) have been the focus of a couple development sprints devoted to improving performance in a variety of ways (see #154, #155, #126 or #146, to name but a few possible solutions). We're also taking to heart the many recommendations that we improve the 'Use this file' panel to attribute files correctly, with a quick summary of author, source and license (Amada44, Elitre, Church of emacs, Rsocol): these are being addressed in this new 'Use this file' panel which includes attribution-friendly Embed, Download and other functions. Requests for a Zoom feature are now being designed on this card. Other requests for a pop-up explaining the license terms are now under development (see cards #118 and #197); and we're preparing a whole new batch of features to support slideshows and other file formats, as described in this updated 'Next Version' section of our overview page for Media Viewer.

These are just some examples of how your insights are being incorporated in our release plans. We're also reviewing your longer-term recommendations, which will take more time to implement, but are under consideration nonetheless. Our focus this quarter is on completing the current version v0.2 and starting work on the next version v0.3 of the Media Viewer, to provide a better viewing experience for all users.

Sorry if we haven't been more responsive on this page in recent weeks: we have all been busy improving the product, based on your earlier feedback. In a few days, we will invite your comments on an updated beta version v0.2, which we are about to release shortly. As that date approaches, we will start archiving many of the comments above which have been addressed, to reduce clutter and to invite us all to focus on the new features and improvements. To keep up with our work and participate in our conversations, we also invite you to subscribe to our multimedia mailing list. And if you're feeling adventurous, you can test the latest features before they are released, on this beta site, but performance will be much slower on that site (you will also need to create an account, then enable Media Viewer in your Beta preferences).

Thanks again to everyone who has already contributed so productively on this page: keep your great insights coming! Keegan, MarkTraceur, other team members and I will do our best to answer your questions (for a faster response, you are welcome to mention our user name in your comments, so we are notified and can get back to you more quickly). But even if don't always respond right away, rest assured that we are reading your comments and considering every suggestion carefully. :) Fabrice Florin (WMF) (talk) 21:35, 9 February 2014 (UTC)Reply

Thanks! A half of my suggestions weren't there. I've added them in. --Gryllida 05:55, 10 February 2014 (UTC)Reply
I'm particularly surprised that 'make preview bigger' and others are on the list, while I didn't expect it to occupy the whole page. Previously the preview shown on image click (without media viewer) was rather small. Having a small preview benefits the reader as he sees that he did not leave the article and didn't enter a weird new full-screen app. Some might think was "was I hacked?" or "where did I come?". --Gryllida 06:04, 10 February 2014 (UTC)Reply
Thanks, Gryllida. We're reviewing your suggestions and will respond to them once we've heard from team members. As a rule of thumb, we tend to implement features which are requested by large number of users, rather than individual requests by a single community member. For example, I understand you are a big proponent of a proposed 'Preview' function, though I'm not hearing this as being a priority feature from other team or community members. I should also point out that this proposal doesn't match best practices on other top multimedia sites we've been studying for this upgrade. So I am not optimistic that this particular feature would be implemented in the near-term, though we will give it careful consideration for future releases. On the other hand, I'm happy to let you know that we plan to implement other features you are advocating, such as making the link to the file repository more prominent, as well as support for multiple page documents. Thanks again for your interest in this project. Fabrice Florin (WMF) (talk) 01:03, 11 February 2014 (UTC)Reply
It'd be interesting to learn that websites have a best practice of ... occupying a whole page with a preview, with black non-transparent background. I'll watch the presentation, expect it to be interesting. :-) Again thanks for the detail. Gryllida 05:45, 11 February 2014 (UTC)Reply

Release Plans

edit

Towards enabling the Media Viewer by default

edit

It appears likely to me that, whenever the time comes, enabling the Media Viewer by default will be rejected by the Wikimedia community, for reasons deriving from our shared vision for all people to freely share in the sum of all knowledge. I think that would be unfortunate, considering all the good work that has gone into it, so I'd like to point out the high-level issues I see. I hope Fabrice and the engineering team will take a step back as well, and consider adjusting feature priorities accordingly. (Maybe this is already part of the plan; but recent communications make it appear that it's getting missed.)

According to the engineering team, the Media Viewer aims for three goals:

  • Provide a richer multimedia experience
  • Display images in larger size
  • Reduce confusion

These are worthy goals, and I'm sure all serious Wikimedians would support them. When the question gets raised, though, of whether to replace the current default view with the MV, less lofty considerations will come into play: does this new feature sufficiently meet the basic requirements already, more or less, met by the current default view? I think the answer is a decisive "no," and am skeptical about whether the apparent plan for refining the Media Viewer will change that.

What requirements am I talking about? I would summarize them as follows:

  1. Are all copyrights and personality rights adequately protected?
    1. Have we met the minimum legal standard?
    2. Have we met the expectations of rights-holders sufficiently that they will feel good about contributing to Wikimedia projects?
  2. Are (potential) reusers shown a clear path forward?
    1. Are they given sufficient guidance in overcoming practical obstacles to reusing materials presented by the Media Viewer?
    2. Are they given sufficient guidance in meeting relevant legal obligations?
    3. Are they given sufficiently convenient access to the right links, including a file download link?
  3. Have we appropriately exposed the strengths of Wikimedia Commons to our users? For instance:
    1. Commons provides strong assurances that all its content is freely reusable, with minimal requirements, unlike Flickr and other repositories. Is that expressed clearly?
    2. Commons is more organized than media repositories like Flickr (eg, category system).
    3. Commons invites anybody to contribute materials that serve its educational mission.

While my list above may or may not be complete, I am pretty sure it more or less reflects what most Wikimedians will have in mind, when considering whether or not the Media Viewer should be enabled by default. Whether the Media Viewer has exciting and worthwhile new features is certainly important, but it is subordinate to meeting the minimum standard of reflecting our shared values, at least as adequately as the current default media view does.

Current efforts to refine the Media Viewer seem (to me) to be missing the significance of these basic considerations. I would expect that, unless the engineering team prioritizes feedback relating to basic adequacy (reflected, more or less, by my numbered list above) more highly than feedback about improving functionality, the Media Viewer will not (and should not) be approved as a default feature by the Wikimedia community. -Pete F (talk) 04:36, 16 February 2014 (UTC)Reply

I'm not a developer of this project, but do know quite a bit about it where it's coming from and I can tell you that at least the first consideration is high on the visibility list of the team. HOWEVER. it is also the most difficult problem to solve and requires a lot of technical work. This work is taking place, but it is not directly visible to most users. This frontend is using a new API to get the information that you are pointing out, and that will be developed specifically to meet these goals. BUT there is still a lot of work to do there and in the way we register licenses and copyrights of files. This project is being used as the driving force to develop this new API. I too would suggest not to enable this for ALL anonymous users until that goal is met, but having it as beta will help garner the feedback that is required to develop the backend systems for license/copyrights/authors.
I have recently met this team and I have great confidence in them. But I too support your statement that the team needs to watch out for the above concerns. Especially the Commons and top 5 wikipedia projects are sticklers for correctness when it comes to legal requirements and EDUCATING users regarding licensing. These aspects need to be extremely well thought out and balanced, so any development would at some point have to be validated against these basic community principals. TheDJ (talk) 11:40, 17 February 2014 (UTC)Reply
Hi Pete F, thanks again for your thoughtful recommendations above, which we are reviewing. We are now hard at work on addressing the first two points you raise above about copyright protection and appropriate tools for re-users. Regarding your third point, Media Viewer already links to Commons in many places, and we will consider making those links even more prominent, while still aiming to reduce confusion for users. We would be happy to discuss your advice in greater detail in our upcoming IRC 'office hours' chat this Fri. Feb. 21 at 10am PT -- and am also open to a separate call to go over this 1:1, if you like. Thanks again, and regards as ever. Fabrice Florin (WMF) (talk) 09:11, 19 February 2014 (UTC)Reply
Thank you both for your thoughts on this. @Fabrice, I appreciate your offer to chat and am happy to if the opportunity presents itself -- but it seems to me at the moment that there's a need for public consideration about the high level goals and impacts of this feature. So for the moment let me add a few thoughts here:
  1. On copyright, I think there is room for improvement beyond the minimum legal requirement, to ease the process of Wikimedia volunteers advocating to content owners for CC licensing. My bigger concern, though, isn't copyright, but personality rights. There has been a great deal of discussion lately about the way we (don't) deal with personality rights, and related software features. For instance, @Sj, a WMF board member, recently suggested adding a feature to the upload wizard to gather information relevant to personality rights. If this Media Viewer were to get presented as a complete feature to the community without any regard to personality rights, I think that repeat a mistake that was made in 2010 when the Upload Wizard was released. Hopefully it's possible to do better this time.
  2. As for reusers, I think a good number of suggestions have been made above, but it's not clear to me that they have been given strong consideration. (Perhaps they have, it's hard to tell for sure what you consider high priority and what you don't.) But to me the most glaring is that when one clicks "use this file" there is no link to even get the file -- that is, no download link. (Also, "use this file on another web site" provides a pretty specific HTML link, which is not what's needed on many modern web sites like Facebook or Wordpress -- a simple link to the file is much easier to use in those cases, but is not made prominent in the beta Media Viewer.)
  3. As to showcasing the strengths of Wikimedia and Commons, this is a much more nuanced issue than simply the number of links. Again, I think good suggestions have been made above; I'm not looking to rehash them all here. But I don't think you're likely to get to the right solution if your main criterion is how many votes each suggestion gets. -Pete F (talk) 17:17, 22 February 2014 (UTC)Reply


Hard to scroll for the more detail (i'm missin a queue)

edit
  • With the newer layout, where you need to scroll below the 'fold' to read the more information, i'm missing a queue that this is an action I should take. My mac doesn't draw scrollbars, unless I'm scrolling, so i'm not being visually informed of the presence of this information, and even if i put scrollbars to render always, it's still not very visible. Suggest downward facing arrows somewhere in the bar above the fold to indicate that there is more content, i need a queue to be made aware of this 'pagination' action that is expected of me. TheDJ (talk) 18:11, 26 November 2013 (UTC)Reply
edit
  • Title of image should link to information page, Copyright title ("CC BY-SA 3.0" for example) should link to information on what that specific license entails. Even better would be if, when clicking the copyright license title, a simple dialog appeared describing what the license permitted. Currently, the license links to the image's dedicated wiki page and the title of the image does nothing. Personally, I think this is confusing for the common user. Image showing what part I'm referring to (imgur link because I didn't want to go through the trouble of uploading to Wikimedia, apologies): http://i.imgur.com/4RTPayo.png --Nicereddy (talk) 02:28, 3 December 2013 (UTC)Reply
+1--Sebaso (talk) 08:29, 16 March 2014 (UTC)Reply

Mention partnership

edit
  • On the Media Viewer, images uploaded by partners (GLAM for example) or during a partnership do not have a visible mention of the partnership. The uploader may not be the partner (upload by a bot) And nobody will click on the "Learn more on Wikimedia Commons" link to see if a partner uploaded it or released it. Trizek (talk) 13:42, 18 December 2013 (UTC)Reply
  • An ok idea. Gryllida 10:05, 7 March 2014 (UTC)Reply

Touch screen image swipe

edit
  • Touch screen image swipe would be a great feature on mobile devices! The < > arrows are small on a phone. (Until Apple makes a bigger screen for me)

Also, the 'x' seems a little too small to touch on a phone. It takes me a few attempts to close the window. MarkJurgens


Caption or title at the bottom?

edit

I would have thought that the title of the image is less useful than the caption that was there before the image was enlarged. Particularly for a scientific article, the cation often annotates features of the image. This would be a genuine improvement over the old system whereby you could either look at the caption or the enlarged image but never both at once. Evolution and evolvability (talk) 11:42, 9 December 2013 (UTC)Reply

Nice first steps, but needs a lot of work

edit

My initial thoughts after using this for a little while:

  • Desperate need for a throbber. When i click on an image i get a black window with a small white area below it, for quite a while. Not even the browser's favicon does its loading-animation!
  • The 100% black could be toned down a bit, made a bit transparent, so you get to see the underlying page (look at the facebook viewer). This gives people the feeling that they are still on the same page, not taken to some other place.
  • Added to that, give the images a bit of breathing space, and if it's only 10px on either side. Right now there is no sense of style to the viewer.
  • The clickable area of next/previous is far too small. Again, look at facebook: pretty much the entire image-area brings you to the next one. Granted, it's not as important here, but at least you could make the entire right/left edges of the screen clickable. Likewise, clicking on the transparent black background closes the viewer. All of this is very convenient.

--Rotane (talk) 00:03, 28 February 2014 (UTC)Reply

Details format

edit

Some comments about the details section of the viewer:

  • I like the overall style: white background, grey boxes, black text, blue links. A small change could be to link the author name only, not the whole like.
  • The grey icons are way too small to be readable. It's like the recent Gmail and Yahoo interfaces, those icons are completely useless. They would be easier to recognize if they were coloured (like the 1990s MS Office) or huge. Both things would ruin the interface. Anyway, each line has a decent description, so there's no confusion at all about what each line means - except with "tags".
  • I don't think that the "used in X pages" section is useful for readers.

-- NaBUru38 (talk) 03:46, 28 February 2014 (UTC)Reply

  • NaBUru38, we appreciate your time to look over Media Viewer. It's good to hear you like the style. How you would suggest to stylize the icons is quite helpful. And as always, the content to contain in the viewer is something we're constantly evaluating with each design to make sure we're displaying what's succinct and important for media use and reuse. With input like this we can work toward community satisfaction. Stay tuned. Keegan (WMF) (talk) 05:29, 5 March 2014 (UTC)Reply

Share to Social Media

edit
  • I would love if I have the buttons to click and share the media easily to twitter or Facebook. Moreover it took a little time to load for the first time. --Jayabharat (talk) 04:12, 28 February 2014 (UTC)Reply
    • That has proven to be controversial on English Wikipedia. Several proposals to add share buttons have been made, but the community falls roughly 60/40 against such an addition. If social media integration was a built in feature with Media Viewer, there are segments of the Wikipedia community that would view it as the Foundation bypassing the consensus process and ignoring the wishes of the English Wikipedia community. Of course other projects feel differently, but it's certainly not a change I'd make without having a conversation about it with the projects that haven't adopted social media integration. Sven Manguard (talk) 01:21, 1 March 2014 (UTC)Reply

I heard that social media integration is problematic because of the way share and like buttons work, namely because of privacy issues that might be against the Wikimedia privacy policy. I'm not a legal or technical expert though, just have rad this several times, also when the topic came up on huwiki, this was the reasoning against it. Teemeah (talk) 14:09, 3 March 2014 (UTC)Reply

Yeah, it's a common argument, but also somewhat flawed. They can be implemented in a way that would avoid the privacy problems, it's just that most websites don't care about your privacy. The problem is usually more that people think it is a form of 'sponsoring' commercial platforms. (I don't really get it, since we do the same for maps, but whatever). TheDJ (talk) 19:51, 3 March 2014 (UTC)Reply

Better Font or bigger size for description

edit

For images with large description, the scroll-bar gets enabled. I don't know why, but it doesn't feel great to scroll and read in that box. For example, you may try : https://en.wikipedia.org/wiki/Main_Page#mediaviewer/File:Wes Brady, ex-slave, Marshall edited.jpg . --Jayabharat (talk) 04:12, 28 February 2014 (UTC)Reply


I agree I might find the text too small. My operating system has a high "DPI" setting with 16px font in all menus, which does not reflect on the media viewer. It's also not exactly black. It seems quite difficult to read. —Gryllida 09:59, 7 March 2014 (UTC)Reply

Seconded. Please stick to the standard font size. I noticed this with Flow designs recently as well: please don't make any fonts smaller than the current default, unless the goal is to hide that text. (Such as user-selected superscripts or subscripts or hidden divs noting an ignorable aside.) Sj (talk) 01:15, 15 March 2014 (UTC)Reply

Orientation (or lack thereof): Needs more user awareness of Commons (and what a sister project is)

edit

It is really really hard to understand where the file is. Keep an equivalent of "This is a file from the Wikimedia Commons. The description on its description page there is copied below." somewhere below the image please, before I scroll. —Gryllida 10:01, 7 March 2014 (UTC)Reply

I really don't agree with this. I think the average person really couldn't care less about 'organizational' details like that. The difference between wikipedia's and Commons communities is our problem. A problem that we created ourselves. We shouldn't bother others with it too much. Once they get into the community they will notice soon enough. (i'm sure one of our communities will give them a scolding one way or another). TheDJ (talk) 20:54, 7 March 2014 (UTC)Reply
TheDJ, What worries me is that in my view the architecture of the Wikimedia movement should be as clear to end users as possible. It took me 2 years to learn what sister projects exist, and to fully understand their role (and role of the WMF). I wouldn't actively promote such idea, but I do dislike when steps are taken which are a regression, removing some information which was available before. Gryllida 00:37, 9 March 2014 (UTC)Reply
Right, I get what you're saying. Our end goal is to provide an accessible and positive way to lead someone to the original file hosting on Commons. Once on the Commons file page, it's up to Commons to make it clear what the site is for. I don't think that's something we can promote with Media Viewer to the level that actually fixes a problem that might exist due to other problems in movement communication. Keegan (WMF) (talk) 01:17, 12 March 2014 (UTC)Reply

Feedback on Opt-out Feature

edit
Thanks for your helpful comments about the Opt-out Feature for Media Viewer! Based on your good feedback on this talk page and via email, we now plan to provide an ‘enabled' user preference (option A). This seems to be the favorite solution for community and team members who responded to this question. Gryllida, thanks as well for preparing other possible design directions, which we will consider for future versions. Next, we would appreciate your feedback on Links to Commons, as described in the next section. Cheers. Fabrice Florin (WMF) (talk) 23:46, 10 March 2014 (UTC)

Our goal is to enable Media Viewer by default on all wikis when it the tool is ready. But as recommended by many in this discussion, we would also like to provide a way for users to disable Media Viewer on a given site, so they can opt-out from this feature if they don't want it (see Mingle card #264).

To that end, we are considering these different options:


A. 'Enabled' user preference

Provide a preference checkbox with Media Viewer enabled by default (e.g.: 'Show images in Media Viewer'). To disable MV, users can uncheck this preference.

  • Pros: preferable from a UX point of view, indicates this is our recommended option, more user-friendy than JS gadget option below
  • Cons: this approach has caused problems before, users may not want this option to be selected for them, adds to preference bloat issue


B. 'Disable' user preference

Provide a preference checkbox where Media Viewer can be disabled (e.g.: 'Disable Media Viewer'). To re-enable MV, users can uncheck that preference.

  • Pros: addresses user concerns about pre-selection, more user-friendy than JS gadget option below
  • Cons: unclear what Media Viewer is, confusing because you have to uncheck the preference to re-enable Media Viewer, adds to preference bloat issue


C. Javascript gadget or script

Provide a site-wide gadget (or personal JS script) that would let users disable Media Viewer.

  • Pros: no preference bloat, no cache fragmentation, can simply ride on #263 and provide example JS code.
  • Cons: not user-friendly (the gadget has to be installed manually), the bootstrap script would still get loaded.


Notes
  • If we implement a user preference, the recommended location would be in the 'Appearances' section, under 'Files'.
  • We should also let power users know that they can easily use Ctrl-click or Shift-click to bypass Media Viewer and access images the same way they used to before this feature was introduced. So even with Media Viewer enabled, there are shortcuts you can use to go directly to Commons if you like.


We would appreciate your advice on which of the options above would be most helpful for the majority of our users. Please add and sign your comments below. Thank you! Fabrice Florin (WMF) (talk) 00:07, 8 March 2014 (UTC)Reply


Comments
Suggestion 1 (from Gryllida)
Move the 'About' and 'Feedback' links up for them to be visible before scrolling; add pretty icons; create a local About page.
Provide a 'About' link on the media viewer itself, in one of the corners, before scrolling. Should open a dialog or a page which explains where files are hosted, what media viewer is, and how to toggle it in favour of what exactly (i.e. going to file page at Commons directly)
  • Pros: Easy to locate; no confusing additional 'Media Viewer' term initially (users don't need to care of names directly (although mw:Multimedia/Media Viewer may be linked to from the dialog)).
  • Cons: ?
Gryllida 00:20, 9 March 2014 (UTC)Reply
Suggestion 2 (from Gryllida)
Wherever suitable, take user to a relevant highlighted pref in special:preferences with a 'back to article' link next to it.
Example: A web search engine preferences interface:
 
Gryllida 00:20, 9 March 2014 (UTC)Reply
edit
 
Option A: Simple 'Edit’ button links to Commons file page
 
Option B: 'Edit’ button with tooltip for new users
 
Option C: 'More details on Commons’

Many folks have raised concerns in our various discussions that the current link to Commons is not prominent enough to help power users go to Commons — or to make new users aware of what Commons is. Right now, that link to the Commons file info page is located below the fold, at the top of the right column in the meta-data panel; the current label is “Learn more on Wikimedia Commons."

As recommended by many in our onwiki, email and IRC discussions, we have been exploring different ways to make this link to Commons more prominent, as outlined in this Mingle card #270.

This link is trying to solve the needs of two very different user groups:

  • Advanced users need a quick link to edit the Commons description page and perform other related editorial tasks for that image.
  • New users want to know more about the image, and also need information on what Commons is and why they should go there.

To address these issues for each user group, we are considering different design solutions, prepared by our designer Pau Giner:


A. Simple 'Edit’ button:
Provide an ‘Edit’ tool above the fold, so that advanced users can quickly go to the Commons description page to edit it. Restrict this to logged-in users only?

  • Pros: gives editors a much-needed edit tool, in a compact format that is easy to understand (pencil icon), making it easier for them to do their work
  • Cons: readers could get confused by this tool, which takes them to a completely different site (so we may want to not show it to them at all).


B. 'Edit’ button with tooltip:
Provide the same ‘Edit’ tool above the fold, but show a tooltip on hover, to explain to new users what it does. Show the edit tool to everybody.

  • Pros: gives editors the same useful, compact tool, to help them do their editing work quickly
  • Cons: readers should like the tooltip, but it may annoy some editors (don’t show the tooltip to advanced users?)


C. 'More details on Commons’:
Provide a call to action inviting new users to check more details on Commons, explaining what it is and how to get there. Shown below the fold, after key details.

  • Pros: Clarifies what Commons is and why users might want to go there: to get more details and share free media. Larger panel makes it easier to find.
  • Cons: Below the fold position means many users will not see it. Consider using it in combination with Options A or B above?


We would appreciate your advice on which of the options above would be most helpful for both new users and power users. Note that we may want to use some of these design ideas in combination (e.g.: Option B + C), to offer different solutions to meet the specific needs of each user group.

Later this week, we will ask your advice about adding a button on Commons to open an image in Media Viewer. Thanks as always for your constructive advice — and speak with you soon! Fabrice Florin (WMF) (talk) 23:46, 10 March 2014 (UTC)Reply

Comments

  • I would perhaps prefer C, as other options expect user to be interested in editing. They are often not. Gryllida 09:21, 11 March 2014 (UTC)Reply
  • I think that a combination of B and C is the best solution: an edit button for advanced users that leads directly to commons without scrolling needed with a small explaining tooltip (that is, imho of power user, not annoying) and a "More details on Commons" area for readers that are looking for all metadata of the file. Tpt (talk) 18:31, 11 March 2014 (UTC)Reply
  • I'd like to vote for a combination of B and C, too. It's easier for power user to look after a link toward Common. B will give the instinct help for others. --Fantasticfears (talk) 13:27, 12 March 2014 (UTC)Reply
  • B is important. I agree that B and C are independent; C would also be useful. Sj (talk) 01:10, 15 March 2014 (UTC)Reply
  • A is mysterious, B and C can both be useful (with some tweaks to the confusing wording of the text). None solves the problem of giving a link which is visible (rather than outside the screen) and actually seems a link, let alone a link to where the file actually is. I still have no idea why the file title would not be a link, as seems most obvious; the pencil icon can convey part of the meaning/satisfy part of the use cases; for the others, if for some reason we're forced to use an icon separate from the title, perhaps the clearest icon possible is a "permalink" icon, a variant of the chain kind I suppose (permalink is a concept known in most websites). --Nemo 12:15, 22 March 2014 (UTC)Reply

Location maps

edit

OK, somewhat complicate to detect and work with, I'm sure, but due to the discussion about maps, I noticed that the MMV doesn't really like locator maps. Take for instance en:Template:Location_map+ and for instance the example on en:Template_talk:Geobox/test1. These are common use cases in the Wikipedia's, and the code should be able to at least do something predictable with them. (instead of showing the overlays in separate views). TheDJ (talk) 08:21, 7 March 2014 (UTC)Reply

I've filed this as an enhancement bug request since it might be difficult to accommodate. Thanks, TheDJ. Keegan (WMF) (talk) 19:26, 12 March 2014 (UTC)Reply

Remove the arrows and view of other images in the article

edit

Quite often an article has images which are not representative of the subject, alone, and without a relevant clear label, clicking the arrows is confusing. With old system, I didn't miss this feature, and with the media viewer, I don't use it, but it occupies space and gets in the way.

It's simple: nobody requested or needs this at Wikipedia or sister projects, and it's getting in the way.

  • When I'm viewing a file at Wikipedia or another sister project, have no arrows.
  • When I click a file from a Commons gallery, it's ok to have arrows or do a slideshow.

Gryllida 00:29, 9 March 2014 (UTC)Reply

Totally agree. There's a template for climate that has some icons, those icons are shown as if they are related to the article on the viewer.--Pertile (talk) 21:54, 17 March 2014 (UTC)Reply
I disagree, if I am looking on a gallery in an article on Wikipedia, the arrows are extremely helpful and save me a lot of clicks. Please keep them. --Ainali (talk) 11:29, 18 April 2014 (UTC)Reply
Yes, if you're looking at a gallery in a Wikipedia article, fine. I totally support a better Media viewer for article galleries! But what is the point of clicking through to this: https://en.wikipedia.org/wiki/Walvis_Bay#mediaviewer/File:Namibia_location_map.svg ? And how do you get back to the point you were initially reading in the article?
Re: "nobody requested or needs this at Wikipedia or sister projects", the Media viewer risks turning Commons into a dead place. In french and german Wikipedia, now, you are directed to commons immediately when you click on a picture, this traffic will disappear. Nobody (except Wikimedians) clicks on the tiny commons symbol at Media viewer, that's just an alibi. Actually the media files in the commons category for the article should get more prominence, should become more accessible for readers, but the Media viewer will lead to the opposite: Wikipedia readers no longer visit and see Commons and commons categories. --Atlasowa (talk) 13:57, 30 April 2014 (UTC)Reply
IMO creating artificial traffic on Commons by forcing the user to go there just to get a decent look of the image was a bug, not a feature. But anyway, I don't see how this is related to having the prev/next arrows. According to the statistics, on average people look at about 2.5 images per lightbox session, so the prev/next feature does get used a lot. (Note that everything down from "metadata open" on that chart is not actually measure yet so those numbers are not real.)
And how do you get back to the point you were initially reading in the article? -- you should be able to do that simply by exiting MediaViewer. If that does not work, could you describe what exactly happens? --Tgr (WMF) (talk) 19:14, 30 April 2014 (UTC)Reply

Please do not go full screen

edit
 

Please don't go full screen. It's confusing as the reader doesn't understand that he/she is still on the same site. I included a drawing of what I would expect instead. Gryllida 00:25, 9 March 2014 (UTC)Reply

Hmm, interesting. Thanks for the mock-up. Keegan (WMF) (talk) 19:11, 12 March 2014 (UTC)Reply
I agree. This is the only place in our interfaces where your screen and menu bars are overwritten, and you have to find and use a small "X" in a corner to close the screen you landed on. I'm not particularly keen on that design, but most of all it's inconsistent. If we start using "click X to go back" in lots of interfaces, readers may get used to it. For now, I would suggest not creating overlays that make the standard nav stop working. Sj (talk) 01:13, 15 March 2014 (UTC)Reply
+1 the black background after the first click on the image could be "nearly fullscreen", but you should see the article page on the edges behind the media overlay. (unkess the users clicks "full screen".--Sebaso (talk) 08:35, 16 March 2014 (UTC)Reply
The intent of media viewer is to give images space to be viewed, understood and enjoyed. This mock-up displays the image at the same size as the image in the article, making it a metadata pop-up, not a media viewer. I think there's something to be said for metadata pop-ups, but they're more useful as a delayed hover action rather than a click action which is an affirmative step to get a larger view. See Beta Features/Hovercards (which is inspired by the navigation popups gadget) for ideas in the direction of surfacing relevant information on hover.--Eloquence (talk) 05:51, 16 March 2014 (UTC)Reply
I love the option to go full browser width (on galleries) or fullscreen --Subfader (talk) 13:24, 16 March 2014 (UTC)Reply
I would perhaps consider having a "default to full-screen" tick box, and a "go full-screen" button, on a metadata pop-up. Otherwise it's really difficult to match a user's expectations: he/she expects to see something more about the image while stay on an article, and going full-screen directly doesn't meet such expectation. Gryllida 00:14, 30 March 2014 (UTC)Reply
One would think that is the user expectation and experience, but it turns out that it is not :)
There are some fundamental problems from the user experience standpoint to make the image not go full screen in Media Viewer. The most prominent is a user figuring out the controls and how to exit the viewer. When presented with a pop-up style box for an image there is not a clear expectation of how to close the viewer. However, when we make Media Viewer full screen, users find it much more navigable and a much more pleasant media viewing experience overall. It becomes a much more immersive experience, which is what we want out of the Media Viewer. A full screen display of some sort is the standard experience on most of the other major sites as well, including Google Images, Facebook, flickr, for instance. There are more examples.
Overall providing a full screen for Media Viewer accomplishes the goal of a rich viewing experience as well as the clarity of control and ease of exit in functionality. Pop-ups do not provide this necessary functionality as well as the full screen. Keegan (WMF) (talk) 16:51, 1 April 2014 (UTC)Reply

┌─────────────────────────────────┘
Sj, if you have some time you might be interested in watching two of the design sessions where the current X/close for Media Viewer developed from in part: Design session #5 and Design session #10. Even in the early prototypes users were able to identify and execute how to close the viewer. There's some great other design tidbits in there as well (thanks, Pau!). Keegan (WMF) (talk) 21:00, 1 April 2014 (UTC)Reply

Hello Keegan, thanks for the deeplinks! That's cool to see. Though I'm not convinced that this implies 'full screen improves clarity of control', and I wouldn't describe "almost-full screen" as a "pop-up". As for immersiveness: I'd feel less trapped by the current design if there were more & clearer interactions available... clicking on the image, showing sets of related images, clicking outside the image.
Re:examples of full-screening on other web sites:
  • Facebook makes the background semitransparent: you can still see the page behind it. With a large screen, you can see the full FB border-interface you are used to. And clicking on the background outside of the image takes you back to where you were.
  • Google Images doesn't quite go fullscreen: it expands to the width of the screen but above & below you can see you're still in the screenful of image search results.
  • Flickr doesn't really have a "non-Image-viewing" core function. However, every major Flickr-page that might take you to an image-focus page is linked prominently "above the fold": a link back to the user-page of the uploader, and any album it's a part of.
Regards, Sj (talk) 02:54, 2 May 2014 (UTC)Reply

Accessibility

edit

I was just realizing that due to the lightbox nature of this project, it's really important to do at least the minimal amount of accessibility testing with screen readers on this feature, before it is released. I'm sure screen readers don't naturally understand overlays like this and need some ARIA love. This feature is also going to be on every page, and seriously affect the experience of people with assistive technology. TheDJ (talk) 07:40, 7 March 2014 (UTC)Reply

Accessibility is always an important consideration; the blurred image while loading can be controversial for those with visual impairment, for example. We'll take screen readers into account. Keegan (WMF) (talk) 19:12, 12 March 2014 (UTC)Reply

With the latest https://www.mediawiki.org/wiki/Talk:Typography_refresh#Latest_release all hints (icons, frames) around pictures disappeared - so now its really hard to understand that you can click on pictures for a larger version/more information. --Sebaso (talk) 08:55, 16 March 2014 (UTC)Reply

"Collection"

edit
 
The next version of Media Viewer 0.3 will support collections of media files in different formats.

What is a collection? [1] was mentioned in bugzilla:5383#c5 but only links a page now redirecting to this page, which doesn't explain the term despite using it twice. I didn't find an explanation in this talk either. --Nemo 08:07, 11 March 2014 (UTC)Reply

Hi Nemo. I archived and redirected the other talk page last week so we don't have split communications. You can find the archive linked at the top of this page :)
The relevant section seems to be this one. It seems that a "collection" is synonymous with a "gallery" in this context. Keegan (WMF) (talk) 18:16, 12 March 2014 (UTC)Reply
Thanks for your question, Nemo. In our design work for Media Viewer, we have been using the word 'collection' as a generic term to describe any group of media files which could be displayed in a sequence in the Media Viewer. For example, all images or media files in an article can be viewed as a collection; so can all images in a gallery, or a category -- or even a PDF slide show. We aim to provide a consistent user interface for interacting with such collections, regardless of their specific forms. Here are our first design slides, which illustrate how we envision this collection user interface to work. And here is a first development ticket for a collection navigation strip, one of the core components of this UI. We plan to start this development work in late spring or early summer, once we are caught up with other high priority tasks. Hope this helps. Comments welcome. :) 07:52, 13 March 2014 (UTC)
Was this new terminology documented somewhere? Please avoid using undocumented jargon. --Nemo 15:24, 31 March 2014 (UTC)Reply
I'm still looking for a dictionary to understand the multimedia team efforts. Thanks, Nemo 11:38, 16 April 2014 (UTC)Reply

Scrolling problems

edit

I have noticed two problems when using Media Viewer. Screenshots can be produced if desired. I am using the latest version of Safari for Mac.

  • When scrolling up to reveal the lower portion of the image label, the label goes behind the image for a moment, before jumping to the front as it should be.
  • After using the fullscreen view and then returning to regular view, I am able to scroll the label so far down that it is not shown at all. It can also be scrolled back up onto the screen.

Very nice work overall. JamesDouch (talk) 09:24, 13 March 2014 (UTC)Reply

I'm not sure if this post has been seen yet or not. Anyway, the first problem I mentioned no longer occurs with the current version of Media Viewer. JamesDouch (talk) 12:59, 4 May 2014 (UTC)Reply

Looks like we missed this comment; sorry about that! Could you add browser/OS details? --Tgr (WMF) (talk) 17:43, 4 May 2014 (UTC)Reply

Eh, read first, write later. We'll look into it. --Tgr (WMF) (talk) 17:44, 4 May 2014 (UTC)Reply

Discuss this image

edit
File:Media Viewer - Edit This File Tooltip - Mockup.png
Mockup for the Media Viewer edit tool

Firstly, lovely work on the viewer: it is a much better viewing experience, and will be simply great for browsing as well once you can see related files, like the category boxes at the top of old-style Commons pages.

A link to the Commons talk page would be useful. People often need a way to leave a comment about an image. A link in the main metadata saying "Discuss this image" or "Discuss" may do the trick.

Else readers may edit the description field for lack of a more appropriate link :-) Sj (talk) 01:18, 15 March 2014 (UTC)Reply

Dear Sj: Thanks so much for your kind words about the Media Viewer, which mean a lot to us :)
We're already considering adding 'Discuss this file' for the next release, as outlined in this Mingle ticket #225. I'll ask Pau what he thinks about including it sooner.
In the meantime, we are including two features to make it easier for folks to access the Commons page:
So for now, either of these tools will provide an easy way for people to join discussions on Commons. Fabrice Florin (WMF) (talk) 01:27, 18 March 2014 (UTC)Reply

Upload a new version

edit

This is a useful link on current Commons pages. Please include that in this design. This can be shown to both logged-in and logged-out users; the logged-out users simply need to sign in first. (Compare how the mobile site encourages edits even if you're not logged in, but gets you to log in en route to making the edit). Sj (talk) 01:18, 15 March 2014 (UTC)Reply

hmm, i don't think we should just slap a button/link in there. Contribution workflow is important, but mobile also started with reading before taking on more complicated problems. TheDJ (talk) 15:11, 15 March 2014 (UTC)Reply
Yeah, this needs to be thought through in the context of the overall contribs flow.--Eloquence (talk) 05:56, 16 March 2014 (UTC)Reply
edit

Large images are thumbnailed. On the old description page, clicking on the image or on a "full resolution" link would take you to it. In addition, a number of thumbnail resolutions are offered.

These are important options for reusers. Sj (talk) 01:19, 15 March 2014 (UTC)Reply

Fullscreen is in the works. I'm not sure at the moment if this includes full resolution. Fabrice? Keegan (WMF) (talk) 04:49, 16 March 2014 (UTC)Reply

We have a fullscreen feature (I don't think there are any pending parts), but the only thing it does is give you a screen-sized thumbnail (instead of a browser-window-sized one). Forcing the user to view the image just to be able to download it is poor UX (Commons has lots of huge images which will probably crash your browser if you try viewing them); we have plans to offer downloads in a more user-friendly way. --Tgr (WMF) (talk) 02:04, 17 March 2014 (UTC)Reply

Absolutelly agree on that. Now I do feel like I am obliged to downlod the image, to see any details on it. (crap!)
If viewing some map (for example), You need to go in much higher resolution then the height of your screen allows!!
--Reo On (talk) 15:15, 4 April 2014 (UTC)Reply
Plans... You shouldn't implement this kind of change before it has essential features like that ready.
Full resolution and scaled down versions are really missing. -- Lord van Tasm (talk) 17:00, 13 May 2014 (UTC)Reply

More visible "Close" button, or close on click outside of the viewer

edit

The X in the upper-right hand corner is not obviously a hotspot for closing the media viewer. Something much more visible would be appropriate, particularly for an initial rollout. "Close (X)" or a much larger button would help.

Even better and clearer: a version of the viewer like Gryllida proposed above, which doesn't take over the entire screen, leaves the top and side menus and the article title visible, and closes when you click anywhere outside of it. Sj (talk) 01:26, 15 March 2014 (UTC)Reply

Hello Sj. This is a complicated issue from the user experience standpoint for a couple of reasons.
In general we avoid the word "Close" because it's another point to be translated; specifically, the English word "close" and its connotations and denotations are widely diverse for translation options. In other words, the word "close" is not as easy to translate as it would be expected. X, thanks to operating systems and browsers, is pretty universal as a symbol for what you want to do.
The issue with the X in the upper right corner has to do with a split in operating systems/browsers. Unix/Linux/Mac OS and Safari browser users look for an X in the left corner. Windows OS and IE, Chrome, and Firefox browser users look for an X in the right corner. It's not easy to solve, and it gets more complicated when we consider RTL language browser conversions.
As for Gryllida's design, it will be up to the design team and Fabrice to look at that option for a smaller window. Personally, I quite like it :) Keegan (WMF) (talk) 04:14, 16 March 2014 (UTC)Reply
Thanks Keegan. I think having space 'outside' of the viewing area to click on, as in Gryll's design, would be extra clear. Or having a larger X-area, or coloring its foreground and background differently so it is highlighted. No problem with "upper right" as a region, from my perspective. Sj (talk)
Sj: The purpose of the media viewer is to give images the space they need to be understood, viewed and enjoyed. Confining them again into a tiny pop-up would defeat that intent entirely. It's a media viewer, not a metadata pop-up. That is not to say there isn't a place for better metadata tools.
Pau just announced the latest round of user tests; so far I'm not seeing any evidence that users are confused by the lightbox view. I do notice that user is trying to close by clicking on the backdrop (in part because the close button is hidden by the usability testing widget). Gilles said in https://gerrit.wikimedia.org/r/#/c/118667/ that there are accessibility issues with a close that's triggered by clicking on the backdrop, but it might be worth testing that a bit more if that's not been done already.--Eloquence (talk) 05:47, 16 March 2014 (UTC)Reply
I would never propose confining the glory of media to a tiny pop-up. But an overlay that covers 90% of the screen instead of 100%, yes that I might. An overlay that is sensitive to people clicking on images, or backdrops, to provide zoom or close interactions: could be interesting too.  :-) Sj (talk) 16:48, 23 March 2014 (UTC)Reply
@Sj: We talked about this a bit in the recent quarterly review. I asked Fabrice (who is currently on a much-deserved vacation) and Pau to see if we can user test the close behavior a bit more. If users are confused by the close behavior, or just intuitively attempt to click on the backdrop, we can experiment more to see if we can introduce that action without diminishing accessibility. Re: size of the lightbox, I think it's ideal to be close to full-screen for images that warrant it to really enable the user to see all the detail of the image without distraction; it might be worth optimizing the behavior in the case of images that are tiny (lots of fair use examples), but it might be more confusing than useful.--Eloquence (talk) 20:51, 25 March 2014 (UTC)Reply

Preview of the previous / next items

edit

I just tested Lightbox_demo and I missed a preview for the items. A row with the previous and next items would be nice so you can skip items etc.

[prev] [prev] [prev] [prev] [prev] [current] [next] [next] [next] [next] [next]

It seems the "collection" has such a feature.

--Subfader (talk) 13:21, 16 March 2014 (UTC)Reply

This is a great suggestion and it's one that we're looking at (Mingle #172) in the collections feature, as you mentioned. This is still in the idea phase for design, but it's something we think Media Viewer should have as well. Keegan (WMF) (talk) 22:54, 17 March 2014 (UTC)Reply

Bigger image when you get the mouse over the image

edit

Great job! In my opinion if you get the mouse over the image the image should get bigger without hiding all of the article, and with a legend saying "click me to get bigger". It could be annoying for some people specially if the image is big on the article, but more people would know about this functionality, and will be easier to convince editors they use "thumb" option in size.--Pertile (talk) 21:54, 17 March 2014 (UTC)Reply

Thanks for the feedback, Pertile. While we do not have plans to make the image get bigger when you mouse over, we do have plans in the works with the upcoming zoom feature that integrates a similar concept to the "click me to get bigger" idea that you mentioned. Specifically, "the overview thumbnail allows the user to zoom-in ( + ), zoom-out ( - ) and reset the zoom level (an expand button that appears on a corner of the thumbnail when the user hovers it)." You can find out more with mockup illustrations at the link I provided above to zoom feature. Keegan (WMF) (talk) 22:59, 17 March 2014 (UTC)Reply
edit
 
Media viewer access from Commons design as a button

Greetings everyone!

As the Multimedia team finishes up this cycle of Media Viewer development, we’d appreciate your feedback on some of its final features, such as the proposed link to Media Viewer from Commons file description pages.

Currently, viewing media on Commons either shows an image standardized on the file description page, or you can click on the image to view it in full resolution. Offering a link to open the file using Media Viewer will allow for a richer media experience, as the viewing size is increased, while still providing useful information, as well as prominent tools for file sharing and reuse.

We propose a "View expanded" link below the image on Commons pages (see mockup thumbnail to the right). This will enable users to open the image in Media Viewer, without making it the standard viewer for file pages. Additionally, if the user clicks "share this file" and it opens in Media Viewer and then the user exits out, they cannot return to Media Viewer without such a link.

You can find more information and comments from the designers on the Mingle card #199 and you can view this mockup of what the button will look like below the file.

Thank you for your time and feedback! Keegan (WMF) (talk) 22:26, 17 March 2014 (UTC)Reply

  • As usual, the button is hard to notice, and it's hard to understand that it's a button doing something, because it's light grey over white.
    • Other than that, it seems quite cluttering, easy to click by mistake instead of "original file" (or vice versa), confusing when opposed to the stockphoto gadget bar at top (or right).
    • It should be one of the buttons above the image, or not be on the file description at all. If that requires integrating stockphoto into the extension, all the better: satisfying the needs of communities shown by default gadgets, and reducing the workload of volunteer gadget authors who have to compensate the inadequacy of MediaWiki, is always a good endeavour.
    --Nemo 12:23, 22 March 2014 (UTC)Reply
Thanks for the thoughts as always, Nemo. Comments from others are still more than welcome :) Keegan (WMF) (talk) 23:01, 27 March 2014 (UTC)Reply
  • @Keegan (WMF): Curious, why not just improve the top bar (Download, Use this file, Email, etc.) and add it to that? I think that'd be more intuitive and could have a lot more potential than the inevitable addition of buttons with no obvious place for their inclusion. Remove the "X", combine "Use this file" into a dropdown with three choices (Use on web, use on wiki, Email), make "Information" less vague. You could also replace the icons with new ones that match the style of the rest of the new Media features and move the "Add a note" button into the bar. Perhaps change the "Other resolutions" into a simple dropdown and put it in the bar as well? I realize this is kind of "Hiding features behind more clicks", but I think it's highly beneficial to lower the text heaviness (which is very heavy on image pages right now), especially since these pages are very confusing to new users and contributors.
  • Holy tangent, Batman! Sorry, I got a bit carried away I suppose. I just hate the current File pages, they're ugly and unintuitive! Point is, I think the problem isn't where you're placing the "View expanded" button, but the current organization of pages in the "File" namespace being a horrible mess that needs to be more modular. --Nicereddy (talk) 04:12, 30 March 2014 (UTC)Reply
  • Yeah, the button as it is currently implemented seems rather "bolted on". I'm not sure we need another layer of zoomed image on the file description page. We already have the click on the preview image to bring up full size (and we also have the ZoomViewer gadget for super large images). Having yet another function to view the image at a larger size seems like a bad UI move to me (interface clutter, user confusion). --Dschwen (talk) 20:31, 15 April 2014 (UTC)Reply
  • In my eyes it does make sense to have a link to the more beautiful (black background, no toolbars, …) fullscreen view Media Viewer offers, but it should be a direct link as the Media Viewer itself is clearly not meant to be accesed from a file description page (strangely, by clicking on Expand view you get to a copy of the page you are on and there are even two links to the file description which is already there in the background (unnecessary reloading)). Also, I don't like the fact it's a button, a link in the File File history File usage on Commons Metadata barTools section of the sidebar would definitely be a better solution. FDMS4 (talk) 22:16, 15 April 2014 (UTC)Reply

I like the button (and Media Viewer) but I don't like the position of the link. Maybe it would be possible to put it into one line with "add a note" so that it doesn't take so much space and makes the file page longer? At the moment you just have to scroll more to see description and categories. --Indeedous (talk) 22:14, 15 April 2014 (UTC)Reply

  • Hi Nemo, Nicereddy, Dschwen, FDMS4 and Indeedous: Thanks for your thoughtful comments about the Media Viewer button on Commons. We will pass them on to our designer Pau Giner when he flies in from Europe tomorrow, and will get back to you with some possible improvements based on your feedback. We are not married to this particular implementation, and I am sure we can find a good solution together. In the meantime, you can read more about the rationale for this feature on our development ticket. Stay tuned ... Fabrice Florin (WMF) (talk) 01:05, 16 April 2014 (UTC)Reply
    • This is not a design question. You're adding technical debt to Commons. Stop immediately. --Nemo 11:28, 16 April 2014 (UTC)Reply
      • I don't think this is a fair statement Nemo, the multimedia team is trying to do the exact oposite of that. They are trying to play catchup to improve the user experience for our re-users. I think nobody had any illusions that this would not mean stepping on the toes of hardcore powerusers at some point. It is up to us to find a reasonable way to please both ends of the spectrum. And a simple "Stop immediately" doesn't seem like a productive way forward. --Dschwen (talk) 15:48, 16 April 2014 (UTC)Reply
 
New proposal to open Media Viewer when you click on the image in the Commons file page
This new solution would be to simply open up the Media Viewer when you click the preview thumbnail on the Commons file page (like it pops up when clicking article thumbnails). This design approach is more consistent with current behavior in articles, galleries and category pages -- and matches user expectations more closely, as well as best practices on the web. To make this even clearer, a tooltip could say 'Open this image in Media Viewer' when you hover over the image preview. To address the needs of power users, a special icon would appear over the image to let you access the original size, as illustrated in this mockup (see thumbnail to the right). Anyone can open that link, even if they are logged out or do not have Beta Features turned on - except if the user has disabled Media Viewer in their preferences (so users could disable this feature if they really hate it).
What do you guys think? This seems like a more elegant solution than adding a button to an already cluttered interface on the Commons file pages. We'd love to reach a consensus for this simpler solution, so we can implement it next week, before we wrap up feature development on Media Viewer. Otherwise, we would need to keep the current ‘View expanded’ button, as described in this ticket #199, for two reasons: 1) if a user wants to see an image in Media Viewer from a Commons file page, they need a practical way to open it with Media Viewer; 2) if a user views an image in Media Viewer over a Commons file page, then closes it, they need an easy way to re-open Media Viewer (all our shared/embed links go to the Commons file page, where they open the image in Media Viewer, so this could happen to a lot of users).
Thanks in advance for your constructive feedback, so we can reach a prompt resolution on this issue :) Fabrice Florin (WMF) (talk) 00:41, 24 April 2014 (UTC)Reply
Oppose: This would make it much harder to get to lager images, as images in Media Viewer are pretty much the same size as on the Commons description page (often smaller, actually), and clicking on the image is the standard/obvious way to get to a larger (full-size) image. Really, I don't get the point of getting to the Media Viewer from Commons pages anyway, as they already have the description/info and large images, and the whole point of Media Viewer is getting to large images and the description/info. Jay8g (talk) 03:44, 24 April 2014 (UTC)Reply
I like that solution. It is consistent and intuitive. I wonder why you even need the button to open a file in its original size on the image. After all, there already is an easily accessible "original size" link directly below the image. Putting an extra button on the image adds a bit of extra clutter and people could misclick it by accident. The link below is easier to hit in any case. --Srittau (talk) 10:52, 24 April 2014 (UTC)Reply

Add the extension to my wiki

edit

How can I add the Extension:Media Viewer to my wiki under Beta-preference?

--Suriyaa Kudo (talk) 17:02, 18 March 2014 (UTC)Reply

Glad you want to try it out, Suriyaa Kudo. On any Wikimedia wiki that you are logged into you can either click on the "Beta" label at the top of your screen, where you have links to your userpage, talk, preferences. The other option is to go to Special:Preferences#mw-prefsection-betafeatures on any wiki when logged in. Let me know if you need any further details or explanation. Be sure to let us know what you think! Keegan (WMF) (talk) 17:31, 18 March 2014 (UTC)Reply
It's ok. :-)
Suriyaa Kudo (talk) 15:37, 19 March 2014 (UTC)Reply
Suriyaa Kudo, I might have misunderstood. Were you asking how to install the extension on your own wiki? Keegan (WMF) (talk) 17:34, 18 March 2014 (UTC)Reply
Suriyaa Kudo, if the question is, "After I have installed the MultimediaViewer extension on my local wiki, how do I add it to my local BetaFeatures extension?" Then the answer can be found here, Using new hooks in your extension. Hope that helps. Keegan (WMF) (talk) 17:41, 18 March 2014 (UTC)Reply
Is this right:
// MultimediaViewer.php
$wgAutoloadClasses['MultimediaViewerHooks'] = __DIR__ . '/MultimediaViewerHooks.php';
$wgHooks['GetBetaFeaturePreferences'][] = 'MultimediaViewerHooks::getPreferences';
// MultimediaViewerHooks.php
class MultimediaViewerHooks {
 
    static function getPreferences( $user, &$prefs ) {
        global $wgExtensionAssetsPath;
 
        $prefs['my-awesome-feature'] = array(
            // The first two are message keys
            'label-message' => 'beta-feature-message',
            'desc-message' => 'beta-feature-description',
            // Path to an image that represents the feature
            'screenshot' => $wgExtensionAssetsPath . '/MultimediaViewer/images/screenshot.png',
            // Link to information on the feature - use subpages on mw.org, maybe?
            'info-link' => 'https://mediawiki.org/wiki/Extension:MultimediaViewer',
            // Link to discussion about the feature - talk pages might work
            'discussion-link' => 'https://mediawiki.org/wiki/Extension_talk:MultimediaViewer',
        );
    }
}

?

Suriyaa Kudo (talk) 15:37, 19 March 2014 (UTC)Reply

MultimediaViewer does include those hooks though, so if you have installed both it and BetaFeatures, things will just work. (This also means that if both MediaViewer and BetaFeatures are installed, there is no way to make MediaViewer work outside of beta. This is not ideal, and will change soon, so for forwards compatibility, you should set $wgMediaViewerIsInBeta = true; in LocalSettings.php, although it has no effect at the moment (you are in beta whatever you set as long as BetaFeatures is installed). --Tgr (WMF) (talk) 19:57, 18 March 2014 (UTC)Reply

Thanks.
Suriyaa Kudo (talk) 15:37, 19 March 2014 (UTC)Reply
Great, Tgr (WMF), thank you for the explanation. I'll look into clarifying the documentation. Keegan (WMF) (talk) 16:33, 19 March 2014 (UTC)Reply
Just tried it. Installed BetaFeatures and MultimediaViewer. The MultimediaViewer didnt show up on the beta preference page before I changed "$wgMediaViewerIsInBeta" from false to true in MultimediaViwer.php. (version wmf17) Christian75 (talk) 20:34, 22 March 2014 (UTC)Reply

Comment (shortcut, and use on en wiki, and ...)

edit
  • It would be nice if f switched full screen (on/off).
  • It shouldt say "use this file"; when the file is non-free
    • The box which opens when pressing "use this fil" doesnt use the full screen (I can only see part of the file title to use) - ask for screen shut...
  • As said before, its not easy to find the description page. I do not expect to learn about the file, when I see a wikipedia logo and "learn more" - then I expect to learn more about wikipedia...
  • The "Used in xx pages" doesnt work when the file is local (it counts different images, from other wikis)
  • When I see "CC BY-SA 3.0" I expect to come to the licens page when I click, not to the description of the file.
  • External links should be marked as external links, like link
  • Maybe right click should open a box which say where to copy the image from

My two cent, but I like the viewer :-) Christian75 (talk) 11:05, 21 March 2014 (UTC)Reply

And we appreciate your two cents, Christian75. Thanks for detailing $wgMediaViewerIsInBeta in the section above as well. Most (if not all of) what your comments above are about are still being finalized before the global release. Always good feedback to have. Keegan (WMF) (talk) 18:06, 24 March 2014 (UTC)Reply

Please consider the various users

edit

Hello,

What is "modern" is not always useful.

The needs of those who write are not the same than for simple readers.

Maybe a simple click opens the picture for a better seeing, a double click opens directly the Commons page for working.

Best regards,

Jean-Jacques MILAN (talk) 13:49, 23 March 2014 (UTC)Reply

 
I really like the new media viewer, and I will certainly not turn it off and I will use it as my default view. But when editing articles the media viewer slows down my progress considerably. Now, instead of just clicking on an image to go to the image details page, I have to 1. click the image, wait for the overlay to open, wait for the Commons link icon to appear, navigate my mouse to the icon and click. One easy solution is to have a commons icon appear overlaid over an image when you hover the image. This would provide a direct link to the commons description page. --Srittau (talk) 02:05, 19 April 2014 (UTC)Reply
You should be able to right click and "open in new tab" on any file that's embedded in the page, if that's faster for you. --GeorgeBarnick (talk) 02:21, 19 April 2014 (UTC)Reply
That's actually a very good hint. Mid-click also does work. My workflow won't suffer. :) Now the only concern I have is that this feature is not very discoverable. --Srittau (talk) 03:19, 19 April 2014 (UTC)Reply

How do you find Categories, galleries etc.?

edit

Am I just not seeing something? Usually I want to see what else is in the category, what other categories it's in and such. Is there a way to do this, or is ditching the Media Viewer a necessary step to get this info? Otherwise, it's great for looking at pictures, but not so good for researching, imo. Parabolooidal (talk) 22:31, 24 March 2014 (UTC)Reply

Thanks for the feedback, Parabolooidal. Categories are not currently shown as the Multimedia team was working out how to best display them. There is a plan now to show categories as tags. Galleries will be supported in the near future as well. Keegan (WMF) (talk) 17:32, 30 March 2014 (UTC)Reply
Categories are the basic tools i need for my work with commons. They are one of the fist things i look at after opening an image. so without categories theres no way for me to use the viewer for my daily work. -- Lord van Tasm (talk) 17:03, 13 May 2014 (UTC)Reply

Don't show hidden categories

edit

The category section of Media Viewer is often polluted with irrelevant categories, typically hidden categories (ie Category:Uploaded with UploadWizard). These are rarely, if ever, relevant to the picture, and should not be displayed so as to not confuse inexperienced editors/readers, the people who Media Viewer will be most important for, and so as to make the real categories be emphasized. Jay8g (talk) 03:01, 25 March 2014 (UTC)Reply

Indeed ; this is tracked at bugzilla:62277. Jean-Fred (talk) 20:06, 25 March 2014 (UTC)Reply

"Public domainPublic domainfalsefalse" bug

edit

The license template has the garbage text "Public domainPublic domainfalsefalse" in it. Please see File:Annotated screenshot of bug in Media Viewer's license display.png for an annotated screenshot of the bug. Sven Manguard (talk) 06:59, 26 March 2014 (UTC)Reply

Thanks, Sven Manguard, really appreciate your bug report and helpful screenshot. I believe this bug is fixed now, though it may not yet be deployed on your home wiki yet. But you should be able to test it on this beta test page, if you don't mind slow performance - or try it on this MediaWiki.org test page, where we deploy every Thursday. Either way, please let us know if the issue has been addressed to your satisfaction, and thanks again for your thoughtful feedback! Fabrice Florin (WMF) (talk) 00:47, 24 April 2014 (UTC)Reply

Show progress bar while an image is loading

edit

I would like to suggest showing a progress bar instead of a blurry image. Otherwise it gets difficult on eyes and I (on a slow internet) don't know when to expect it to finish. Gryllida 00:11, 30 March 2014 (UTC)Reply

There is a progress bar, at the bottom of the image. --Tgr (WMF) (talk) 06:08, 30 March 2014 (UTC)Reply

edit

For example, for this picture, the HTML code for embedding is:

<p>
  <a href="https://commons.wikimedia.org/wiki/File:Fran%C3%A7ois_Hollande_(Journ%C3%A9es_de_Nantes_2012).jpg">
    <img src="https://upload.wikimedia.org/wikipedia/commons/0/07/Fran%C3%A7ois_Hollande_%28Journ%C3%A9es_de_Nantes_2012%29.jpg" height="145" width="91">
  </a>
  <br>
  „François Hollande (Journées de Nantes 2012)“ von
  <a rel="nofollow" class="external text" href="http://www.flickr.com/people/44790477@N05">
    Jean-Marc Ayrault
  </a> - <a rel="nofollow" class="external text" href="http://www.flickr.com/photos/jmayrault/6730212809/">
    François Hollande et Stéphane Hessel aux Journées de Nantes
  </a>. Lizenziert unter cc-by-2.0 über Wikimedia Commons.
</p>

In my opinion, cc-by-2.0 should be a link to the license text as required by the license. (Vice versa for the other licenses that require a link to the license text.) Regards, --Ireas (talk) 08:42, 2 April 2014 (UTC)Reply

This was omitted due to technical problems and should work in the version deployed today. (Wikimedia Commons will also become a link.) --Tgr (WMF) (talk) 22:03, 3 April 2014 (UTC)Reply

@Tgr (WMF): Thanks for dealing with this. Yet I stil don’t get a link; neither on dewiki nor on Commons. Regards, --Ireas (talk) 22:36, 5 April 2014 (UTC)Reply

ːThere was no deployment this week, for reasons unrelated to MediaViewer, so add one more week. (Even if there was one, it wouldn't effect Commons or dewiki yet; there is half a week and one week delay, respectively, in deployments to those sites. mediawiki.org is always the best place to check for new things.) --Tgr (WMF) (talk) 23:58, 6 April 2014 (UTC)Reply

  Done. Works for me; thanks! --Ireas (talk) 22:22, 18 April 2014 (UTC)Reply

Translation

edit

Hello,

Where can I change the Hebrew translation? There are couple mistakes in it. Neukoln (talk) 16:28, 8 April 2014 (UTC)Reply

Translations for Media Viewer (and all of MediaWiki) are done on translatewiki. If you do not have an account there - it's not a Wikimedia wiki - then you need to register one through the simple three step process. After you have your account, you can help with the translation for Media Viewer here. Let me know if you have any further questions about translating, Neukoln. Keegan (WMF) (talk) 18:27, 8 April 2014 (UTC)Reply
Thanks, I have an account in translatewiki, but I didn't find the messages, so I ended up here :) (I've searched for the translation without taking into account the possibilty of $1). Is there a way to view all pages that use one of the messages? specifically "More details on $1". The translation of this one depends on the context. it can be either "פרטים נוספים על" (the current translation) or "פרטים נוספים ב" (the right translation if $1 = wikicommons, and the meaning is more info about the file. If the meaning is more info about wikicommon the project, than the first translation is fine after all). Neukoln (talk) 07:43, 9 April 2014 (UTC)Reply
Add ?uselang=qqx to the url of the page (before the # if already in the lightbox) to see the names of the displayed messages. This makes it easier to then find it in translatewiki. /31.211.223.187 20:33, 10 April 2014 (UTC)Reply

Exit lightbox, goes to top of page

edit

I'm fine with the lightbox ... but every time I hit 'X' and exit the lightbox, I end up at the top of the page. This is annoying when I'm going through e.g. the test page and trying lots of different images and image types. "As a user, I would like exiting the lightbox not to change my position in the page, so that I do not find the experience unduly annoying." - David Gerard (talk) 21:37, 10 April 2014 (UTC)Reply

BTW, the video at the bottom of the test page doesn't do this - David Gerard (talk) 21:38, 10 April 2014 (UTC)Reply
Right, I see what you mean. Good catch, David Gerard. I think at this point I've opened it up so much I don't even notice that inconvenience. We'll pass this along to see if it can be rectified reasonably. Keegan (WMF) (talk) 22:19, 10 April 2014 (UTC)Reply
This is a regression. Created card 439. --Tgr (WMF) (talk) 22:42, 10 April 2014 (UTC)Reply
...so that's why it wasn't a problem that I noticed before. Thanks, Tgr. Keegan (WMF) (talk) 23:13, 10 April 2014 (UTC)Reply

Statistics on image viewing

edit

Are any logs kept when images are viewed through Media Viewer? It would be useful to be able to look at viewing statistics, especially since Media Viewer will probably replace many views of file description pages. Data on the referring page (if any), the date/time, and the resolution viewed would be useful IMO. (The last two might need to grouped before any public release.) --Avenue (talk) 05:25, 11 April 2014 (UTC)Reply

Hi Avenue. Thanks for your good suggestion. We hadn't planned to provide detailed viewing statistics for every image served in Media Viewer; but if enough people want this feature, we'd be happy to put it in the backlog for future releases. In the meantime, you may be interested in these metrics dashboards for Media Viewer, which show how this tool is being used in the aggregate. Please let us know if you have any questions. All the best. Fabrice Florin (WMF) (talk) 23:19, 14 April 2014 (UTC)Reply
Thanks Fabrice, the aggregate stats are interesting. I do think detailed image viewing stats would be even more useful, especially if we can enable people to easily access and compare viewing stats for all images in a particular article. For now, my main concern is whether the necessary data is being collected. How exactly it would be made accessible can be sorted out in due course. --Avenue (talk) 00:43, 20 April 2014 (UTC)Reply
You're very welcome, Avenue. Your suggestion makes really good sense to us, and we will consider it for future releases. For now, I have filed this ticket so we don't forget. Thanks for this good idea :) Fabrice Florin (WMF) (talk) 00:59, 24 April 2014 (UTC)Reply

my comments

edit

the tool is nice. but i have few comments:

  • there should be a way to access the source page, for editors and readers. and i mean in Wikipedia (for me its he.wiki) not only in Commons.
  • an option to turn it off would be nice - people have their habits and preferences so would be nice to have control, and for editors that's important - so at list for editors.
  • the background color (black) is too contrastic (in reference to the white BG it opens from) so i suggest a lighter color or preservation of white.

tnx, Dalilonim (talk) 14:03, 11 April 2014 (UTC)Reply

Thank you for the comments, Dalilonim. We'll see what can be addressed about your first comments. As for the second comment, there is an option to disable Media Viewer by unchecking the "Enable new media viewing experience" box in your preferences: Preferences -> Appearance -> Files -> Uncheck "Enable new media viewing experience". Your third point is a good suggestion, but all usability studies and industry best practices use a black background to reduce eye strain and enhance color and detail in photos. Let us know if you think of anything more and thanks again. Keegan (WMF) (talk) 22:14, 12 April 2014 (UTC)Reply
Could you at least make that background translucent, like all the other sites following industry best practices do?[2] The current solid black background loses all context of the page at which it's embedded. Diego Moya (talk) 16:24, 17 April 2014 (UTC)Reply
edit

A list of pages on which the image is used is displayed, but it appears to ignore namespaces when displaying the title of those pages. So "Talk:Philadelphia" shows up as just "Philadelphia". The link goes to correct namespace; it's just the display that's misleading. LtPowers (talk) 17:36, 14 April 2014 (UTC)Reply

Great find, LtPowers. I filed a bug to fix that. Keegan (WMF) (talk) 18:41, 14 April 2014 (UTC)Reply
File usage Links make no sense in my mind, when only a few are displayed. Which are chosen? I see only 6 of 30 and for the rest I have to go to an extra page. This makes ist even more complicated as the original commons page where I had everything in view just by scrolling the page once. -- Lord van Tasm (talk) 17:09, 13 May 2014 (UTC)Reply

Off switch

edit

I don't mind the implementation of this new tool if there's the option to not use it. Even if Media Viewer is the new default, will "switch Media Viewer off" be an option? If not, why not? DragonflySixtyseven (talk) 19:48, 14 April 2014 (UTC)Reply

Hey DragonflySixtyseven, we agree with you. You can easily turn off this feature in the 'Appearances' tab of your preferences, then uncheck 'Enable media viewing experience'. Try it out here on MediaWiki.org and let us know how it works for you. Cheers :) Fabrice Florin (WMF) (talk) 23:14, 14 April 2014 (UTC)Reply
Hej, can you help me with that? I cannot find this in my preferences (I found Media Viewer turned on on my Sewdish wiki account. Note, that I have usurpated Macuser account on most wikis I use, but on mediawiki someone else is using it, and my appeal to give it to me is still waiting, so that I can not log in as Macuser on Mediawiki. 78.73.55.57 15:20, 9 May 2014 (UTC)Reply
should be at sv:Special:Inställningar#mw-prefsection-rendering the option “Aktivera en ny multimediaupplevelse” --se4598 (talk) 15:35, 9 May 2014 (UTC)Reply
Thank you very much, it was really helpful. I cannot understand why would one put efforts in developing such a strange thing. 78.73.55.57 18:32, 9 May 2014 (UTC)Reply

Media Viewer Launching Soon

edit
 
Media Viewer lets you browse larger images on Wikimedia sites.

Greetings! We would be grateful for your help to prepare for the upcoming release of Media Viewer, a new tool for browsing multimedia content on Wikipedia, Commons and other Wikimedia sites.

We now plan to gradually release this tool in coming weeks -- starting with a few pilot tests this month, followed by wider deployments next month, as described in this release plan.

As we approach release, we would like to know what you think of this tool, so we can address any critical issues, based on your feedback. If you haven't already, we invite you to try the tool in beta as described here, then share your comments here.

We are particularly interested in comments on these features:

To learn more about this release, please join our next IRC chat, on Wed. Apr. 16 at 18:00 UTC at Wikimedia's Office IRC Channel. Hope to see you there! Fabrice Florin (WMF) (talk) 01:05, 16 April 2014 (UTC)Reply

Fabrice Florin (WMF), can we please have a feature freeze for a couple weeks at least and ask for community feedback on the existing version? Gryllida 11:37, 16 April 2014 (UTC)Reply

Fabrice Florin (WMF), there are some issues, such as not going full screen, showing metadata more prominently, which are requested by community but not addressed. Please don't deploy yet. Gryllida 11:39, 16 April 2014 (UTC)Reply

I'm testing the Media Viewer, and I've found several critical errors that are showstoppers.

  • When clicking on an image a very blurry version of the thumbnail is shown maximized, and it can be there for up to ten or twenty seconds. As there isn't any spinning wheel animation indicating that the actual high resolution image is being loaded, it simply looks like the image is broken. In some cases there is a (very difficult to see) progress bar below the image, but it doesn't show always, and it doesn't display progress while it's stalled and waiting to load on a slow connection; a continuous animated .gif would work much better to indicate the "loading" status.
  • If the background loading process breaks, there is no indicator that this happened, and the blurry version does remain in place as the only broken version ever displayed, with no obvious way to access the file page to see the original. I've found this happening with File:Clementine_0.6_in_Windows.png in en:Amarok (software). Clicking on the image should go to the File page for it - it works much more reliably.
  • When closing an image, I lose my reading point an the page is scrolled to the top, forcing me to scroll down again to the place where the image is located. This is unacceptable for a supposedly "easy to use" tool.

The thing doesn't look ready for mass deployiment. Shouldn't you first fix critical errors, then decide a release schedule? Sorry but your release plan seems backwards. Diego Moya (talk) 16:22, 17 April 2014 (UTC)Reply

  • There's also no way to pan&zoom into the image with the browser's zoom feature, not even in full screen mode. This one is not a showstopper for most the common cases, but it's quite inconvenient, and prevents users from watching details in the image. All these problems should have been not too hard to catch, by testing how users recover from errors (you are testing users under harsh conditions of unreliable connections and slow computers, and not just in lab rooms in California, right? ;-) That's Wikipedia's target audience). Diego Moya (talk) 16:52, 17 April 2014 (UTC)Reply
  • Someone else from the team will speak to your first two points, but as for the third: losing your place in the page when closing an image will be fixed in today's deployment. It was an unfortunate regression that happened after last week's update. We now have a test going out to prevent this regression from reoccurring.
As for the zoom feature, it is in the works for v0.3. Hope this helps. Keegan (WMF) (talk) 17:58, 17 April 2014 (UTC)Reply
(edit conflict) From the usage videos you linked to above, it seems like you're testing how the media viewer works as a tool for slideshows; but I've seen no use cases to test how it interacts with the encyclopedia - maybe you should also create some cases for these (including more variety of the images - not merely landscapes but diagrams, application screenshots, old newspapers...), with some cases of images whose detail is coordinated with the text around it. The Media Viewer does not even show the image's caption text above the fold, for heaven's sake.
As for the Zoom Feature; I'm looking at the design you link. I don't want to use a zoom's button, I want to use the standard zoom features in my browser over which I have more control than with page scripts. Will that work with the mouse wheel and Ctrl +/-, pinching on mobile, and showing vertical/horizontal scroll bars for panning? It's OK if it works by dragging and pressing on visible controls too, but the basic browser functions should not be broken. (I.e. I already have a very good zoom feature that I like and know how to use, why won't you just let me use it?). Diego Moya (talk) 18:08, 17 April 2014 (UTC)Reply
Same problem here: it takes too much time (many seconds) until the non-blurry image appears. This is a lot worse than going to the traditional description page (see screencast on bugzilla:64135). And I confirm it is loosing the scroll position when the viewer is closed. Helder.wiki 13:21, 19 April 2014 (UTC)

Some more data in case it helps. I've been testing a bit more the two first errors. I've noticed that not seeing the progress bar is because, in the first image I click on any page, the entire float bar does not show at all. I'm testing this on Firefox and Chrome, on the English and Spanish Wikipedias and with two different user accounts (the English one has many gadgets and widgets; I think that's why :File:Clementine_0.6_in_Windows.png didn't finish to load. The Spanish account has most default configurations). I reiterate that, even when I can see it, the progress bar is often too subtle to notice. 2.136.173.188 19:03, 17 April 2014 (UTC)Reply

Hi Diego,

  • we are aware of the loading bar issues and looking for a better way to make it clear the image is loading.
  • we do have an error page for when loading the image breaks. We had a bug where, if you stopped the image loading by closing the lightbox, and the reopened it, it did not reload, and you got the blurry image. Maybe you ran into that one? It should be fixed by today's release. Otherwise, it is not inconceivable that both the image loading and the error page display break in some specific situation, but we would need reproduction steps, or at least an error message from the browser console, to be able to fix such a bug. The example you cited works fine for me.
  • as Keegan said, we now have multiple tests to make sure restoring the scroll position does not break again.
  • I haven't followed the user tests, but for internal testing, we use this suite. If you have suggestions about different kinds of images to include, we would be happy to hear them.

--Tgr (WMF) (talk) 20:57, 17 April 2014 (UTC)Reply

I'm missing images of the following kinds, where the detail is important and they're placed within an article section explaining their content. It would be good to have a representative sample of the following (most of these are from computing-related articles, it would be good to have them from several other fields of knowledge):


 
1888 telautograph patent schema
 
Overview of the various programming paradigms
 
Calligra Active displaying a presentation
 
A screenshot of KNIME.

Diego Moya (talk) 10:41, 18 April 2014 (UTC)Reply



  • Update: Hi Nemo, Gryllida and Diego Moya: Thanks for your detailed feedback and thoughtful suggestions. Many of your recommendations have already been solved or are being addressed, as other team members have pointed out in this thread. Overall, the feedback we are getting from the many other voices in our worldwide community suggests that this product is getting ready for wider release, even if it is not perfect. The key remaining issues are being addressed, such as the image load times, which now seem to be on par with the current file page load times, as shown in this metrics graph. Our gradual release plan seems like an effective way to incrementally test this tool in more and more pilot sites, and we carefully review pilot results each week before proceeding with the next step. So it appears that we are proceeding on the right track, and do not see a need to stop everything as has been suggested by some. Thanks again for your continuing feedback, which is invaluable to us: even if we can't act on every suggestion we get, we read everything, and prioritize tasks to match their overall urgency and team capacity. Onward! Fabrice Florin (WMF) (talk) 02:36, 24 April 2014 (UTC)Reply

Extremely annoying issue with embedded video in news reports

edit
 
Before clicking play

Since my remarks in the "please don't go fullscreen" discussion thread seem to have been overlooked, I've created screenshots to show where there is a most-annoying, and reader-unfriendly, aspect to how video is being displayed.

First, we have a news article — with video clips included — where no clip is playing. Second, and below it, with the clip playing.

 
After clicking play

Where is the point in even bothering to arrange the video within the text? I can't keep reading once I press play; all I can do is abandon watching the video, or sit back and and nitpick over the player controls cutting off the bottom of the actual uploaded video.

 
Similar issue on Wikipedia article Apollo 11

When I created this article, I'd estimate that I spent at least couple of hours looking for an option on [[File:foo]] to leave the damn video playing embedded, where I wanted it. Still haven't found one.

Video can be more than a supplement to an encyclopedia article, sat in a gallery at the foot of the text, which seems the primary purpose of handling it in this manner. I've looked, and can't find a single news source which has video take control away from the user in this manner; nowhere that other text in a report is treated as second-class the second you press play. Sure, I can hit escape and it goes away — that's not the point! This turns "multimedia" into "monomedia". That's fine if you want to take a closer look at a still or diagram, not where text and video are meant to complement each-other.

I assume this is the "Lightbox view", but I did not click on the 'thumbnail'; I clicked on the video's 'play' button. Like every other site on the Internet, I'd expect to then click a fullscreen or 'larger player' button to get this view. The image on the right illustrates the same issue on Wikipedia, where the embedded video is the exact same size as the 'thumbnail' displayed in the static version of the article. It, too, seriously detracts from the experience of reading the article when the media player takes over the browser window. --Brian McNeil (talk) 12:01, 16 April 2014 (UTC)Reply

Fair point, but this is completely unrelated to MediaViewer. Is this a recent change in behavior? --Tgr (WMF) (talk) 18:00, 16 April 2014 (UTC)Reply
Hey Brianmc - This was caused by gerrit:91342. Previously the pop up thing only happened if the video thumbnail was really small (<200px wide). After that change it happened for any video < 800px wide. The setting can be changed on a per wiki basis, so to change it back on Wikinews, just needs some show of consensus on the WC. To change it on all wikis would require some sort of wide discussion probably. Bawolff (talk) 18:52, 16 April 2014 (UTC)Reply
Hi Brianmc, thanks for reporting this issue, even though it's not related to Media Viewer. As a long-time TV producer and documentarian, I feel much as you do about the importance of video and its lack of support on our sites. We were hoping to address some of these video issues this quarter, but are running out of time before our next assignments. So unfortunately we had to push video further out on our roadmap, until we are caught up with more urgent tasks like Upload Wizard and Structured Data on Commons. It breaks my heart to tell you this, but sometimes we have to make tough decisions. :( However, rest assured that we really want to address the issues you brought up, as soon as we can. For now, here's a sneak peak at the new user interface designs we're considering to integrate video and audio in Media Viewer, sometime in the next fiscal year. Be well ... Fabrice Florin (WMF) (talk) 01:24, 24 April 2014 (UTC)Reply
edit

If you are scrolled down on a long page and open the media viewer to look on a file and then close it, I expect to be on the same spot on the page. But instead I am taken to the top of the page. This is very frustrating and unexpected. Closing the media viewer should put you in the same spot as you were when entering it. --Ainali (talk) 07:13, 18 April 2014 (UTC)Reply

This was fixed with yesterday's deployment. I just checked and could not reproduce the issue. Is anyone else still encountering this issue? Keegan (WMF) (talk) 16:10, 18 April 2014 (UTC)Reply

Categories

edit

It seems that only three categories are being shown (not even dots to indicate more); and the category order is being scrambled by putting the cats into alphabetical order. Both of these choices would appear to be undesirable. Jheald (talk) 07:55, 18 April 2014 (UTC)Reply

Agree ; I reported a connex bug some time ago under bugzilla:62277. Jean-Fred (talk) 10:22, 18 April 2014 (UTC)Reply
Thanks, Jheald and Jean-Fred. We had initially intended to show a 'More' link after the first three categories and this requirement fell through the cracks: I just filed this ticket #499 to fix that problem. I also agree with Jean-Fred's proposal to ignore hidden categories, and have filed this separate ticket #498 to address that issue. I can't promise we can fit all these fixes right away, but they are now high on our list. Thanks again for these good suggestions :) Fabrice Florin (WMF) (talk) 01:40, 24 April 2014 (UTC)Reply
I don't see any category on any image. And I need categories. -- Lord van Tasm (talk) 17:05, 13 May 2014 (UTC)Reply

"Created on 1828"

edit

Should be "Created in" if no day of the month is specified

Jheald (talk) 07:58, 18 April 2014 (UTC)Reply

For creator, Artist field should be preferred to Author field if both are present

edit

CC0 (CC-zero) should be recognised as a public domain license

edit

Just showing the CC icon for all CC licenses is somewhat unhelpful. A CC icon specific to the relevant license should be displayed. Jheald (talk) 08:10, 18 April 2014 (UTC)Reply

Agree. Another instance of Media Viewer removing important info from view in a confusing manner.--Paracel63 (talk) 12:39, 26 April 2014 (UTC)Reply

Multiple creators

edit

The viewer doesn't appear to be handling cases where there are multiple {{Creator: }} templates being used for "Artist", only showing the first -- eg cases of Engraver after Original Artist, [8] Jheald (talk) 08:28, 18 April 2014 (UTC)Reply

Images being picked up from templates on Commons file description pages

edit

eg: [9]

The images of the artist (John Leech) and the current location of the work (British Library) make little sense outside their original templates, so probably should not be shown in any slideshow. Indeed it's not clear why any other image should be shown in such a slideshow, for a file from a Commons image description page. But particularly when there is no explanation of where these other images may have come from, nor what may be their relationship to the original image. Jheald (talk) 08:35, 18 April 2014 (UTC)Reply

Make clearer what has to be done for re-use

edit

Hello, I enjoyed seeing the new media viewer very much. A major problem of Commons is, in my opinion, a lack of clarity for the non Wikimedia user how to re-use a file. The media viewer could be still a little bit clearer on what someone has to do if he wants to reuse the image on his own website. I see now the title of the image together with the name of the license on one line, and the name of the creator on the second one. Why not putting name creator name and license on one line, maybe even in quotation marks, and the title on the other? By the way, I would leave away the CC-logo, it is only adding confusion (except for those who already know about the difference between the copyright-sign and the CC-logo, and about the pun intended). Kind regards Ziko (talk) 11:54, 18 April 2014 (UTC)Reply

Agree. A one-line solution presenting a correct (the simplest variant) attribution would be most welcomed. Many thanks in advance.--Paracel63 (talk) 12:41, 26 April 2014 (UTC)Reply

Page jumps to top after closing the media viewer

edit

If I scroll down a page, open the media viewer and then close it, the page scrolls back to the top. --Ireas (talk) 22:20, 18 April 2014 (UTC)Reply

This should be fixed on mediawiki.org. We'll backport on Monday. --Tgr (WMF) (talk) 22:44, 18 April 2014 (UTC)Reply
edit

It should be possible to mark utility files and images as "icons". These are excluded from the gallery view and clicking on them opens the description page directly. It doesn't make sense to have a gallery view for those kinds of icons. If you really want to view them this way, you can always go to the description page and use the enlarge button there. --Srittau (talk) 02:07, 19 April 2014 (UTC)Reply

Adding a metadata class to some ancestor of the image does that. --Tgr (WMF) (talk) 06:04, 19 April 2014 (UTC)Reply

I would really prefer Wiki syntax to achieve this, for example [[File:foo.png|meta|Flag of Fooland]] (where meta could probably be replaced by a better word). Using CSS classes is a power-user feature. Also writing <span class="metatdata">[[File:foo.png|thumb|right]]</span> to achieve this in one-of situations is hard to write, hard to read, and hard to understand for ordinary editors. --Srittau (talk) 16:14, 19 April 2014 (UTC)Reply
@Srittau: Tgr Also, metadata should exclusively be used for elements that are not considered part of the 'content proper'. This flag IS part of the content. Let's start with a more fundamental question. Why Srittau, do you think it should NOT be visible in the viewer, can you think of other images that should not be visible (but are part of the content and can you think of similar images that you would want to see, but are otherwise a lot like this flag. Let's see what is needed, before we start adapting the code. TheDJ (talk) 16:38, 19 April 2014 (UTC)Reply
I think, images with "icon" character should not be displayed. Also, there are some special cases, where viewing an image using the media viewer doesn't make sense. Let's have a look at the Namibia article on en.wikipedia. In my opinion the following images should not be displayed in the media viewer: (Please note that some of the examples I am listing are already missing from the media viewer. I am listing them for completeness sake.)
  • The earth icon next to the location in the country box. (Already suppressed.)
  • Same for the "up" arrow icon next to the population number. (Already suppressed.)
  • In the "Administrative division" section is a map that uses CSS tricks to add labels. The map without lables is not very useful and should be suppressed. Also, even if the labels were part of the image, viewing it out of context would arguably not make much sense, because it is already shown at full size. (This would be different if it was a detailed SVG or higher resolution map, like the shaded relief map further up in the article.)
  • In the "Religion" section there is a diagram. This particular diagram is made up using HTML & CSS, but for other simple SVG or raster diagrams having them in the gallery list would not make much sense.
  • The "See also" section has three icons for portal. These should not be included. This particular case could be solved with "class=metadata" or something similar, but this is not very intuitive as mentioned above.
  • The "External Links" section also has various icons and flags that do not belong in the viewer (and are already suppressed).
--Srittau (talk) 17:44, 19 April 2014 (UTC)Reply
Oh, another example from this very page: The "archive box" icon from the top of the page. --Srittau (talk) 17:45, 19 April 2014 (UTC)Reply

We can add another class besides metadata that disables MediaViewer for the contained images (there are some things like mixed HTML/image maps which are not going to work with MediaViewer but are not really metadata). Any suggestions about the name?

Srittau: changing the parser just so CSS classes can be set via wikisyntax would be the wrong approach, pretty sure we are not going to that. (You can use [[File:foo.png|link=File:foo.png|Flag of Fooland]] right now as a horrible hack to achieve the same effect, but no guarantees about that working in the future.) You can use templates to make the syntax somewhat more user-friendly, but really people should not mess with which images are displayed, unless they are authoring templates, in which case they probably won't be scared off by a CSS class. "Meta" images should not be included in the article's source code directly. --Tgr (WMF) (talk) 02:03, 25 April 2014 (UTC)Reply

  • Most icons, flags, etc are distinguished by being small - it's rare to see a non-content image which is >100px and equally rare to see a content image which is <100px. Would a simple size-based cutoff work for deciding what to put in the gallery view? Andrew Gray (talk) 11:51, 2 May 2014 (UTC)Reply
This was suggested at bug 64520. As I mentioned there, this might work most of the time, but there will always be exceptions, while marking up non-content images would be useful outside of MediaViewer as well. (Also, define non-content. Is the main image of Template:Evolutionary_biology (200px) content or not? Those type of >100px images, which belong to an article group but not a specific article, are not so uncommon.) --Tgr (WMF) (talk) 18:29, 2 May 2014 (UTC)Reply

Goes back to the top of the page...

edit

First off: this is a great feature, way easier than hitting "back" and waiting for it to load. But: when I'm about halfway down the page...and click on a picture...and look at it in media viewer...and close media viewer...it leaves me at the top of the page...so then I have to scroll all the way down again. This gets on my nerves. A lot. I'm no techie though, so don't ask me to help.

Thank you! Eman235 (talk) 07:19, 19 April 2014 (UTC)Reply

eh, ignore this...just noticed someone else saw it. Glad to know someone share my sentiments. Eman235 (talk) 07:20, 19 April 2014 (UTC)Reply

changes - hate 'em

edit

im afraid from changes, is there anyway for easy disable? thnx Yoav Nachtailer (talk)

Hi Yoav Nachtailer, we feel your pain. Change is scary -- for all of us. I personally think that becoming comfortable with change is our greatest challenge as a species -- now that everything is changing faster and faster. Fortunately, we have a great solution for you in this case: you can simply turn off this feature in the 'Appearances' tab of your preferences, then uncheck 'Enable media viewing experience'. Try it out and let us know if it makes you happier :) Fabrice Florin (WMF) (talk) 01:06, 24 April 2014 (UTC)Reply
Thanks from me too. I am indeed happier without Media Viewer. Change only for the sake of change is a not a reason, so please spare us the sarcasm. Many thanks.--Paracel63 (talk) 21:09, 27 April 2014 (UTC)Reply
Then why make changes to articles ? TheDJ (talk) 10:52, 28 April 2014 (UTC)Reply
thank you very much! Yoav Nachtailer (talk) 13:06, 24 April 2014 (UTC)Reply

Media Viewer Launches on More Pilot Sites

edit
 
Media Viewer lets you view images in larger size, for a more immersive experience.

Greetings!

I’m happy to announce that we just enabled Media Viewer by default on nine more pilot sites: Czech, Estonian, Finnish, Hebrew, Polish, Romanian, Thai, Slovak, and Vietnamese Wikipedias.

1. Overview
We’re releasing Media Viewer gradually, a few wikis at a time, to test it carefully before deploying to the next batch of sites. So far, the tool has been well received on our first pilot sites: Catalan, Hungarian and Korean Wikipedias, as well as on English Wikivoyage, as outlined below. Next Thursday, we plan to deploy to some of our first large wikis, including: Dutch, French, Japanese and Spanish Wikipedias. Learn more about this release.

2. Metrics
We’re now logging about 336,000 image views per day on a global basis, as shown on this graph. About half of these views are coming from the Hungarian Wikipedia, and the rest from Wikimedia Commons, English Wikipedia and other pilots. More metrics dashboards are available for selected sites on this page.

3. Performance
We are now tracking image load performance globally, and first results suggest that images take over a second to load on average (50th percentile), but can take up to 5 seconds when looking at worst case for most users (90th percentile), as shown in this graph. We’re also encouraged by early comparisons of the time it takes to open an image with Media Viewer versus on a Commons File, the current default: the mean load times for these two methods seem to be very close, on the order of 2-3 seconds on a cold cache, as shown in this preliminary graph.

4. Surveys
We are now running surveys in multiple languages, to validate whether or not this feature is useful to readers and editors alike. Overall response so far is generally favorable. Here are the current results:

  • English Survey: 64% find the tool useful, 12% don’t find it useful, 24% are not sure (50)
  • Hungarian Survey: 48% find the tool useful, 46% don’t find it useful, 5% are not sure (271)
  • Catalan Survey: 62% find the tool useful, 15% don’t find it useful, 23% are not sure (13)

We’re also starting new surveys in French, German and Portuguese. Here are links to live results and comments from these surveys.

5. Usability
For the past few months, we have been running a series of usability studies, with positive results. Testers are typically able to complete most common tasks successfully, and they have helped us find new ways to improve the user experience for features they found confusing. Here are the updated results of our usability tests.

6. Your feedback
How can we improve Media Viewer? Are there any critical issues that should be addressed for this first release? Please let us know what you think of this tool here on this discussion page. We’d also be grateful if you could take this quick survey, to let us know how Media Viewer works for you. It only takes a minute and means a lot to us :)

Many thanks to all the team and community members who are making this launch possible! Enjoy ... Fabrice Florin (WMF) (talk) 23:22, 24 April 2014 (UTC)Reply


New is not always better

edit

I was hoping we would stop programming for programming's sake. This image viewer is terrible and I noticed I couldn't view the pictures the way I wanted to straight off. The original display page contained data in a format I used frequently. I don't see any EXIF data now, I have to scroll to get what little extra information I can, and the image sizes to my screen the way the viewer wants - not the way I have my browser set. Please stop "updating" "features" just to say you are "new and improved" as this is not an improvement. Sometimes less is just less and not more. Mrcomputerwiz (talk) 01:09, 5 June 2014 (UTC)Reply


edit

The share button is a non-obvious place to place the link to the Commons page. We clicked everywhere before finding the link hidden there. And even after clicking the share button, we thought this link was not the link to the Commons page, just the raw jpg file. And we were also dumbfounded at first to not find a clickable link. Only after I copy-pasted the link I had the idea that the chain icon could be clickable... Very frustrating experience to search everywhere for a link that was just weeks before the direct link from the image.

All in all, the feature is maybe in need of user testing along the usual paths of users (my friends is used to go to a WP page, identify interesting images and then go and download them on Commons)

I see. Thanks for sharing what frustrated you about the experience. The design is not 100% final, so we'll see what happens there. Keegan (WMF) (talk) 05:25, 18 May 2014 (UTC)Reply

There are two links to the Commons file page: in top right corner of the scrollable metadata panel (in the part which is always visible - this link only appears when logged in), and in the right-side information column of the metadata panel (it even has a big logo and distinctive border and background to jump out more).

The share link has a different purpose, it goes to Commons but also opens MediaViewer there. It is really only meant for sharing the MediaViewer view of the image - basically it is a replacement for sharing the current URL that MediaViewer creates when you pop up an image over some article. Sharing that URL would be problematic, since the image could be removed from the article at any time, so the URL is not permanent - so we offer a link to the image's "home page" instead.

Also, MediaViewer tries to remove the need to go to the article page for really basic stuff like downloading the image - you can do that in the same menu which has the share link. --Tgr (WMF) (talk) 23:05, 18 May 2014 (UTC)Reply

This feature is very inconvenient for research where as much information as possible on each image is needed. Its relationship to Wikipedia, a valuable information source, should carry over as much as possible to images and media captioning. Because the new media feature is imposing itself (gradually, apparently, but out of the blue and very inconveniently for me)as a default, it discourages people who post images from telling as much as they could about the images, because the full information does not show in the viewer. In short, the viewer makes an information + image source into an image showcase like Flickr. But Flickr already exists. We do not need another one.

Another related disadvantage to the MediaViewer is that it does not offer the scaled images sizes of the old viewer. It is useful to be able to access and use images at lower resolution for some purposes, and high ones for others. The MediaViewer should include this option--- and all the information in the earlier mode of display. Until/unless it does, it is merely frustrating and useless for getting images for teaching or research. For those plummeted into it, there should be an easy-to-see OFF button. I hope we will always be able to have the option to turn it off.

How can I have data on all the languages of comment

edit

Some pictures are commented in various languages. For example this one. I can not see the comments in all languages with the new visioner. So I might add a comment in a language that already exists.

How can we solve that problem?

--Lucyin (talk) 11:14, 16 May 2014 (UTC)Reply

Lucyin, I'm not sure what you mean. I'm not seeing a description for the file in anything other than English, and I don't see commentary on the gallery placement. Could you please explain a bit more? Keegan (WMF) (talk) 05:24, 18 May 2014 (UTC)Reply

Why the captions are omitted?

edit

Well, I'll try to be constructive this time. I don't understand why the cutlines/captions are omitted. I mean, without them, the most of the images from an encyclopedia are meaningless, since they are used for improve the explications and not just for decoration. Besides, many of them are diagrams or pictures with numbered parts like this that must have a caption. ¿Why not to include them? Thanks. Albertojuanse (talk) 00:26, 26 April 2014 (UTC)Reply

+1. I noticed the same big problem. Most of all a serious lack into comparative galleries. --Salix (talk) 16:30, 27 April 2014 (UTC)Reply
They are only omitted on galleries (that bug has been fixed, but the fix has not been rolled out yet). If you do not see the caption for any image that is not inside a gallery, could you provide a link? --Tgr (WMF) (talk) 06:59, 28 April 2014 (UTC)Reply

No, I mean, this is not a bug report, Tgr. What I mean is that I tried the "beta" on esWiki and, when I clicked on an image, there was not the caption of the picture, the explanation of it. Of course, there was the file description and copyright mark, etc; but no the explication which is under the image in the "normal" MediaWiki view.

My point is that without these captions, the explanation of that image, this software is "useless" for a project like Wikipedia, in which the explanations/captations of the image are needed for understand it (maybe not for other proyects, of course, talking about Wikipedia). Thanks. Albertojuanse (talk) 15:20, 28 April 2014 (UTC)Reply

Albertojuanse: I think Tgr point was that the no-caption in galleries was a bug which has been fixed since.
Unless you feel (like Salix) that the caption should be displayed without scrolling down to the hidden metadata panel, which is tracked on bugzilla:64132. Does the bug report accurately describes what you are expecting? Jean-Fred (talk) 16:46, 28 April 2014 (UTC)Reply
¿Is it scrollable!!!!!? Then, sorry, Jean-Fred and Tgr, the captions are shown properly when you scroll it.
Then, you have to find a way for making people know that the page is scrollable!!! I have no even notice that, so I guess other people won't either. Thanks. Albertojuanse (talk) 11:32, 29 April 2014 (UTC)Reply

Media Viewer problems

edit

Another negative opinion: trying to download SVG file but instead of easy access there are only PNGs served by viewer. Not acceptable. Problem only to be solved via right clicking image, showing in new tab, editing href path - cut out 'thumb/' and parameters following original filename, hit enter, now you've got the SVG that is possible to download. 95.171.99.171 10:54, 25 May 2014 (UTC) And hate that I have to separately register on each Wikipedia PL/EN/.../Wiki Commons.......... Lack of basic functionality is the most irritating. 95.171.99.171 11:00, 25 May 2014 (UTC)Reply

Hi! My experience with Media Viewer has so far been mostly negative. Here are some points:

  • It presents a cleaner interface, but at the same time it hides a lot of valuable information from view.
  • It seems to have a very different interface compared to the normal Commons experience, which may be confusing.
  • I've witnessed at least two instances, where another user could not escape out of Media Viewer in an easy and straightforward manner (no menus etc visible).
  • It seems Media Viewer has gone default on some Wikipedias – including plwp. My preferred browser (Mozilla Camino 2.1.2) doesn't seem to be compatible with Media Viewer, and I'm not proficient enough in Polish to be able to deactivate Media Viewer in my plwp account. This is not good.

If any or all of these things could be addressed, I'd might be more positive to its implementation. But as for now it's a big no-no for me.--Paracel63 (talk) 12:28, 26 April 2014 (UTC)Reply

I now found the deactivation command info in the discussion above. Thanks for that.--Paracel63 (talk) 12:48, 26 April 2014 (UTC)Reply
BTW, there doesn't seem to be a way of deactivating Media Viewer "in advance"? Next week, I still want to be able to reach Commons, with my preferred brower, through any of these Wikipedias "Dutch, French, Japanese and Spanish". Best of wishes. :-)--Paracel63 (talk) 12:56, 26 April 2014 (UTC)