Can't set root node in Navigation portlet with p.a.multilingual

[lyralemos]

As discussed in this forum thread:
https://community.plone.org/t/pat-contentbrowser-broken-in-multilingual-sites/21491

When plone.app.multilingual is installed, I am unable to set the Root node.
I'm unable to navigate the site using the contentbrowser, I encounter a "results not found" message.

[petschki]

Currently investigating this. The difference here is that the navigation portlet root_uid field uses source=CatalogSource(is_folderish=True) and so we call the view @@getSource in pat-contentbrowser.

So that should not be the problem, but my investigations showed that the "plone.app.querystring" parsed query (see https://github.com/plone/plone.app.content/blob/master/plone/app/content/browser/vocabulary.py#L161) has some strange results when it comes to INavigationRoot marked folders (like the LRF types from p.a.multilingual).

Debugger tests

assumptions

1. you have a Plone site with the folder structure /Plone1/folder/subfolder/subsubfolder
2. /Plone1 is IPloneSiteRoot
3. /Plone1/folder is INavigationRoot

parse with portal root context

>>> queryparser.parseFormquery(portal, [{'i': 'path', 'o': 'plone.app.querystring.operation.string.path', 'v': '/Plone1::1'}])
{'path': {'depth': 1, 'query': ['/Plone1']}}
>>> queryparser.parseFormquery(portal, [{'i': 'path', 'o': 'plone.app.querystring.operation.string.path', 'v': '/Plone1/folder::1'}])
{'path': {'depth': 1, 'query': ['/Plone1/folder']}}

parse with context inside "navigation root"

>>> queryparser.parseFormquery(folder, [{'i': 'path', 'o': 'plone.app.querystring.operation.string.path', 'v': '/Plone1/folder::1'}])
{'path': {'depth': 1, 'query': ['/Plone1/folder']}}
>>> queryparser.parseFormquery(folder, [{'i': 'path', 'o': 'plone.app.querystring.operation.string.path', 'v': '/Plone1::1'}])
{'path': {'depth': 1, 'query': ['/Plone1/folder/Plone1']}}

So as long as our parsing context is the portal, all is OK, but if our context is inside a nav_root and you want to query for the "portal root path" we're in trouble ... see the last line.

Because of that I could not even browse with pat-relateditems ...

/cc @1letter

[petschki]

Hum ... I think we have to use the absolutePath operator in pat-contentbrowser because with that, the parsed query looks correct:

>>> queryparser.parseFormquery(folder, [{'i': 'path', 'o': 'plone.app.querystring.operation.string.absolutePath', 'v': '/Plone1::1'}])
{'path': {'depth': 1, 'query': ['/Plone1']}}
>>> queryparser.parseFormquery(folder, [{'i': 'path', 'o': 'plone.app.querystring.operation.string.absolutePath', 'v': '/Plone1/folder::1'}])
{'path': {'depth': 1, 'query': ['/Plone1/folder']}}

[1letter]

@petschki currently i'm trying to debug the problem in contentbrowser. I'm not sure and confused where are the right entry point of path calculation. Or is an explicit pattern option for basePath or/and rootPath in the navigation portlet schema sufficient?