Talk:Flow

Jump to: navigation, search

The Collaboration team has enabled Flow on this talk page.



Previous feedback is on Talk:Flow Portal/Archive2 (using old Liquid Threads), and on our labs server.

 
Bennylin (talkcontribs)

TOC "Browse topics" behavior is rather wacky, I would say.

On the top of the page, (when clicked) it would display in the order of edit (newest at the bottom), while the threads itself is in reverse order (newest at the top). If it stop at that I would not complain. But then (while the TOC is open) when I scroll to the bottom, suddenly the TOC changed its behaviour and reordered everything in reverse (newest, current section at the top), which suddenly disorient me and while I understand the intention of the devs, I wouldn't be able to get accustomed to that.

Plus, the TOC is blocking the view, while about 40% space in the right hand side of the screen is left empty (I'm using monobook btw, if that's matter). Wouldn't it be better to put the TOC on the right?

Steps: 1. Go to the top of the page 2. Click "Browse topics" (TOC) 3. Scroll to the bottom of the TOC 4. While the TOC is opened, scroll down the page a little bit (probably until the next section or two), until the TOC flipped, the TOC is suddenly scrolled to the top of the TOC 5. Scroll up again, and it's magically flipped again Repeat 4 and 5 to get yourself dizzy. Which way is up? Which way is down?

Mattflaschen (WMF) (talkcontribs)

There are two possible orders for the board, "Newest topics" (the topics that were *started* most recently) and "Recently active topics" (the topics that had *activity* most recently, anything from being started, to a reply, etc.). You can change this in the top right (next to Browse topics).

Note, neither neither of these are meant to have newest at the bottom. Either the newest topic is at the top, or the most recently active topic is at the top.

However, the TOC and board should always use the same order. Note that when you scroll the page, the TOC also scrolls at the same time, showing you where you are in the board. However, you can still scroll wherever you want in the TOC manually as well.

If the order really is inconsistent, that's a bug. To help us track that down, can you tell us:

1. What board does it happen on? 2. Which order are you using? 3. What are the first 3 topics of the page, and first 3 of the TOC? 4. When did you do this test?

Also note that if someone changes the board in the meantime, that may lead to some minor discrepancies as new topics are loaded (pagination, essentially). This will not lead to a full-scale flip, though.

Reply to "Wacky TOC"
Bennylin (talkcontribs)

Please return the hotkey Alt+Shift+"S" for Saving, pretty please, with cherry on the top.

(while you do that, you could do Alt+Shift+"P" also for Preview, but that's not as important as the first; currently Alt+Shift+"P" tries to show the printable view of the page instead)

Mattflaschen (WMF) (talkcontribs)

Thanks for the suggestion. Filed as phab:T90512.

Reply to "Just one small request"
Stephan Kulla (talkcontribs)

I coincidentally found this project and and I want to say "Thanks" for the work you already have done. I am looking forward to the day the Flow extension will be enabled at German Wikibooks where I mostly work. Good job!

Mattflaschen (WMF) (talkcontribs)

Thanks for the feedback. We are currently rolling out gradually to smaller wikis, so if you're interested, keep in touch.

In addition to this page, we have an IRC channel ( #wikimedia-collaborationconnect) and a public mailing list.

Reply to "Thanks for this project"
106.37.8.245 (talkcontribs)

Is there any way to use flow in 1.24.1?

Mattflaschen (WMF) (talkcontribs)

For master of Flow, you should use core's master.

I have not tested the REL1_24 branch of Flow with core 1.24.1. It may work, but if so, note no new features will be added to that branch.

See Special:ExtensionDistributor/Flow .

Reply to "1.24.1"
-revi (talkcontribs)

I tried to change header on this wiki but it gave the result like this: Exception Caught: Parser only supports wikitext to HTML conversion.

Is it problem of the instance running this wiki or is it flow bug?

ps. I'm not a sysadmin on this wiki.

Quiddity (WMF) (talkcontribs)

Hmm. Possibly because Parsoid isn't installed? (according to http://nuriwiki.net/Gnat/index.php/Special:Version )

In case it gets fixed in the meantime, here's a description for future reference: If we click the edit-header icon it results in this error

But I'll ask a dev to take a look.

Superm401 (talkcontribs)

Yeah, I think it's running in the non-Parsoid configuration. (In addition to what Quiddity said, there are no data-parsoid attributes).

This is currently allowed, but not nearly as well tested. We're going to start requiring Parsoid (see phab:T88147 and phab:T88908.

If the sysadmin contacts us, we may be able to follow up on migration to that configuration.

Mattflaschen (WMF) (talkcontribs)

Sorry, I meant to post that with my staff account.

Reply to "Problem on non-wmf site"

Upon posting a reply, all comments in a thread appear to have been posted "45 years ago"

3
Gparyani (talkcontribs)

When viewing a Flow thread, the times of posting for all the comments of that thread appear to have been posted when they have actually been posted ("a day ago", "3 days ago", etc.). However, when adding a new comment to that thread, all the comments suddenly change to appear as though they were posted "45 years ago". This only affects the thread on which the comment was posted on; the other threads on the page remain unaffected. Refreshing the page fixes the problem and causes the times ago to display correctly.

Using Internet Explorer 11 on Windows 8.1.

193.134.216.2 (talkcontribs)

Sounds like a null timestamp. 45 years ago is January 1st 1970, time 0 in unix timestamps.

Quiddity (WMF) (talkcontribs)

Sorry for the delayed reply. The developers have been working on it at phab:T86852.

Reply to "Upon posting a reply, all comments in a thread appear to have been posted "45 years ago""
Subfader (talkcontribs)

The hover actions shouldn't pop up immediately on mouseover. This way it often accidentaly opens on scrolling / navigating over the page.

Add some delay. Not sure what is good, maybe 100 ms. Google may know.

Reply to "Add some delay to the hover actions"
Gryllida (talkcontribs)

I would like to ask about progress in this area.

Reply to "converting stuff"
Nirmos (talkcontribs)

Hi. Can you activate Flow on sv:User talk:Nirmos?

Quiddity (WMF) (talkcontribs)

Hi, they're currently only activating Flow on new wikis (and pages) very slowly, in order to concentrate on a manageable quantity of features-in-development, and bugs to be examined, at a time. Thanks for your interest though! If you add your name to the (very low frequency, but overdue for a new update) newsletter list at w:Wikipedia:Flow/Newsletter#At other Wikimedia locations, you'll find out when there are new volunteer-locations being looked for, or new features being released. Hope that helps.

Reply to "Activate on sv:User talk:Nirmos"
DannyH (WMF) (talkcontribs)

We're releasing a new Flow feature today on mediawiki -- a Table of Contents, which is designed to help people browse and navigate around a Flow board.

As you scroll down on a Flow board, you'll see a persistent header that gives you access to the Table of Contents, wherever you are on the page. You can scroll around using the Table of Contents, and hop quickly from one topic to another.

The current feature is version 1 -- there are a few more tweaks that we want to make, so there will be a v2 coming. This is also a milestone on the road to Search -- we're going to build the feature to search on a Flow board on top of the ToC feature.

It's going live here a little later today. I'm looking forward to hearing what you all think of it!

Whatamidoing (WMF) (talkcontribs)

It's pretty subtle. It took me a moment to realize that it was actually there. I was expecting to see (without needing to click on anything) an actual list, and therefore something that displayed more than one line of text (by default).

I JethroBT (talkcontribs)

Yeah, I'm in agreement here that it would have taken me some time to notice it without the announcement. I understand the choice that the list should be clicked on because the TOC loads all topics, and it wouldn't be feasible to display them all at once and push down the rest of the page.

Hey here's an idea. I remember when I opened up the TOC, it covered up the comments on the page. Not a big deal, perhaps, but is there any chance the TOC might be put over in that white space over on the right side there? One benefit to doing this is that opening the TOC would cover up less or none of the comments on the left side of the frame. It might also help it pop-out a little more.

DannyH (WMF) (talkcontribs)

Yeah, we started with the idea that the ToC would be on the right. The idea that won me over to this version is the header changing as you scroll through, to reflect the thread that you're currently on. But if people don't see it, then that's definitely a problem we'll need to solve.

We're doing some user testing late next week on the ToC and a prototype for Search, and one of the basic things we're testing for the ToC is if people actually notice it and use it. :) The tests will be with people who are familiar with wiki talk pages (either reading or contributing to them), so they won't be brand-new newbies. If we see people completely missing the ToC, then we will definitely take steps.

Diego Moya (talkcontribs)

The problem I see with the new ToC design is that it doesn't even look clickable at all.

If people doesn't see it, a first step to test before recovering the "floating ToC on the right" may be to show it expanded by default when the page is scrolled to the top, showing a preview of the first (last) 6-8 topics and a "browse all" link that unfolds the whole pop-up. Scrolling down would fold the box to its current one-line-tall, current-title behavior.

Painting it blue (the color of links) instead of the current grey may also help.

I JethroBT (talkcontribs)

Hey DannyH (WMF). I did a little playing around with it over the last 10 minutes or so. I like how I can CTRL-F through the topics once I've opened it up if I know the topic name and don't want to scroll down through all of it. I also like that even if I haven't loaded the entire page, it will still bring me to a topic that's been well-buried at the bottom of list. I did notice that it takes slightly longer (due to the loading) in this case, but I think that's OK.

I did notice something a little strange-- when scrolling through the list with my mouse wheel (Mouse button 3, it sometimes called), I did notice that sometimes it will scroll the through topic list, but sometimes it would switch to scrolling on the background window. Not sure if this is an artifact of monobook or not (which I am using). I'm going to check real fast with vector.

I JethroBT (talkcontribs)

Hm. Well, I can reproduce the same scrolling issue in vector, but it's kind of hard to describe in words. There seems be some interval of loading time for the topic list after it is visible where the cursor is confused about what part of the screen it is focused on. If you move your mouse around a bit over the topic list, however, the problem appears to fix itself and scrolling is squarely on the topic list rather than the talk page.

Erik Moeller (WMF) (talkcontribs)

Yes, I can repro that scrolling issue in chrome as well.

DannyH (WMF) (talkcontribs)

Oh, thanks for the report. I know that there's been a scrolling issue when it reaches the bottom of the list and there's nowhere else to scroll to -- but it sounds like you're having a different problem. It's happening for you before you hit the end of the list?

I JethroBT (talkcontribs)

Correct, I can produce the error immediately after I opened it up.

DannyH (WMF) (talkcontribs)

Yeah, I can see it in Chrome. It's not happening in Firefox.

I filed a Phabricator ticket for it -- we'll take care of it. Thanks!

https://phabricator.wikimedia.org/T87041

Erik Moeller (WMF) (talkcontribs)

Great to see this live.

Small thing: I find the alignment between the sort order ("Newest topics") and the TOC confusing. It makes it look like I can sort the TOC.

DannyH (WMF) (talkcontribs)

Yeah, I agree it's a little confusing. That's something we'll change when we build the Search feature -- Search and ToC will work together as part of the same bar, and the sort order will be in a more obviously separate place.

Diego Moya (talkcontribs)

Congratulations for the good work. I've been advocating for a table of contents in Flow and following its design iterations from afar, and the results are fairly reasonable. It's a simple and non-intrusive feature that gets the work done, which is something quite difficult to achieve.

I've found a case of a behavior that is not intuitive. After jumping to a topic way down in the middle of the board, scrolling down does the right thing and shows the next topic; but scrolling up triggers a loading animation (so far so good), and when it ends, it jumps to the first topic in the batch of new topics. This is quite surprising, as the expected behavior is to show the end of topic right above the one where I jumped first.

For example, if I jump to "WIBNI infinite scrolling" and scroll up, I'd expect to see the end of "Have bugs been fixed?" which is the immediately previous one, and instead the screen flickers and the scroll bar jumps to the totally unrelated "Topic appears two times".

DannyH (WMF) (talkcontribs)

Yes, that's one of the pieces we want to improve for v2. The board loads topics in batches of ten, but we wanted people to be able to jump quickly to the topic that you choose in the table of contents. So we load the topic that you jumped to, but if you scroll up from there, then we have to load another batch.

In that situation, it should leave you at the bottom of the newly-loaded topics, so that it feels like you're still in the same place on the board. The current version pops you up to the top of the new set, which feels disjointed, like you said. We'll be working on this over the next few weeks.

I'm glad you mentioned it -- it was one of those pieces that made us say, "When we work on this, is anyone going to notice or care?" It's good to know that you did, thanks. :)

Reply to "New feature: Table of Contents"