Description

This happens locally too, and I don't think it has anything to do with configuration that differs on private wikis.

I'm just using a test page on Office wiki as an example, because I was unable to find any other pages in production where both VisualEditor and Flow are enabled (there is a check that the namespace is enabled for VE).

While logged in, on any page in Office wiki (this doesn't matter because the parameter is specified explicitly), run the following two statements in the JavaScript console:

In the second, instead of rendering the provided text, it renders the Flow board.

• Mattflaschen-WMF renamed this task from ApiVisualEditor parsefragment behaves unexpectedly when context page has flow-board content model to API:Parse wrongly outputs the Flow board when the board is only being used as a context title.Mar 17 2015, 5:37 AM

Part of (probably the root cause, so retitling the bug) is either in Flow or core (or an interaction of the two).

It does use the context page's content model by default (giving those results). However, it works fine when contentmodel is specified, which Parsoid already does (@EBernhardson fixed this a while back):

So I'm not sure what the issue is. Removing MediaWiki-Parser since I don't see any sign the problem is there.

I'd appreciate if the Parsoid and VE teams could take a look.

• Mattflaschen-WMF renamed this task from API:Parse wrongly outputs the Flow board when the board is only being used as a context title to ApiVisualEditor parsefragment behaves unexpectedly when context page has flow-board content model.Mar 17 2015, 5:28 PM