I noticed that the preview card for w:en:Bohol displays the markup of the infobox template rather than the first sentence(s) of the article proper. Aside from the infobox contents including a relatively large number of sub-templates, I'm not immediately seeing anything too far out of the ordinary. I didn't want to try troubleshooting by testing on the live article, and I thought I'd check for answers here before taking this to a sandbox. Anyone have a sense of what's broken? Cheers.
Return to "Page Previews" page.
Reply to "Preview shows template code"
Reply to "Preview text too short (user feedback from en-wp Help Desk)"
Reply to "Empty page Previews"
Reply to "Text summaries are clipped awkwardly sometimes."
Reply to "Page preview feature requirements?"
Reply to "Suggestion: End Preview Text At End Of Sentence"
Reply to "Parentheses as part of title"
Reply to "Vandalized Page Previews - how to revert or edit?"
Reply to "Similar browser extensions or add-ons to be inspired by"
Reply to "Can't see the Page Preview enable/disable button in Appareance"
About this board
Page Previews solves the core problem of users opening multiple tabs to gain an understanding of a word in the context of the subject they are reading. Whenever a reader hovers over a link to another article, a short summary of the subject, including its graphical image, is provided to them so they can decide whether they need to visit that subject more fully before continuing the current subject.
Please give us feedback on your experience using this feature so we can change and improve it. Each language is welcome in this discussion!
You can read more about the feature here.
- All issues with potential work attached to them tracked here: https://phabricator.wikimedia.org/project/view/765/
Preview shows template code
Confirmed bug. Screenshot: https://i.postimg.cc/K8v834tg/image.png
Find a link to [[Bohol]] in the first sentence at w:en:Tagbilaran to test it.
I can't see what is wrong, either. @Niedzielski perhaps you can tell?
The template is in the page previews summary endpoint response, no surprise. It's my understanding that the summary endpoint uses Parsoid and it's in that too. I manually bisected the article's diffs (being mindful of possible caching and purging concerns) to see when it occurred and was able to narrow it down some, I think. My guess is T197523 which I've left a comment on. If you think it's a priority and you agree with the assessment, please consider awarding the task a token.
Preview text too short (user feedback from en-wp Help Desk)
[https://en.wikipedia.org/w/index.php?title=Wikipedia:Help_desk&oldid=945998562#New_page_preview_system Original post]. The complaint says (in summary) that the preview text will often look like "Foo is a game published in YEAR_I_DONT_CARE by COMPANY_I_DONT_CARE on PLATFORMS_I_DONT_CARE (...)" and so the information they want (summary of game story, etc.) is below the fold. There is not much we can do on the Wikipedia side unless we change radically how the lead is written, but maybe the settings (which currently contain only a activate/disable switch) could include a "max length of preview" setting. (I am not saying it is easy especially across various displays, I am just saying that some could find it useful, at the very least the person who complained.)
Empty page Previews
I am getting empty page previews if page starts from a heading. Is there any way to resolve it?
Can you give an example where starting from a heading is a good idea?
Let me give you an example. Every research article begins from an "Abstract". In academia, abstracts are compulsory. I want to publish a journal on mediawiki. Therefore, every article in my wiki will start from an "Abstract".
Hi there, I am having a similar issue. Can someone please help to resolve this? All my pages with a Header serving as the title show "..." in the preview instead of the article content. The only way I have been able to fix this, is to remove the header. I would rather not do this though- any suggestions?
Text summaries are clipped awkwardly sometimes.
Most times the hover cards do a good job of ending after an appropriate amount of content, but on longer excerpts text gets truncated, often abruptly. (Example: The link to the flow extension at the top of this talk page.) This is opposed to just ending at a sentence boundary.
This wouldn't be so bad if ellipses were at least appended to the text, but in either situation it badly triggers the zeigarnik effect. This leads to clicking on the page to finish reading the excerpt... and then you've left the page and lost your original reading context.
As a designer/copywriter/programmer, this just stuck out at me -- I don't know if it bothers anyone else. Overall though, I think hover cards are a great idea. The project page states that the goal of the feature is to provide readers with an excerpt so that they "can make the decision about whether they want to read the full article" or not, but it strikes me as being just as useful for getting a quick idea of what a term means. (It's kind of the idea pondered here.)
I have a couple other suggestions, but I want to turn those over in my head for a bit first. For most of the project though: looks good!
Connor, I completely agree with you, we should truncate sentences. Say we have to truncate after 250 characters. This would be very different for different languages. What counts as a character in Hindi is much less than an actual alphabet. So we are struggling a bit with this technical limitation.
Its a great insight that once the user lands on the target page, the transition is lost. I have some ideas, but would also like to hear of how we might be able to solve this.
I believe we have some language engineering folks who can help figure this out. Pau Giner?
Showing some partial content in a way that works well across multiple languages is a hard thing to do. Depending on how you want to deal with it, you may need to take into account how each language separate words, use a different line according to their script, or the very notion of "character" and how those are counted.
It would be useful to have a generic component in MediaWiki that let's you just show a given number of lines, or whichever content fits in a given space. This is something that the Language Team may consider to support in the future.
An alternative to cropping with an ellipsis, could be to make the last part of the text to fade out by applying a transparent-to-white gradient on top of it (covering the last line).
Regarding the continuity problem mentioned by Connor, that can be solved if when reaching the article though a hovercard, the first sentence of the article gets highlighted for a second (e.g., background could fade to grey and back to white again). In that way, the user could guess that the text is the same and continue reading where he/she left.
Breaking the sentence after a certain number of characters is not i18n safe. It can cause lot of issues with complex scripts. Complex scripts require grapheme boundary detection or word boundary detection for finding out sensible line break positions. That is defined in TR29 of unicode standard and very difficult for the context. Pau's suggestion about fading the last line looks good to me.
Santhosh.thottingal: I think you are making it a bit too complicated here. You are looking for solutions to fix an imperfection, but your workaround is also not perfect. Don't trade the one imperfection for another imperfection too easily.
TheDJ: I was just pointing out the i18n aspect. I did not propose any solution or workaround. Thanks.
As an example of somewhat awkward cropping, mousing over a link to https://en.wikipedia.org/wiki/Bernard_Zakheim gives "Bernard Zakheim, Apr.", presumably because it treats the period as a sentence termination rather than an abbreviation. Not the end of the world but something else to consider while improving this.
Page preview feature requirements?
Hi, are there any requirements (in size and dimensions) for images to be visible with page preview feature? I have updated logo of one page, but image is still not visible in page preview, only text, like before.
Suggestion: End Preview Text At End Of Sentence
IMHO, a much-needed improvement to the Page Preview feature would be to have it end at a complete sentence instead of at an arbitrary word limit. Here's an example for the entry Uffizi :
The Uffizi Gallery is a prominent art museum located adjacent to the Piazza della Signoria in the Historic Centre of Florence in the region of Tuscany, Italy. One of the most important Italian museums and the most visited, it is also one of the largest and best known in the world and holds a collection of priceless
This preview text would be so much better if it included the full sentence, like so:
The Uffizi Gallery is a prominent art museum located adjacent to the Piazza della Signoria in the Historic Centre of Florence in the region of Tuscany, Italy. One of the most important Italian museums and the most visited, it is also one of the largest and best known in the world and holds a collection of priceless works, particularly from the period of the Italian Renaissance.
Could you please pass on this suggestion to the developers? Thanks.
That sounds like a nice idea when you assume that you will be gaining the end of the sentence. However in reality there's going to be a maximum preview text length, which essentially changes this into a proposal to drop the first half of any sentence that would be incomplete. When viewed that way, displaying the partial sentence is almost surely preferable to not displaying it.
Thanks for the reply. I agree with your assessment of the issue, and I had thought about it too. The reason I still believe it's an issue though is because I observed that a large part of the time, the incomplete sentence actually caused me to open the link in a new tab to see what the next word was, thus defeating the very purpose of the preview. If many other users have also experienced this same behaviour, it might be worth fixing it.
To explain better, considering the example provided in my original comment, the preview ends with "holds a collection of priceless", which immediately begs the question: priceless what? Whereas, using the rule of only including complete sentences but not crossing the word limit, the preview would reduce to:
The Uffizi Gallery is a prominent art museum located adjacent to the Piazza della Signoria in the Historic Centre of Florence in the region of Tuscany, Italy.
IMHO, this brief extract fully serves the function of a link preview, without the added "discomfort" of having a broken sentence. An ideal compromise might be to add a setting to "Include full sentences only" in the page preview preferences, but I'm guessing this might unnecessarily complicate matters.
Essentially, I suppose it boils down to seeing which option more users prefer: a shorter but complete paragraph, or a longer but broken one?
Completely agree. I've been using the link preview gadget for years, and I don't recall this being an issue there.
With this new implementation we get cut off in the middle of the sentence, with the text just fading out. The reaction is to try and scroll or to try and find the 'expand' link that will complete the sentence - basically to try and get the rest of the sentence to appear. As per previous poster, this kind of defeats the point of the preview, if you need to click through to finish the sentence.
I really appreciate the design work that has gone into this, but it nevertheless feels like a step backwards, due to this issue. Looks pretty, works less well.
Please take a look at what the previous gadget did, because that worked well.
Parentheses as part of title
I'm sure this has been mentioned before, but what about article titles which contain parentheses that actually are part of the name of the subject? The page preview seems to work with chemical elements that have parentheses in the title, but looking at the preview for Brandy (You're a Fine Girl) leaves out the remainder of the song title which is in parentheses.
I think this has been discussed previously but I'm not sure what the current thoughts are on it. I've opened a ticket for discussion with the maintainers: T226323.
Currently anything in parentheses is hidden in the preview, but I think anything in bold should be shown.
Vandalized Page Previews - how to revert or edit?
I'm not sure where Page Previews pull their content from - I've found one this morning that differs wildly from the article it links. On the 2017 Honduras General Election page (link A, below), under the Supranational bodies header, when you hover over "Organization of American States", the preview text reads:
The Organization of American States, or the OAS or OEA, is a continental organization that serves to control American puppet states in the Americas. Headquartered in the United States capital Washington, D.C., the OAS's members are the 35 independent states of the Americas.
This is not an objective or factual statement, and differs wildly from the article that the OAS link leads to. The word "puppet" appears nowhere in the article source - which was where I went first in my attempt to find and revert the vandalism.
The previews feature is great, but I really hope that it is refined so that vandalism is easier to revert/address in the future.
For some reason the vandalized version remained as the active version in the page-preview cache for over 17 hours. I preformed a purge on the affected page which successfully cleared out the vandalism.
I'm not an expert on the caching, but one of the devs might want to look into why a few seconds of vandalism got stuck in the cache for so long. Is it possible the two edits were asynchronously processed in the wrong order? It would be bad if the software didn't spot something like that. A swift revert like this tends to be a significant red flag for blatant vandalism.
P.S. 126.96.36.199 thanks for the report. Any edit to Organization of American States would have fixed it. It can also be fixed by purging the page, adding ?action=purge at the end of the OAS address and loading it. Like this: https://en.wikipedia.org/wiki/Organization_of_American_States?action=purge
This problem still exists. The preview for Angolan Civil War is vandalized, but I cannot find the text anywhere in the article. It's really aggravating.
Similar browser extensions or add-ons to be inspired by
I'm moving these here, from the project page where I originally listed them. Feel free to edit this to add any you find.
- No endorsement of a particular extension is implied.
Browser extensions/addons that show mouseover popups within Wikipedia
- wikipedia plus
- wikipedia quick hints
- wikipedia smart links
- wiki it
- LiveWiki (github)
- wikipedia peek
- wikipeeks for wikipedia
- wikipedia hover
- wiki on speed
Browser extensions/addons that show Wikipedia/Wiktionary content at any external site
Full library for embedding in any web page
There are similar tools like this Page Previews feature, however that shouldn't stop our community from making ours. Having one official tool providing the best features in a simple way for everyone is a great idea which doesn't need installing browser extensions.
Listing the other extensions and add-ons is useful because we can review their design and features to improve our version.
Yup, that's exactly why I started/researched the list. To show how popular the idea was (proving we ought to implement something) and to glean good ideas/designs from. :-)
Think this means this feature really needs to be globally rolled out to non-registered users then... Maybe leave as an option for registered users though because some prefer third party gadgets like Popups on english that give you way more details (for editors)
- To EoRdE6: I agree that this feature would good for everyone outside beta testing (it is a tool made by many others), however this shouldn't happen too soon because it needs to be finished (main problems fixed, features added). Also an option for users to disable it on their account could be a good idea but it would be better to make Page Previews/Hovercards have the popular features of other third party tools so users would use our official tool.
My issue with that is that editors still have very different requirements to readers therefore a reader centric tool will never function for editors... Third party tools allow editors to view page history and editors and block logs and protection and tons more all from the pop-up. It's messy and ugly but for editors it's useful. Readers have no use for that information so I would support giving them this basic version that is currently available...
- To EoRdE6: I see your point but we could have these editor only stats in Page Previews/Hovercards as opt-in features enabled on users' settings pages which could get some editors to use our tool instead of competitors' ones to keep ours supported and popular.
There is also a library that can be embedded in web pages, AnandChowdhary/hovercard. (Have not tested.)
Can't see the Page Preview enable/disable button in Appareance
...simply does not exist the Reading Section in my Special:Preferences under Appearance tab.
This is my configuration:
These are my available/enabled Skins:
|Metrolook||6.0 (930bc3c)13:56, 17 December 2016||GPL-2.0-or-later||ENABLED||immewnity, Paladox, Craig Davison and lagleki|
|MinervaNeue||– (e1c3fb6)15:00, 16 October 2018||GPL-2.0-or-later||A responsive mobile first skin||Readers Web Team, Bahodir Mansurov, Joaquin Hernandez, Jon Robson, Juliusz Gonera, Ryan Kaldari, Florian Schmidt and Sam Smith|
|MonoBook||–||GPL-2.0-or-later||The classic MediaWiki skin since 2004, named after the black-and-white photo of a book in the page background||Gabriel Wicke, Isarra Yos and others|
|Timeless||0.8.1||GPL-2.0-or-later||A timeless skin designed after the Winter prototype by Brandon Harris, and various styles by the Wikimedia Foundation||Isarra Yos|
|Vector||–||GPL-2.0-or-later||Modern version of MonoBook with fresh look and many usability improvements||Trevor Parscal, Roan Kattouw and others|