When searching for a flow page, the preview displayed in the search results only says "This talk page has been taken over by a Flow board.". Either it should show nothing, or should show an excerpt of the header (and nothing if there is no header). This also means that text searches probably don't work, but I don't know what to do about this.
The Core Features team has enabled Flow on this talk page.
- Please conduct testing at Talk:Sandbox, retaining this page for discussions and suggestions.
- If you find bugs, report in Bugzilla if you can, and here if you can't.
- Small view
- Collapsed view
- Full view
- The title input should have spellchecking enabled by default.
- The spinner that comes up when some ajaxing is happening should keep the width of the button it replaces, so the other buttons don't move about.
- If the preview isn't visible once it is loaded, the page should be scrolled up to it.
- When refreshing the preview, the old preview shouldn't be removed until the refresh is done, otherwise the textbox jumps twice. On that note, the resizing of the preview box should be animated so it isn't an instant and jarring jump.
- The preview box should represent how the comment will look when it's posted as best as it can. This includes making sure the content box is the same width (it currently has some padding and a border which makes it a bit smaller than it will actually be) and that the font colour is the same (it's black in the preview, but gray when posted). It'd also be good to have the background colour the same, but then the preview may not be separated enough from existing comments.
- Textboxes shouldn't have titles set on them, otherwise when you're moving your cursor over some text to modify it (or even just leaving your cursor over the textbox while you type), you get an annoying tooltip come up covering the text. The placeholder text is enough to tell the user what the textbox is for.
- The terms text under the textbox is just a bit too small. For me, increasing the width of the box it's in by a few percent allows the font size to be raised to the more readable 11 or 12px.
- A single newline should be replaced with a <br>, so it displays like it does in the textbox. I understand the reasoning for doing this for articles, but it's not necessary or expected in a comment. I don't know of any comment system or forum that doesn't display single newlines. (Obviously double newlines should still be divided into separate paragraphs as per usual.) But I suspect this will be too difficult to be worth doing because they share the same parser?
- Restore the usual resize handle so I can override the automatic resizing of the textbox. Personally, for a longer comment I'd prefer to have a smaller textbox so I can see the preview and the textbox on the screen at the same time. I don't see any harm in giving the user the option of control, which is usually present.
- Find uses for the large amount of blank space on the right of the screen that any standard sized monitor has. The most obvious thing would be displaying the preview there. (This of course should adapt to the size of the display, if there's not enough room to display the preview in the correct width, it should stay above the textbox.)
4 days ago Fri, 07 Mar 2014 05:22:10 GMT
Why not to allow 3rd, 4th, etc. level for messages, as in LiquidThreads?
If user A creates a post, B replies to A, A replies to B and C replies to A's first post, C's reply could be misinterpreted as a reply to A's second post. This is undesirable.
13 days ago Wed, 26 Feb 2014 03:12:27 GMT
Ricordisamoa: We want whatever we build to work across all the different kinds of devices that people use to access Wikipedia now and 5-10 years from now: desktop, laptop, tablet, phone (mobile phones currently represent ~20-30% of Wikipedia pageview traffic, and this number is steadily growing). Infinite levels of threading display very badly on smaller screens. We're testing 3 levels currently (reply to topic, reply to user, reply to user's reply) to see if this suffices for more complex back-and-forth discussions.
11 days ago Thu, 27 Feb 2014 22:25:22 GMT
Maryana (WMF): Can't you increase the width of the comment threads a bit? It's somewhat weird: Articles are much more dense in terms of the information contained yet they extend over the entire width of your screen, but discussion threads (here) only get roughly 60% of the normal width of a Wikipedia page.Show changes
9 days ago Sat, 01 Mar 2014 21:00:52 GMT
Maryana (WMF): While I agree with using an optimal reading width; with further nesting levels you run into the issue of the comment being less than the optimal width. I assume the reason for the first nesting level having a smaller font size was to solve this, however you won't be able to just keep lowering the font-size for additional nesting levels.
The easiest solution would be to allow nested comments to extend out further, however this would look pretty messy. So perhaps the solution is to meet it half way and extend the width to a bit greater than optimal, so nested comments are a bit closer to optimal?
4 days ago Fri, 07 Mar 2014 04:48:07 GMT
188.8.131.52: I mostly agree with your comment right there. Additionally, longer replies get more compressed in such a narrow width.
Since Maryana said it's at approximately 60% width right now, I'd just take a guess that 70%-80% would still look good, and meet half-way with the two opinions on the width.Show changes
4 days ago Fri, 07 Mar 2014 05:00:30 GMT
Flow users (or maybe sysops only) should be able to set a 'priority' on each thread, so other users would focus their attention on important discussions first, even if they are not the newest on their board.
13 days ago Tue, 25 Feb 2014 17:53:39 GMT
Ricordisamoa: So "Sticky posts", essentially? I'd support this feature, but I'm not sure how priority should be given. If anything, the post should be colored differently (or have some other differentiator) and collapsed by default as not to break the flow (heh) of the rest of the page. Especially if there's more than one.
13 days ago Wed, 26 Feb 2014 00:28:51 GMT
Ricordisamoa: They're planning on adding some "sorting methods" to the ordering of topics, so that we can reorder by "recent activity" vs "chronological".
They're also contemplating various ways meta-data could be applied to topics or posts (such as through the category system, or via a new #tag type system).
Adding these 2 features together, plus any other "sorting methods" that we can suggest and-are-possible, should result in us each being able to focus on different topics/threads, in the ways that we need. :)
13 days ago Wed, 26 Feb 2014 01:07:31 GMT
I was wondering if there were any previous suggestions to follow a specific thread to get notifications for it? I can follow an entire Talk page, but only using the Watchlist. I would like to be able to Follow/Subscribe to a topic (or thread? I suppose they're interchangeable in this case) and receive Echo notifications whenever a comment is added.
Preferably, regardless of how many comments there would only be one Echo Notification for each thread I'm subscribed to. Opening the Echo dialog would tell me how many responses there are, who wrote the most recent response, and/or how many new responses there are since I last viewed the topic.
e.g. "Subscribing to/Following" a Flow thread? on Talk:Flow has 4 new responses and 13 responses total.
This could undoubtedly be improved and changed to suit the most common needs of users, but I'd like to at least discuss the feature, as I feel that it's unfortunately lacking.
15 days ago Mon, 24 Feb 2014 00:08:26 GMT
Thanks Nicereddy. It's been mentioned a few times, and is on the to-do list, but this is a good description of a desired feature-set.
"Bundling" is how Echo defines its "many related changes merged into a single message", so I'll use that term.
Bundling Flow changes by-topic is a good idea, and something that they've already started to implement in our watchlist entries (not live on mediawiki.org yet. Work ongoing). It's not perfect yet, but it should demonstrate how we can get things that are better than the status quo.
How Flow changes get integrated with both our Echo notifications and our Watchlist entries, are something that will need ongoing tweaking and experimentation, as the scope/scale increases, and the possibilities-via-new-features expand. More suggestions appreciated. :)
13 days ago Tue, 25 Feb 2014 23:08:00 GMT
No one will ever be forced to use flow on their own usertalk page, right? Just checking. ~~~~
16 days ago Sat, 22 Feb 2014 13:39:46 GMT