Talk:Structured Discussions

Jump to navigation Jump to search

About this board

Structured discussions (Flow) is used on this page (documentation).

You can leave your message in any language, but answers will be made in English (or your language if we speak it).

Exception caught when starting a new topic

7
Summary last edited by PlavorSeol 14:45, 2 September 2018 23 days ago

SQLite syntax problem, which reported to phabricator

PlavorSeol (talkcontribs)
Trizek (WMF) (talkcontribs)

Hello

You mean on a non-Wikimedia Foundation hosted wiki?

PlavorSeol (talkcontribs)
Framawiki (talkcontribs)

Nothing in log files ?

PlavorSeol (talkcontribs)

Which log file?

Hoto Cocoa (talkcontribs)
PlavorSeol (talkcontribs)

I found this in log file:

[exception] [e66a958595cd23350b3269c9] /plavorexitbeta/api.php   Flow\Exception\InvalidDataException from line 253 of C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Collection\AbstractCollection.php: Invalid workflow: ugvzzs70cj48wj9t

#0 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Collection\AbstractCollection.php(238): Flow\Collection\AbstractCollection->getWorkflow()

#1 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Model\AbstractRevision.php(413): Flow\Collection\AbstractCollection->getTitle()

#2 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\Listener\ReferenceRecorder.php(249): Flow\Model\AbstractRevision->getContent(string)

#3 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\Listener\ReferenceRecorder.php(115): Flow\Data\Listener\ReferenceRecorder->getReferencesFromRevisionContent(Flow\Model\Workflow, Flow\Model\PostRevision, Flow\Model\PostRevision)

#4 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\Listener\ReferenceRecorder.php(82): Flow\Data\Listener\ReferenceRecorder->calculateChangesFromExisting(Flow\Model\Workflow, Flow\Model\PostRevision)

#5 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\ObjectManager.php(264): Flow\Data\Listener\ReferenceRecorder->onAfterInsert(Flow\Model\PostRevision, array, array)

#6 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\ObjectManager.php(173): Flow\Data\ObjectManager->insert(array, array)

#7 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\ObjectManager.php(146): Flow\Data\ObjectManager->multiPut(array, array)

#8 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Data\ManagerGroup.php(80): Flow\Data\ObjectManager->put(Flow\Model\PostRevision, array)

#9 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Block\TopicListBlock.php(178): Flow\Data\ManagerGroup->put(Flow\Model\PostRevision, array)

#10 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\SubmissionHandler.php(150): Flow\Block\TopicListBlock->commit()
#11 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\WorkflowLoader.php(66): Flow\SubmissionHandler->commit(Flow\Model\Workflow, array)

#12 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Api\ApiFlowBasePost.php(35): Flow\WorkflowLoader->commit(array)

#13 C:\inetpub\wwwroot\plavorexitbeta\extensions\Flow\includes\Api\ApiFlow.php(98): Flow\Api\ApiFlowBasePost->execute()

#14 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(1584): Flow\Api\ApiFlow->execute()

#15 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(535): ApiMain->executeAction()

#16 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(506): ApiMain->executeActionWithErrorHandling()

#17 C:\inetpub\wwwroot\plavorexitbeta\api.php(83): ApiMain->execute()

#18 {main}

ApiMain::setCacheMode: setting cache mode private

[Mime] MimeAnalyzer::loadFiles: loading mime types from C:\inetpub\wwwroot\plavorexitbeta\includes/libs/mime/mime.types

[Mime] MimeAnalyzer::loadFiles: loading mime info from C:\inetpub\wwwroot\plavorexitbeta\includes/libs/mime/mime.info

[error] [e66a958595cd23350b3269c9] /plavorexitbeta/api.php   ErrorException from line 100 of C:\inetpub\wwwroot\plavorexitbeta\includes\libs\HttpStatus.php: PHP Warning: Unknown HTTP status code invalid-workflow

#0 [internal function]: MWExceptionHandler::handleError(integer, string, string, integer, array)

#1 C:\inetpub\wwwroot\plavorexitbeta\includes\libs\HttpStatus.php(100): trigger_error(string, integer)

#2 C:\inetpub\wwwroot\plavorexitbeta\includes\WebResponse.php(106): HttpStatus::header(string)

#3 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiFormatBase.php(181): WebResponse->statusHeader(string)

#4 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(1808): ApiFormatBase->setHttpStatus(string)

#5 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(600): ApiMain->printResult(string)

#6 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(544): ApiMain->handleException(Flow\Exception\InvalidDataException)

#7 C:\inetpub\wwwroot\plavorexitbeta\includes\api\ApiMain.php(506): ApiMain->executeActionWithErrorHandling()

#8 C:\inetpub\wwwroot\plavorexitbeta\api.php(83): ApiMain->execute()

#9 {main}

MediaWiki::preOutputCommit: primary transaction round committed

MediaWiki::preOutputCommit: pre-send deferred updates completed

MediaWiki::preOutputCommit: LBFactory shutdown completed

[cookie] ''(Hidden)''

[cookie] ''(Hidden)''

Request ended normally

[session] Saving all sessions on shutdown

[DBConnection] Wikimedia\Rdbms\{closure}: closing connection to database ''.

Error in topic deletion and slow update

9
Sokote zaman (talkcontribs)

Hello

This is my system profile and my wiki:

محصول     نسخه

MediaWiki:    1.31.0 (b9cc61f)

PHP:        7.2.7-0ubuntu0.18.04.2 (fpm-fcgi)

MariaDB:    10.1.34-MariaDB-0ubuntu0.18.04.1

ICU:        60.2

ubintu 18.04 x64

LocalSettings.php profile:

wfLoadExtension( 'Flow' );

$wgNamespaceContentModels[NS_TALK] = 'flow-board';

$wgNamespaceContentModels[NS_USER_TALK] = 'flow-board';

$wgGroupPermissions['write']['flow-create-board'] = true;

$wgFlowHelpPage    = '//www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:Flow';

$wgFlowCluster = false;

$wgFlowUseMemcache = false;

$wgFlowEventLogging = false;

$wgFlowDefaultWikiDb = false;

$wgFlowExternalStore = false;

$wgFlowParsoidForwardCookies = false;

$wgFlowServerCompileTemplates = false;

$wgFlowSearchEnabled = true;

$wgFlowParsoidURL = "null";

$wgFlowContentFormat = 'html';

$wgFlowParsoidPrefix = "null";

$wgFlowParsoidTimeout = "null";

$wgFlowDefaultWorkflow = "discussion";

$wgFlowSearchServers = array( 'localhost' );

$wgFlowEditorList = array( 'visualeditor', 'wikitext' );

$wgFlowAbuseFilterGroup = 'flow';

$wgFlowCoreActionWhitelist = array( 'info', 'protect', 'unprotect', 'unwatch', 'watch', 'history', 'wikilove', 'move', 'delete' );

$wgFlowMaxLimit = "100";

$wgFlowAjaxTimeout = "30";

$wgFlowDefaultLimit = "10";

$wgFlowCacheVersion = "4.7";

$wgFlowMaxMentionCount = "100";

$wgFlowMaxThreadingDepth = "8";

$wgFlowCacheTime = "60 * 60 * 24 * 3";

$wgFlowAbuseFilterEmergencyDisableCount = "50";

$wgFlowAbuseFilterEmergencyDisableThreshold ="0.10";

$wgFlowAbuseFilterEmergencyDisableAge = "86400"; // One day.

My question is: Why to eliminate an issue with an error: An error occurred while contacting the server.         ??????????

And when I cancel the removal operation, I'm surprised to find that the issue has been removed!!!!!!!!۱

Why the flow is slow?

Why is the visual editor gadget low? Only bold and italic is available ???

please guide me

Thanks

Trizek (WMF) (talkcontribs)

Why to eliminate an issue with an error: An error occurred while contacting the server. And when I cancel the removal operation, I'm surprised to find that the issue has been removed!!!!!!!!۱

Where do you have that problem?

Why the flow is slow?

It is not supposed to be. Do you have that issue when you're not logged-in?

Why is the visual editor gadget low? Only bold and italic is available ???

Bold, italic and more. You can also use any visual editor shortcut.

Sokote zaman (talkcontribs)

Meanwhile, my wiki does not have more buttons

Sokote zaman (talkcontribs)

f I delete the settings below, it will work without a problem. With this setting, the wiki will be slowed down and the conversation will be delayed....:::

$wgFlowHelpPage    = '//www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:Flow';

$wgFlowCluster = false;

$wgFlowUseMemcache = false;

$wgFlowEventLogging = false;

$wgFlowDefaultWikiDb = false;

$wgFlowExternalStore = false;

$wgFlowParsoidForwardCookies = false;

$wgFlowServerCompileTemplates = false;

$wgFlowSearchEnabled = true;

$wgFlowParsoidURL = "null";

$wgFlowContentFormat = 'html';

$wgFlowParsoidPrefix = "null";

$wgFlowParsoidTimeout = "null";

$wgFlowDefaultWorkflow = "discussion";

$wgFlowSearchServers = array( 'localhost' );

$wgFlowEditorList = array( 'visualeditor', 'wikitext' );

$wgFlowAbuseFilterGroup = 'flow';

$wgFlowCoreActionWhitelist = array( 'info', 'protect', 'unprotect', 'unwatch', 'watch', 'history', 'wikilove', 'move', 'delete' );

$wgFlowMaxLimit = "100";

$wgFlowAjaxTimeout = "30";

$wgFlowDefaultLimit = "10";

$wgFlowCacheVersion = "4.7";

$wgFlowMaxMentionCount = "100";

$wgFlowMaxThreadingDepth = "8";

$wgFlowCacheTime = "60 * 60 * 24 * 3";

$wgFlowAbuseFilterEmergencyDisableCount = "50";

$wgFlowAbuseFilterEmergencyDisableThreshold ="0.10";

$wgFlowAbuseFilterEmergencyDisableAge = "86400"; // One day.

This post was hidden by Sokote zaman (history)
Trizek (WMF) (talkcontribs)

Is your wiki a Wikimedia Foundation hosted wiki?

Sokote zaman (talkcontribs)

Yes, it's for mediawiki

MediaWiki: 1.31.0 (b9cc61f)

PHP: 7.2.7-0ubuntu0.18.04.2 (fpm-fcgi)

MariaDB: 10.1.34-MariaDB-0ubuntu0.18.04.1

ICU: 60.2

ubintu 18.04 x64

Trizek (WMF) (talkcontribs)

Is it your personal website?

Sokote zaman (talkcontribs)

Yes

Reply to "Error in topic deletion and slow update"

Ways to easily revert to unconstructive edits

4
George Ho (talkcontribs)

The Structured Discussions system is prone to unconstructive edits, like some seen here and there. I don't get why there is no "undo" option. The way I reverted those edits on Structured Discussions is not as convenient as on other project. Are there more convenient ways to revert such edits?

Trizek (WMF) (talkcontribs)

Thank you for taking care of those edits. There is usually an "undo" button, but I can't find it on the examples you gave me. I'll do more tests.

Improvements needed to Structured Discussions on that area have been documented, especially the ones concerning how to deal with history and moderation.

George Ho (talkcontribs)
Trizek (WMF) (talkcontribs)

Thanks, I've updated it with your feedback.

Reply to "Ways to easily revert to unconstructive edits"

How much money was wasted on this failed project?

10
The Quixotic Potato (talkcontribs)

Has anyone published a guesstimate of the amount of money that was wasted on this terrible idea?

Sänger (talkcontribs)

Look at this thread, they actively deny VE on talk pages, probably to push this failed bullshit Flow. This is just a weask forum impersonation, without any of the flexibilities the current system has. Dumbed down beyond recognition to increase the facebookisation.

The Quixotic Potato (talkcontribs)
Sänger (talkcontribs)

They did a so-called Flow satisfaction survey, but under completely bogus assumptions: They artificially created a rift between wysiwyg and proper talk pages, although that's just a decision by the WMF not to implement it on talk pages, without real merit. They based a lot of the questions ion this bogus assumption, so the answers are just rubbish. Of course asked this way: old fashioned editor or wysiwyg-editor, and the second only possible with flow, you'll get the answers, that were intended by this: I want wysiwyg, so I have to want Flow.

It's this complete dishonesty about projects like Flow that's so frustrating. They seem to do anything, including blatant lies, to push their pet projects against the community. Grüße vom Sänger ♫(Reden) 17:28, 22 January 2017 (UTC)

The Quixotic Potato (talkcontribs)

The WMF should not be allowed to use surveys because they are using them to get the result they want instead of trying to determine what the consensus is.

They use surveys on external servers, and they only invite a small group of people, because they know the majority disagrees with them. We should have an RfC on en.wiki instead.

Sänger (talkcontribs)

There was an RfC on enWP already, and Flow was planted in the bin: T148611.

They will probably get the same results on deWP, if they dare to introduce this piece of junk there anywhere.

Bur as you see on this baloney "survey", they don't like real feedback based on facts, they live on those kind of alternative facts like the groper in chief and his lackeys. Grüße vom Sänger ♫(Reden) 14:43, 23 January 2017 (UTC)

Sänger (talkcontribs)

Thanks, He7d3r, for fixing my wrong syntax. I tried to do this the usual way, via the thanks link in the version history, but thanks to Flow that's impossible. So I had to use this quite elaborate way ;) Grüße vom Sänger ♫(Reden) 08:38, 25 January 2017 (UTC)

The Quixotic Potato (talkcontribs)
The Quixotic Potato (talkcontribs)

@Sänger I do not think we've ever received an official reply to this answer.

Sänger (talkcontribs)

No, and I don't expect any. They still maintain this fairytale about a dichotomy between wysiwyg and talk pages, the one that was the base of this completely useless "survey" I mentioned above. They even implemented VE in discussions themselves in the 2017 Community Wishlist Survey, but in this still insist that very discussions with VE that it's not possible and moved this simple wish, that could be done in no time with probably just a simple check in a checkbox, to "not possible", because those who desperately want Flow don't want better real talk pages. Grüße vom Sänger ♫(Reden) 09:28, 9 December 2017 (UTC)

Reply to "How much money was wasted on this failed project?"

Cleaning up the mess left behind from the failed LQT and Flow experiments

3
The Quixotic Potato (talkcontribs)

The WMF should focus on cleaning up the mess left behind from the failed LQT and Flow experiments before it starts yet another experiment that is doomed to fail under the new name "Structured Discussions".

77.161.58.217 (talkcontribs)

No reply whatsoever?

Moonian (talkcontribs)

They never admit this project is a failure, why would they reply?

Reply to "Cleaning up the mess left behind from the failed LQT and Flow experiments"

Protect description section

2
Summary by Trizek (WMF)
علاء (talkcontribs)
علاء (talkcontribs)
Reply to "Protect description section"

A vandal renamed my discussion. How to undo?

3
Summary by 197.218.84.133
Syced (talkcontribs)
ChristianKl (talkcontribs)

The only way seems to be to manually rename the post.

I like the idea of flow and structured discussions. On the other hand, the inability to undo vandalism properly gives me lately the impression of it being very unfit at the moment. With occasional vandalism it's not enough for me to switch my talk page back from Structured Discussion but if the vandalism would increase I would.

The ability to undo vandalism by undo/rollback should be a top development priority if the Wikimedia team wants those people who use Structured Discussions to continue using it.

Trizek (WMF) (talkcontribs)

Sorry for the late reply, I'm catching-up.

It is possible to undo a change when the page description or a message has ben changed, but not a title.

@ChristianKl, I read a lot of people having the same opinion as yours. That kind of feedback is important to define priorities to address communities using Structured Discussions' concerns.

Reply to "A vandal renamed my discussion. How to undo?"

MediaWiki message for empty board description

8
Summary last edited by Clump 03:34, 31 July 2018 1 month ago
91.142.85.176 (talkcontribs)

Hi! Is there a possibility to add a MediaWiki message, like MediaWiki:Talkpageheader, on top of Structured Discussions board descriptions? It is incredibly useful to have this message to have a setup like French Wikipedia has. I hope this can be added in Structured Discussions.

Trizek (WMF) (talkcontribs)

Hi! The header has been moved to the board description, to give immediate access to the conversations. Adding a header would allow people to add a lot of informations, that may hide the discussions or block people to discover where they can start a discussion.

What would be the goal of that header?

From my experience on my volunteer account, I see that people leaving me messages respect the advice posted in the sidebar, maybe because I've tried to design the sidebar to catch readers' eyes. Apparently, it works. But that's just an example.

91.142.85.176 (talkcontribs)

Well, if sysops on wiki would add a lot of information to such header, it would be on their behalf. For now there isn't a simple possibility to add anything to Flow header in multiple discussions, you have to add Flow descriptions to every page and they are not available through templating then. MediaWiki messages don't have that problem.

The goal of that header for me is to have a simple message with some basic text on how to act in discussions. Adding this message to every single Flow board upon article creation would be burdensome.

Trizek (WMF) (talkcontribs)

Is it already implemented somewhere?

91.142.85.176 (talkcontribs)

Do not really understand your question. It is present in default MediaWiki talk pages, like in French Wikipedia (the "Autres discussions" banner is added with a MediaWiki message I linked above), so it is a regression that this can't be done in Flow.

Trizek (WMF) (talkcontribs)

Now I see a case, thank you. I've documented it.

On the example you give me, we can see how the page is overloaded and discussions are not accessible. I know most elements are on the talk page itself, but if there is an integration on Structured Discussions, that would be done in consistency with the current design. MediaWiki:Talkpageheader would then be added on top of the sidebar.

91.142.85.176 (talkcontribs)

Yeah, I wasn't talking about user-defined messages, board descriptions can have them if someone wants that clutter.

Thanks for help, hope this can be added soon.

Trizek (WMF) (talkcontribs)

You're welcome. I can't promise anything. That's on developers' hands for now and that kind of improvements is not on the roadmap...

Reply to "MediaWiki message for empty board description"

Scripting in Flow editor - mw.libs.ve.addPlugin not fully available

6
Summary last edited by Clump 03:33, 31 July 2018 1 month ago
185.162.92.7 (talkcontribs)

Hi! Since MediaWiki 1.31 update something in Flow editor changed and I need to update my code. I used to be able to have my own input method (for writing some letters and symbols for users without a special keyboard) working in Flow editor, is there a way to implement this in new one? Some events or hooks to use, maybe. There is no documentation for this at the moment and the only script for Flow makes only stylistic changes.

Trizek (WMF) (talkcontribs)

Hey

You mean the wikitext editor? It has been changed to use the 2017 wikitext editor (for Wikimedia supported wikis only), on which gadgets are coded the same way as on visual editor. That way, you can have gadgets working on both editors. I'm not aware of a gadget I can show, so I would be curious to see if you change yours to try it.

185.162.92.7 (talkcontribs)

Yeah, I mean wikitext editor. It seems to be enabled now for all wikis with visual editor available. I am already supporting visual editor in my code, but it seems like initialization for Flow editor does not work the same way as for standard visual editor.

Trizek (WMF) (talkcontribs)

What is your gadget so I can have a look at it?

185.162.92.7 (talkcontribs)

I have since then found a way to overcome all problems. Bug with Flow editors for me seemed to be in that Flow editors don't support mw.libs.ve.addPlugin at all but support sequenceRegistry and other stuff, so I had to duplicate the code to make it work either in visual editor or wikitext editor.

	mw.loader.using( 'ext.visualEditor.desktopArticleTarget.init', function () {
		mw.libs.ve.addPlugin( function () {
			return mw.loader.using( [ 'ext.visualEditor.core', 'ext.visualEditor.mwwikitext' ] ).done( function () {
				// This does nothing in Flow boards
			} );
		} );
	} );
	if ( mw.config.get( 'wgPageContentModel' ) === 'flow-board' ) {
		mw.loader.using( 'ext.visualEditor.desktopArticleTarget.init', function () {
			mw.loader.using( [ 'ext.visualEditor.core', 'ext.visualEditor.mwwikitext' ] ).done( function () {
				// This seems to work in Flow boards
			} );
		} );
	}

Hope this helps someone if they had to write plugins for Flow editors.

Trizek (WMF) (talkcontribs)

I've documented your case. This is something we need to fix so that it would simplify your life.

Reply to "Scripting in Flow editor - mw.libs.ve.addPlugin not fully available"

paste with wikitext locks up the browser tab

8
Alsee (talkcontribs)

I suspect this latest breakage is caused by Phabricator T155861: Migrate Flow to use the integrated VE/WT editor widget when it exists.

Steps to reproduce:

  1. Go to United States or any of the other 500 articles listed here.
  2. Edit source.
  3. Copy all. (CTRL-A CTRL-C)
  4. Click reply or create a new Flow post in wikitext mode. (Visual mode seems to be equally affected, but I only tested it once.)
  5. Paste. (CTRL-V)
  6. The browser tab locks up completely. Wait. Wait. Wait. In one case I tried waiting over 15 minutes.
  7. Kill the browser tab to escape.

Expected results:

  • Functionality and performance which is not catastrophically inferior or broken compared to existing talk pages. That includes, but is not limited to:
    • On a Talk page the entire sequence from clicking-edit, loading the editor, pasting any article text, clicking preview, and receiving that preview, can ALL be completed in under ten seconds in my experience. Taking twice as long might be a tolerable downgrade, but generating browser time-out popup errors is obviously unacceptable breakage.
    • On a Talk page, pasting any wikitext and previewing provides a correct wikitext render (and of course a correct preview-render of the wikitext). Flow's wikitext support is unacceptably broken, but that's been broken from day Flow was built.


Tip: When the WMF finally gets around to admitting Flow is never going to be accepted, and potentially starts a new project from scratch to address Talk pages, the #1 requirement for design development and testing is to copy paste various articles into it and make sure you're not breaking anything. Any project to replace/improve talk pages is NEVER going to be accepted if the team isn't treating that as a #1 MVP requirement from the start. Talk pages are not chatboards. Talk pages are a wiki-workplace, and editors have this odd expectation that we can copy-paste anything from anywhere to anywhere as part of our work. Any project ignoring that fact is just going to be a black-hole waste of staff-time and donor-money.

197.218.88.227 (talkcontribs)

This is likely worse in a firefox browser. On a chrome browser it loads in a few seconds, less 40. This might be due to performance optimizations that chrome has.

No matter how desperately people want to blame developers. The simple fact is that the textarea input box isn't a magic bullet either. Pasting content equivalent to the maximum bytes (2MB) that can be saved, will mean the browser will also take a few seconds to load it. This might not be an issue for a sufficiently powerful computer, but it certainly will be a massive issue on older and less performant platforms like mobile devices, tablets etc.

Bad performance is quite simply an inherent design flaw of web-based development. Bad editing performance on the web in general isn't going to change in near future, unless editors are redesigned to either use plugins like flash or use "native" web based applications that aren't based on the DOM model or someone comes up with a way to overcome those deficiencies.

Anyway, one way to deal with pastes in general is simply to defer it when it is massive. Instead of pasting the whole content, it could paste enough to fill 3 or 4 screens , and asynchronously load the rest as needed.

197.218.88.227 (talkcontribs)

Indeed, apparently it is an issue that has affected browsers (for years ) using = the "plain" wikitext editor.

https://bugzilla.mozilla.org/show_bug.cgi?id=190147

https://bugs.chromium.org/p/chromium/issues/detail?id=109587

In fact, there are claims that at some point firefox only allowed 64K in a textarea:

https://stackoverflow.com/questions/1600398/large-text-in-textarea-freezes-computer/7584116

Alsee (talkcontribs)

The WMF was informed that Flow had fatal design flaws even before the prototype was built. Three of the most important wikis now have explicit consensus to refuse delivery of the defective product, other major wikis would also surely refuse refuse it if the WMF attempted to move forward on it.

The NewWikitextEditor was effectively built in secret, and as soon as the prototype was made available the WMF was informed that it had fatal design flaws. The biggest wiki has an explicit consensus refuse delivery of the defective product, and other major wikis would surely also refuse delivery if the WMF tried to move forward with it.

I come here pointing out that that the latest move to combine the two mis-designed products causes them to burst into flames, and your response is:

  1. List fictional problems that aren't affecting anyone.
  2. Tell me that Bad performance is quite simply an inherent design flaw of web-based development, which is quite absurd when our pre-existing tools have excellent performance.

I am *this* close to just reverting the two IP posts instead of replying.

There isn't a programming problem. There's a design problem, a strategy problem, and an ignoring-end-user-feedback problem.

Jdforrester (WMF) (talkcontribs)
I am *this* close to just reverting the two IP posts instead of replying.

Please do not blank other people's discussions just because you disagree with them. Such behaviour will likely get you blocked from this (or any) wiki.

Alsee (talkcontribs)

JDF, don't worry. It wouldn't even cross my mind to delete other people's discussions just because I disagreed with them.

But since you're here, perhaps you could make a content-relevant reply? Either on:

  1. The immediate issue of paste into Flow locking up the browser tab apparently due to integration of the 2017Editor; or
  2. preferably on the broader issue of the WMF explicitly disregarding community feedback on Flow and major multi wiki rejection of Flow + the WMF effectively building 2017Editor in secret and disregarding community feedback on 2017Editor and community rejection + the WMF just rolling forwards on both projects and making them go from bad to "kill the browser" worse. I'd really love for us all to work together better new and better wikisoftware, but there seem to be ongoing problems of strategy-conflict with the community and an isolationist approach to design.
Jdforrester (WMF) (talkcontribs)

Sorry, I don't feel I can answer your question. It seems to be based on a set of facts with which I am not familiar.

This post was hidden by Clump (history)
Reply to "paste with wikitext locks up the browser tab"