After some discussions, the best way forward seems to be to revert the fix for LP:1938296. We will also take this particular issue onto our backlog, as the proper fix may affect the UI and API in non-trivial ways.
After some discussions, the best way forward seems to be to revert the fix for LP:1938296. We will also take this particular issue onto our backlog, as the proper fix may affect the UI and API in non-trivial ways.